How can we add criteria to Output Set Builder for the following Affiliate names for Households contained in the list?
A1 First Name
A1 Last Name
A2 First Name
A2 Last Name
Is this possible?
Thanks,
Chuck
No view needed it works from the standard t_customer table. Just enter the details listed into the TR_QUERY_ELEMENT system table
From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Charles Buchanan Sent: Saturday, 9 February 2013 2:42 AM To: Sandra Ashby Subject: RE: [Tessitura Technical Forum] Adding A1 & A2 Names to Output Sets
Hi Sandra, Thank you for the response. Does this also require a SQL view to be added or will it work simply by adding these to the system table? Thank you, Chuck
From: Sandra Ashby <bounce-sandraashby2064@tessituranetwork.com> Sent: 2/7/2013 7:56:04 PM
Hi Charles
Sorry for my late reply - I was away during January.
I have an output set element that I have created that might help you. It uses the Sortname in t_customer.
For Households it returns A1Lastname/A1Firstname. For individuals it returns lastname/firstname. For organisations it returns the company name.
Description
Customer_sortname
Category
Constituent
Data_select
!.sort_name
Data_from
t_customer
Single_row
checked
Cheers
Sandra
From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Charles Buchanan Sent: Wednesday, 16 January 2013 10:41 AM To: Sandra Ashby Subject: Re: [Tessitura Technical Forum] Adding A1 & A2 Names to Output Sets
Hmm, it looks like we already have these in TR_QUERY_ELEMENT carried over from v10. I believe we are on the newest version of v11 as we just went live a few weeks ago.
My issue is that if a household account is on the list, the output set criteria for Customer First Name and Customer Last Name does not pull A1 information as we would like but instead a blank for First Name and the Household name for Last Name.
From: Doug Jones <bounce-dougjones2834@tessituranetwork.com> Sent: 1/15/2013 3:17:07 PM
We have just put these into the TR_QUERY_ELEMENT system table based off of the view VB_Customer. Haven't run into any problems yet but YMMV. I'd definitely advise waiting until you have the newest VB_Customer view from the 11.0.4 patch as the 11.0 VB_Customer view was performing poorly here.
id description category data_select data_from 201 Customer Last Name2 101 lname2 VB_CUSTOMER 200 Customer Last Name 101 lname VB_CUSTOMER 199 Customer First Name2 101 fname2 VB_CUSTOMER 198 Customer First Name 101 fname VB_CUSTOMER
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!
Great!
Thank you.