Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

SOLVED

Extract Email content for all the users

Avatar

Level 3

Hi All,

I have an issue

I am using dynamic parameters in my email to fill up the content. The content is coming from querying the database. I am using <%=targetData.information %> to fill the email and sending it to 5 users.

 

Is it anyway possible to get the exact content that was mailed to each user including the content that came from DB ?

1 Accepted Solution

Avatar

Correct answer by
Employee Advisor

Hi @bhaskarc1289447 ,

If you want to get the content of targetData.information after the email has been sent, you can store contexutal data from targetData into the delivery logs by extending the nms:broadlogRcp entity and adding the filed in the nms:recipient Target Mapping (Storage section). You must ensure that the field in targetData will ALWAYS be the one mentioned in the Target Mapping.

For instance let assume you extended nms:broadlogRcp to add a field named "information" of type string of 255. in target Mapping targetData.information will be stored to that field.

In the workflow field targetData.information will be stored however targetData.Information won't, it'scase sensitive...

Denis_Bozonnet_0-1653033447797.png

We got customer that uses such capability to store common element across all their campaigns that they then export to their data warehouse for in-depth insights...

That would also be an alternative

Thanks

Denis

 

 

View solution in original post

4 Replies

Avatar

Level 3

Hi @bhaskarc1289447 ,

I feel you can try to render this content by capturing the data from "HtmlContent" field attribute in the email delivery schema.

 

Thanks

Avatar

Correct answer by
Employee Advisor

Hi @bhaskarc1289447 ,

If you want to get the content of targetData.information after the email has been sent, you can store contexutal data from targetData into the delivery logs by extending the nms:broadlogRcp entity and adding the filed in the nms:recipient Target Mapping (Storage section). You must ensure that the field in targetData will ALWAYS be the one mentioned in the Target Mapping.

For instance let assume you extended nms:broadlogRcp to add a field named "information" of type string of 255. in target Mapping targetData.information will be stored to that field.

In the workflow field targetData.information will be stored however targetData.Information won't, it'scase sensitive...

Denis_Bozonnet_0-1653033447797.png

We got customer that uses such capability to store common element across all their campaigns that they then export to their data warehouse for in-depth insights...

That would also be an alternative

Thanks

Denis

 

 

Avatar

Level 3

@Denis_Bozonnet

@Manoj_Kumar_ 

 

Thank you for your reply and I think we will adopt that approach.

A small query:

we are using a schema 'vendor' to create the Target Mapping, so 'abc:broadLogVendor' is created. Now if we have to create a field just as you mentioned, can we include the field directly in the schema since it is not a factory - schema or we need to extend the custom 'abc:broadLogVendor' schema. Please suggest