A user has created an Output Set featuring a number of new attributes we just created. When she tries to execute this Output Set via the "Execute and Output Set" report, we get the error below:
I'm not sure what's the problem here, since as far as I know only tx_cust_keyword has a column named keyword_no, and running a trace on my SPID results in output that is rather opaque.
Any suggestions? Thank you.
Make sure that the elements you are using in TR_QUERY_ELEMENT have a table qualifier (!.) in the data_select column. The exclamation mark (“bam”) is replaced by the table name when the query is executed. Without, you can result in trying to find a “keyword_no” from multiple tables, which is probably why you see the error here.
This applies to every element except those in the Constituent, Address Information, and Membership categories, as those are “virtual tables”.
If this doesn’t solve the issue, please open a support ticket and we’ll help you further.
______________________________________
Ryan Creps
Network Developer |Tessitura Network, Inc
From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Chris Jensen Sent: Tuesday, July 28, 2009 1:51 PM To: Ryan Creps Subject: [Tessitura Technical Forum] Ambiguous column name 'keyword_no'
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!
Checked by AVG - www.avg.com Version: 8.5.392 / Virus Database: 270.13.22/2253 - Release Date: 07/28/09 06:00:00
Thanks. I appear to have all the "!" in the correct places. The problem goes away if I have just one OB element selecting from the new attribbutes in tx_cust_keyword; as soon as I add a second, I get the error. I'll open a support ticket.
Chris,
I ran into the same problem, especially when trying to get different package records in a row. My workaround in the TR_QUERY_ELEMENT is to use max(pkg_code) in the Data Select instead of !.pkg_code. It seems to work pretty well.
Jan LaRocque
Wow, that works really well. Thank you very much for your reply!