Exporting optional addresses

Hi everyone,

I have a list of patrons with a winter address in Florida.  Is there a report that will let me choose to export this optional address instead of the patrons' primary address for the whole list?

Thank you,

Josh Wright

Parents
  • Reports and utilities that output addresses (including the Execute an Output Set report) have parameters meant to help you select winter addresses, but they are based on address purpose or address active dates.  Would either of those two options work for you in this circumstance?

     

    If not, you’ll have to add a new output set element for address that has a parameter for address type (or have an IT resource pull these addresses for you from the back end).

     

    Kevin Sheehan

    Senior Documentation & Learning Resources Specialist

    Tessitura Network

    +1 888 643 5778 x 329

    ksheehan@tessituranetwork.com

     

  • Kevin, 

    I am running in to this issue - i need an output that pulls all available options of our address types, NOT just the primary address.  
    I don't see this option in the output recipe book - and we do not have IT support at our org, and cannot afford consulting - is there an output set recipe that you have for this, OR is there another way for me to get this info about my constituents via list/extraction or output set that I'm just not aware of? 

    Thank you! 

  • Hi Kelly! Kevin asked me to reply on his behalf. I suggest you implement the Emails by Type recipe. If you use this element without the filter applied, it will return all active email addresses for a constituent. 

  • Thanks Michael! I was looking for mailing addresses- will this idea used for the emails work for trying to build the output for address types too?

  • Oh I'm sorry, I read too fast! Postal addresses are really similar to emails, just a few more fields. 

    Add a row to TR_QUERY_ELEMENT_GROUP with a Description of "Address – Multiple Output" (or however you'd like to label it), a Data From to VS_ADDRESS, a Data Where of !.inactive <> 'Y' and a Category of Address Information.

    Then add 5 rows to TR_QUERY_ELEMENT (for street 1, street 2, city, state, and postal code):

    1. Street 1: 
      1. Description: Street 1
      2. Group Id: Address – Multiple Output 
      3. Data Select: !.street1
    2. Street 2: 
      1. Description: Street 2
      2. Group Id: Address – Multiple Output 
      3. Data Select: !.street2
    3. City:  
      1. Description: City
      2. Group Id: Address – Multiple Output 
      3. Data Select: !.city
    4. State: 
      1. Description: State
      2. Group Id: Address – Multiple Output 
      3. Data Select: !.state
    5. Postal Code:
      1. Description: Postal Code
      2. Group Id: Address – Multiple Output 
      3. Data Select: !.postal_code
Reply
  • Oh I'm sorry, I read too fast! Postal addresses are really similar to emails, just a few more fields. 

    Add a row to TR_QUERY_ELEMENT_GROUP with a Description of "Address – Multiple Output" (or however you'd like to label it), a Data From to VS_ADDRESS, a Data Where of !.inactive <> 'Y' and a Category of Address Information.

    Then add 5 rows to TR_QUERY_ELEMENT (for street 1, street 2, city, state, and postal code):

    1. Street 1: 
      1. Description: Street 1
      2. Group Id: Address – Multiple Output 
      3. Data Select: !.street1
    2. Street 2: 
      1. Description: Street 2
      2. Group Id: Address – Multiple Output 
      3. Data Select: !.street2
    3. City:  
      1. Description: City
      2. Group Id: Address – Multiple Output 
      3. Data Select: !.city
    4. State: 
      1. Description: State
      2. Group Id: Address – Multiple Output 
      3. Data Select: !.state
    5. Postal Code:
      1. Description: Postal Code
      2. Group Id: Address – Multiple Output 
      3. Data Select: !.postal_code
Children
No Data