• Replies 4 replies
  • Subscribers 336 subscribers
  • Views 37 views
  • Users 0 members are here
Related

Infomaker Column Specifications

A. Freeman
$organization

I'm having a problem with a custom screen. For reasons unknown, 2 columns in the dw have the same name. I can see from the Column Specifications tab that they're referencing two totally separate columns in the database, but because they have the same name in infomaker, when I select a column for any elements on this screen, I don't really know which I'm actually grabbing. I can't figure out how to rename the one column.

The data source is a select statement, and there's no aliasing going on in there. I don't know how these two fields ended up with the same description in infomaker in the first place. Anyone ever seen this? Suggestions on how to resolve it?

Parents
  • $organization

    I would go to the local procedure behind the InfoMaker report, give an alias to one of the two columns, then change that name in the InfoMaker report. Just keep spaces out of the alias, and, if memory serves me, don’t start with a digit.

     

    Lucie

     

  • $organization in reply to Lucie Spieler

    Thanks for the quick reply, but the datasource isn't a stored procedure. It's a straight up boring select statement. As far as I can tell, IM won't let me edit the names. I did try giving one an alias just to see if it'd make a difference or change the name directly, having changed it in the datasource, but it didn't do that. 

  • $organization in reply to A. Freeman

    Amanda -

    If you are using the DataSource in Infomaker you should be able to say something like:

     

    SELECT dbo.T_CONTRIBUTION.cont_dt as test
    from T_CONTRIBUTION
    blah blah

    And that will show cont_dt as field 'test'. If I understand what you are trying to do?

    Heather
    Seattle Rep 

  • $organization in reply to Heather Laidlaw Kraft (she/her)

    Thanks. What happened was I had 

    SELECT (a bunch of other things), perf_no, campaign_no 

    from LT_blah

    showing up as 

    Name           DBName

    Perf_no        LT_blah.perf_no

    Perf_no        LT_blah.campaign_no

    in the column specifications.

    I had already tried 

    SELECT (a bunch of other things), perf_no, campaign_no as campaign

    from LT_blah

    and saving and it was still displaying perf_no, perf_no. I’m not sure if adding the alias should have fixed it; I expected it to, but it didn’t.

    I ended up commenting out the last two fields. Saved and let it just get rid of them, then went back to the datasource, uncommented them, saved again and then they showed up with the appropriate names. It meant I had to redo the bits that referenced those fields, but it ended up being the fastest solution at the time.

Reply
  • $organization in reply to Heather Laidlaw Kraft (she/her)

    Thanks. What happened was I had 

    SELECT (a bunch of other things), perf_no, campaign_no 

    from LT_blah

    showing up as 

    Name           DBName

    Perf_no        LT_blah.perf_no

    Perf_no        LT_blah.campaign_no

    in the column specifications.

    I had already tried 

    SELECT (a bunch of other things), perf_no, campaign_no as campaign

    from LT_blah

    and saving and it was still displaying perf_no, perf_no. I’m not sure if adding the alias should have fixed it; I expected it to, but it didn’t.

    I ended up commenting out the last two fields. Saved and let it just get rid of them, then went back to the datasource, uncommented them, saved again and then they showed up with the appropriate names. It meant I had to redo the bits that referenced those fields, but it ended up being the fastest solution at the time.

Children
No Data