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

Preview Enrichment Data in an Email

lewisg95724902
Level 2
Level 2

I'm hoping this is the right place to ask this question. We have adobe campaign version 6.1.1

I've built a workflow that creates a segment for an email. The segment uses an enrichment step to get join some data from another step.

This all works fine and when I "Display the target" coming out of the enrichment step I can see the data that I am expecting.

When I add this data to an email template and try to preview it, I get the following error:

PGS-220000 PostgreSQL error: ERROR: relation "wkf321272887_enrich" does not exist LINE 1: ...

The html syntax I have tried is

<%= recipient.targetData.field1 %>

and

<%= targetData.field1 %>

I added them using this selector:

1630103_pastedImage_0.png

So this understands that these fields exist upstream, its just when I go to preview that it can't seem to pull them through. Is there another way I should be previewing emails when enriching data?

Thanks

4 Replies
subhajit9830660
Level 3
Level 3

Hi Lewis,

I think the syntax <%= recipient.targetData.field1 %> is not correct. Try removing this field and check. Also the <%= targetData.xxx %> fields are not visible in preview of email. Try sending a proof and check the result.

Thanks,

Subhajit

lewisg95724902
Level 2
Level 2

Thanks for your response.

I've just tried this, adding in the targetData as additional data for the seed following the instructions in this post - targetdata is not defined - and unfortunately I get the same error when trying to send the proof (screenshot below).

1630913_pastedImage_1.png

pablo_rosero1
Level 10
Level 10

Hi Lewis,

Please try the workaround identified on targetdata is not defined

I hope that works!

All the best,

Pablo

lewisg95724902
Level 2
Level 2

Hi Pablo,

Please see my response above to Subhajit where I stated that when using this workaround I received the same error response when sending the proof.

Thanks
Lewis