Lists: Getting Name 1 and Name 2 to appear as separate columns

Hi everyone -

I'm trying to create a list that would show names within a household as separate columns.  Currently, it shows the Household as one row, the A1 account as another and the A2 accounts as another.  Ideally, I would be able to see the A1 account (first name, last name, and ID) in their own columns and then the A2 info in separate columns.  This will eventually be for a Wealth Engine upload, so I need to format it correctly based on their template.

Thanks!

Parents
  • This is 2-year-old knowledge, but Wealth Engine should be able to format this on their end, free of charge. You simply have to email customerservice@wealthengine.com and direct them to the result sets you want them to format for you. Otherwise, this sounds like a custom output set element in TR_QUERY_ELEMENT. You may be able do something in the Data Select like " !.a1_fname + ', ' + !.a1_lname + ', ' + !.customer_no " within the Constituent Name A1/A2 Group Id... or just make WE do it. :)

    If you choose to go the TR_QUERY_ELEMENT route, it looks like the a2_fname/lname columns only populate when referencing the HH customer_no, so you would have to incorporate all affiliates' individual IDs, despite the screening information living on the HH record... but perhaps there's a better way. 

Reply
  • This is 2-year-old knowledge, but Wealth Engine should be able to format this on their end, free of charge. You simply have to email customerservice@wealthengine.com and direct them to the result sets you want them to format for you. Otherwise, this sounds like a custom output set element in TR_QUERY_ELEMENT. You may be able do something in the Data Select like " !.a1_fname + ', ' + !.a1_lname + ', ' + !.customer_no " within the Constituent Name A1/A2 Group Id... or just make WE do it. :)

    If you choose to go the TR_QUERY_ELEMENT route, it looks like the a2_fname/lname columns only populate when referencing the HH customer_no, so you would have to incorporate all affiliates' individual IDs, despite the screening information living on the HH record... but perhaps there's a better way. 

Children
No Data