• Replies 8 replies
  • Subscribers 337 subscribers
  • Views 45 views
  • Users 0 members are here
Related

Question regarding FT_GET_EADDRESS

David Frederick
$organization

Hi everyone,

We're working on addressing v11 issues in our stored procedures, and I have a question regarding the use of the FT_GET_EADDRESS function. The Preparing Customizations for Tessitura Version 11 document indicates that this function can be used in place of calls to T_EADDRESS to ensure an email address is returned for affiliates, such as A1 and A2 on a household.

However, when I test out this function on an A1 or A2 affiliate to a household where the affiliate has no email address, but the household does, it returns no data. Here is a specific example: Household ID 425453 has two affiliates. A1 = 2959141 and A2 = 2959142. The household has two active email addresses on file.

This statement against the household record returns a single row with an email address, as expected:

select * from FT_GET_EADDRESS (GETDATE(), null, null, null, 425453)

However, using the A1 affiliate - 2959141 - it returns no results.

Did I misunderstand the intended use of this function or do we perhaps have the wrong version of FT_GET_EADDRESS in our v11 test environment?

Thanks,
David 

Parents
  • $organization

    Hi Chuck,

     

    Thank you for your reply. Neither email address is marked primary. Email addresses are not shared between companies in our consortium, so consequently, every email address in our system uses a control grouped type.

     

    Essentially what we are looking for is a way to pull the same email addresses for A1 and A2 affiliated individuals as though we were passing the ID number of the household. Of course, if the individual record has an email address, we would want that to take precedence.  I can write a function if necessary, but didn’t want to reinvent the wheel.

     

    Thanks again,

    David

     

    From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Chuck Reif
    Sent: Tuesday, May 15, 2012 7:26 PM
    To: David Frederick
    Subject: Re: [Tessitura Technical Forum] Question regarding FT_GET_EADDRESS

     

    Are either of the two emails on the household marked as Primary?

    From: David Frederick <bounce-davidfrederick9045@tessituranetwork.com>
    Sent: 5/14/2012 2:18:15 PM

    Hi everyone,

    We're working on addressing v11 issues in our stored procedures, and I have a question regarding the use of the FT_GET_EADDRESS function. The Preparing Customizations for Tessitura Version 11 document indicates that this function can be used in place of calls to T_EADDRESS to ensure an email address is returned for affiliates, such as A1 and A2 on a household.

    However, when I test out this function on an A1 or A2 affiliate to a household where the affiliate has no email address, but the household does, it returns no data. Here is a specific example: Household ID 425453 has two affiliates. A1 = 2959141 and A2 = 2959142. The household has two active email addresses on file.

    This statement against the household record returns a single row with an email address, as expected:

    select * from FT_GET_EADDRESS (GETDATE(), null, null, null, 425453)

    However, using the A1 affiliate - 2959141 - it returns no results.

    Did I misunderstand the intended use of this function or do we perhaps have the wrong version of FT_GET_EADDRESS in our v11 test environment?

    Thanks,
    David 




    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!


    Privileged And Confidential Communication. This electronic transmission, and any documents attached hereto, (a) are protected by the Electronic Communications Privacy Act (18 USC §§ 2510-2521), (b) may contain confidential and/or legally privileged information, and (c) are for the sole use of the intended recipient named above. If you have received this electronic message in error, please notify the sender and delete the electronic message. Any disclosure, copying, distribution, or use of the contents of the information received in error is strictly prohibited.
  • $organization in reply to David Frederick

    We're looking into the code for FT_GET_EADDRESS which at the moment only exposes inherited email addresses if they are primary.

Reply Children
  • $organization in reply to Chuck Reif

    While you are looking at this procedure, we are having the opposite issue.  In our environment, the orders are on the household and emails generally live with the affiliated individuals.  The email addresses are marked primary, but when we use the household ID with the FT_GET_EADDRESS function no eaddress is returned.  It appears the inheritance is flowing down from household to affiliated accountss, but does not roll up from affiliated individuals to the household.  Was this the intended behavior?  If so, can you make any recommendations?  At this point our only thought is to make a custom function.

    Thanks

    Jackie Guy

  • $organization in reply to Jackie Guy

    Jackie, 

    You should be getting the household email address in the results.  I have not been able to re-create this issue on my system.  If I have an email address on the household I am getting the email address in the results.  I just did a simple selection where constituent 12 is a household:

    select b.address

    From T_CUSTOMER a

    CROSS APPLY [dbo].ft_get_eaddress(GETDATE(), null, null, null, a.customer_no) b

    where a.customer_no = 12

    If using this simple sample code you are not able to get the household email address then I would put in a help ticket on TASK as you should get the household in the results.  That being said, there were some changes to this procedure in the 11.0.3 patch so if you have not patched yet you may see slightly different results.  

    Best,

    Anna