Output Sets - Ambiguous Column

 

Sandra,

 

I’ve watched the t-class and understand what is going on….but still am not sure of what to do to fix it.  I believe the issue I’m having is maybe with pre-defined elements?  Is there a list of the pre-defined elements that we are not to change or delete so I’ll know the difference?  I’m trying to use Ticket Date and this is what’s in my table:

 

172      Ticket Date     !.perf_dt          lvs_tkt_hist_dcpa        perf_dt between (<<p3>>) and (<<p4>>) and season in (<<p1>>)        

 

I realize perf_dt is the problem but doing an alias isn’t working for this.  How can I edit or fix so I don’t get the ambiguity error?  I’m having the same thing with the Ticket Season element as well.

 

 

 

Hi Teresa

 

This means that across the elements in your Output Set something has the same name and OSB can’t figure out which one is being referred to. A good habit to get into is to give common field names for your custom elements alias’. For example !.campaign_no as ‘camp_no1’ and the next time you use a field of that name in another element you would do !.campaign_no as ‘camp_no2’ so if ever those 2 elements were used in the same Output Set which campaign_no is identifiable to OSB.

 

Also when you use an alias this is what you refer to in the data_select and where columns, not the actual field name.

 

If you want to learn more about Ambiguity check out my Output Set Builder T-Casts … number 2 explains it depth.

http://www.tessituranetwork.com/network/Learning/Webinars%20Archive/Marketing/Intro%20to%20Output%20Set%20Builder%20T-Cast.aspx

 

Cheers

Sandra

 

 

 

This is for all you Output Set experts out in Tessi land.....because I am far from it!!

What causes a message about an ambiguous column when trying to run the Output Set report?  I've created an output set and one of the criteria that I'm using requires an element parameter.  After selecting the parameter and running the report, I get an ambiguous column error message.  I've edited the entry in tr_query_element to remove the Data Where column entry and the element requirement is removed and I can run my report...but that's not what I want to do because then I get lines in my output that I don't want.  What causes the error and how can I fix it?

This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Technical Forum. You may reply to this message to post to the Technical forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!

This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Technical Forum. You may reply to this message to post to the Technical forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!

This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Technical Forum. You may reply to this message to post to the Technical forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!

 

Sandra,

 

I’ve watched the t-class and understand what is going on….but still am not sure of what to do to fix it.  I believe the issue I’m having is maybe with pre-defined elements?  Is there a list of the pre-defined elements that we are not to change or delete so I’ll know the difference?  I’m trying to use Ticket Date and this is what’s in my table:

 

172      Ticket Date     !.perf_dt          lvs_tkt_hist_dcpa        perf_dt between (<<p3>>) and (<<p4>>) and season in (<<p1>>)        

 

I realize perf_dt is the problem but doing an alias isn’t working for this.  How can I edit or fix so I don’t get the ambiguity error?  I’m having the same thing with the Ticket Season element as well.

 

 

 

Hi Teresa

 

This means that across the elements in your Output Set something has the same name and OSB can’t figure out which one is being referred to. A good habit to get into is to give common field names for your custom elements alias’. For example !.campaign_no as ‘camp_no1’ and the next time you use a field of that name in another element you would do !.campaign_no as ‘camp_no2’ so if ever those 2 elements were used in the same Output Set which campaign_no is identifiable to OSB.

 

Also when you use an alias this is what you refer to in the data_select and where columns, not the actual field name.

 

If you want to learn more about Ambiguity check out my Output Set Builder T-Casts … number 2 explains it depth.

http://www.tessituranetwork.com/network/Learning/Webinars%20Archive/Marketing/Intro%20to%20Output%20Set%20Builder%20T-Cast.aspx

 

Cheers

Sandra

 

 

 

This is for all you Output Set experts out in Tessi land.....because I am far from it!!

What causes a message about an ambiguous column when trying to run the Output Set report?  I've created an output set and one of the criteria that I'm using requires an element parameter.  After selecting the parameter and running the report, I get an ambiguous column error message.  I've edited the entry in tr_query_element to remove the Data Where column entry and the element requirement is removed and I can run my report...but that's not what I want to do because then I get lines in my output that I don't want.  What causes the error and how can I fix it?

This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Technical Forum. You may reply to this message to post to the Technical forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!

This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Technical Forum. You may reply to this message to post to the Technical forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!

This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Technical Forum. You may reply to this message to post to the Technical forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!