Read data from a schema linked to recipient in a Email delivery | Community
Skip to main content
M
muralipraveenr1
Level 2
February 28, 2020
Solved

Read data from a schema linked to recipient in a Email delivery

  • February 28, 2020
  • 2 replies
  • 3726 views

Hello,

We have a custom schema "recipient Registrations" which is linked to extended recipient schema. when we try to include the data from this custom schema in an email delivery
" recipient.recipientRegistration.createdDate" we are getting "undefined"  in the sent out mail/preview section.
when we try to print the entire schema we getting "[object EntityCollection]"
 
Is there any other way to display this value on the Email?
How to display the value from this entity collection object?
 
Thanks in Advance.
 
This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Milan_Vucetic

Hi @muralipraveenr1 ,

 

in case of collection you should access the value using index:

 recipient.recipientRegistration[0].createdDate

 

This will work for you like this in case you have link 1:1.

If you have multiple values for the same recipient you need iteration of index. ([0],[1],[2]...)

 

In case there is not an record for particular recipient you will get error like "Index out of range" therefore you should have conditional personalization here (if/then).

 

Regards
Milan

2 replies

Milan_Vucetic
Milan_VuceticAccepted solution
Level 9
March 2, 2020

Hi @muralipraveenr1 ,

 

in case of collection you should access the value using index:

 recipient.recipientRegistration[0].createdDate

 

This will work for you like this in case you have link 1:1.

If you have multiple values for the same recipient you need iteration of index. ([0],[1],[2]...)

 

In case there is not an record for particular recipient you will get error like "Index out of range" therefore you should have conditional personalization here (if/then).

 

Regards
Milan

    anupk2111
    anupk2111
    Level 2
    March 3, 2020

    @muralipraveenr1  is correct about using the field as a collection.

     

    An alternative workaround could be to create the link with the custom schema and bring back the collection filed into target data. This could be done by using an enrichment, bringing the collection field and renaming the internal name. Now you have the data in the target filed and use it as targetData.fieldXYZ.

     

    Hope this helps.

    Anup

    Terms & ConditionsAccessibility statement

    Loading footer...