research notes and output set builder

Hi everyone,

I’m trying to create an output set element called ‘Research tab notes’ with a parameter of note type.  I set up the parameter just fine and was able to construct my output set, but am running into an error with the element.  When I try to execute the output set I get an error stating “the multi-part identifier c.id could not be bound.”  Here’s how I’ve created the element:

Data select:  !.notes

Data from:   (select a.notes, b.customer_no from tx_cust_notes_ext a JOIN tx_cust_notes b ON a.cust_notes_no=b.cust_notes_no JOIN tr_cust_notes_type c ON b.note_type=c.id)

Data where:  c.id in (<<p4>>)

(c.id being my element parameter of note type, pulled from tr_cust_notes_type)

Does anyone have any suggestions? 

Cheers,
Kathleen

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!

I rewrote your Data from and Data where slightly:

Data from:  (select a.customer_no, a.note_type, b.notes from tx_cust_notes a JOIN tx_cust_notes_ext b on a.cust_notes_no = b.cust_notes_no)

Data where: note_type in (<<p4>>)

Make sure you don’t have single row selected.

It should work now.

However, any note that is over 255 characters long will be broken up. I’ll continue to play with this a little longer to see if I can shoehorn a way of clumping notes into one long field (I wrote a report that does this, so that’s what I’m borrowing from).

Lucie

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!

Correction: use view, rather than table—vxs_cust_notes

My note_type parameter is not multi-select, and is passing a number value.

(select a.customer_no, a.note_type, b.notes from vxs_cust_notes a JOIN tx_cust_notes_ext b on a.cust_notes_no = b.cust_notes_no)

I rewrote your Data from and Data where slightly:

Data from:  (select a.customer_no, a.note_type, b.notes from tx_cust_notes a JOIN tx_cust_notes_ext b on a.cust_notes_no = b.cust_notes_no)

Data where: note_type in (<<p4>>)

Make sure you don’t have single row selected.

It should work now.

However, any note that is over 255 characters long will be broken up. I’ll continue to play with this a little longer to see if I can shoehorn a way of clumping notes into one long field (I wrote a report that does this, so that’s what I’m borrowing from).

Lucie

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!