Expand my Community achievements bar.

Announcing the launch of new sub-community for Campaign Web UI to cater specifically to the needs of Campaign Web UI users!
SOLVED

Using a Data Schema for one off send

Avatar

Level 1

Hello! 

 

I am developing an email that will send using a specific data schema, but I do not have that schema in my sandbox.  I am wondering if the correct flow for this would be to start a workflow -> call the data schema in question -> populate the variables - but how would I populate the data schema with the data I need for the send? 

 

Also, is there a way to do this as a proof or individual send? Or do I have to run a workflow in order to call the schema in question? 

 

Thank you.

 

-Bob 

1 Accepted Solution

Avatar

Correct answer by
Level 6

Hi bob,

is this "data schema" is like the recipient schema?

I mean: it contains all the columns that you need for your sending including the custom variables?

 

If yes, be sure to create a target mapping dedicated to your schema: Target mapping | Adobe Campaign

Once done, you can import in a workflow a CSV file to insert/update required columns in the "data schema" and then use a query activity to select it in order to target your delivery population

 

But... That's the technical aspect, for my part, as you could use directly the CSV file with an import activity and use the existing "mapAny" target mapping. Is there any special requirement to build a dedicated schema?

 

 

 

View solution in original post

6 Replies

Avatar

Correct answer by
Level 6

Hi bob,

is this "data schema" is like the recipient schema?

I mean: it contains all the columns that you need for your sending including the custom variables?

 

If yes, be sure to create a target mapping dedicated to your schema: Target mapping | Adobe Campaign

Once done, you can import in a workflow a CSV file to insert/update required columns in the "data schema" and then use a query activity to select it in order to target your delivery population

 

But... That's the technical aspect, for my part, as you could use directly the CSV file with an import activity and use the existing "mapAny" target mapping. Is there any special requirement to build a dedicated schema?

 

 

 

Avatar

Level 1
Thank you for your response! My data schema has fields that are not in my recipients table.

Avatar

Level 1
Thank you for your response! My data schema has fields that are not in my recipients table. My hope is that I can test the dynamic variables in my email by using that schema in my sandbox before pushing to Prod. But perhaps I am thinking about it the wrong way.

Avatar

Level 6

Personnaly, I would have suggested you to use a dataloading activities for importing a CSV file with your custom fields but be sure to have a column with the recipient Id (or another field to identify your recipients) in it.

If we can say that "1 line from the CSV = 1 recipient" then it will be easy: after the file import, just use a enrichment activity.

Open it and go on the 2nd tab ("Reconciliation"), select "use simple reconciliation key",

select "recipient" as targeting dimension,

select the column of your "recipientId" in source expression and "recipientId" as destination expression.

Now you no more have just "columns" in your workflow but "recipients with new columns": you can add your delivery but be sure that all your "special" columns are coded this way "targetData.mySpecialColumn".

 

if this is for a "one shot" delivery I wouldn't create a dedicated schema for that but prefering to use the most simple tools without having to alter the structure of the database

Avatar

Level 1
Not really no. The Data schema exists in Prod but not in the sandbox. So I dont have the fields that will be on the record. However, to your point, could I set up a workflow that imports a spreadsheet and then maps those fields to the custom data variables I have in the HTML?

Avatar

Level 6
you can do it even easier: https://experienceleaguecommunities.adobe.com/t5/adobe-campaign-classic-questions/how-to-launch-from... just don't forget that through this external file mapping, you'll have to call your custom columns with "datasource.myCustomColumn"