I am new at my organization, and I am trying to create an output set that gives a me patron names based on a list of ticket buyers that I created. I know how to create an output set from a list, but the output I am getting is listing "The Smith Household" because that is what was created in their records as their lname. Their actual last name only appears in their constituent record under "affiliate1" . I don't see an element in output sets that lets me pull by affiliate.
How do I get my list of ticket buyers to output as "lname", "fname"?
Thank you.
Hi Dennis You'll need to create new output set elements to pick up the lname and fname from the A1 and A2 affiliated constituents of the Household in your List. There's a reference page in here to a T-Cast session on how to work with Output Sets, and it links to a document called the "Output Set Cookbook" which has lots of recipes for new elements that you might want to create. Not this one, sadly... But the easiest place to pick up those values is from the view called VB_CUSTOMER, which is what we've done. Because it's meant to be a "bridging view" to help you deal with the transition from v10 to v11 or 12, it's not guaranteed to persist, but it's still there in v12, so it's safe for a while, at least. And given it's so useful for stuff like this, hopefully it will hang around. I've attached a little snapshot below of the relevant bits from our TR_QUERY_ELEMENT table that pull from VB_CUSTOMER. Hopefully it will appear... otherwise you can see it here. Ken From: Dennis Keefe <bounce-denniskeefe5448@tessituranetwork.com>Sent: 1/15/2015 6:23:33 PMI am new at my organization, and I am trying to create an output set that gives a me patron names based on a list of ticket buyers that I created. I know how to create an output set from a list, but the output I am getting is listing "The Smith Household" because that is what was created in their records as their lname. Their actual last name only appears in their constituent record under "affiliate1" . I don't see an element in output sets that lets me pull by affiliate. How do I get my list of ticket buyers to output as "lname", "fname"? Thank you.This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Shared Reports Forum. You may reply to this message to post to the 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!
Hi Dennis
You'll need to create new output set elements to pick up the lname and fname from the A1 and A2 affiliated constituents of the Household in your List.
There's a reference page in here to a T-Cast session on how to work with Output Sets, and it links to a document called the "Output Set Cookbook" which has lots of recipes for new elements that you might want to create.
Not this one, sadly... But the easiest place to pick up those values is from the view called VB_CUSTOMER, which is what we've done. Because it's meant to be a "bridging view" to help you deal with the transition from v10 to v11 or 12, it's not guaranteed to persist, but it's still there in v12, so it's safe for a while, at least. And given it's so useful for stuff like this, hopefully it will hang around. I've attached a little snapshot below of the relevant bits from our TR_QUERY_ELEMENT table that pull from VB_CUSTOMER. Hopefully it will appear... otherwise you can see it here.
Ken
From: Dennis Keefe <bounce-denniskeefe5448@tessituranetwork.com>Sent: 1/15/2015 6:23:33 PM
Came across this thread, and though it's old, I think this is worth adding:
A1 and A2 fields for this purpose are great, but be careful about whether deceased and inactive people are pulling in (typically) your A2 slot. I had our DBA modify the A2 so that it would be blank in those cases.
I've since had Klearsky build an Email salutation that populates nightly, and for households we use the household salutation for emails found on HH and affiliates - both for consistency, and because unfortunately there's no correlation between which account an email is found and whom (within a HH) is getting an email. Simplified things for us.
MeganSeattle Symphony