Expand my Community achievements bar.

Never miss an update of the Adobe Journey Optimizer Community Lens! Subscribe now to get the latest updates, insights, and highlights delivered straight to your inbox every time a new edition drops.
SOLVED

Schema to create profile target dimension

Avatar

Level 1

Hi everyone,

 

I'm working on creating various target dimensions to use in my Orchestrated Campaigns. During this process, I noticed there is an OOTB 'Recipient' schema, but it isn't available as an option when setting up a profile target dimension. Since this schema is relational and linked to profiles, shouldn't it be possible to create a target dimension based on it? Any guidance would be appreciated.

 

Thanks,

Sumanth

Topics

Topics help categorize Community content and increase your ability to discover relevant content.

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

@Sumanth_Venkate  Make sure that for the schema -   the primary key, identity and version descriptor are defined

AnuhyaY_0-1761642510495.png

 

 

And create a dataset using the schema and enable for “Orchestrated Campaigns”

AnuhyaY_1-1761642510496.png

 

 

 

View solution in original post

3 Replies

Avatar

Correct answer by
Community Advisor

@Sumanth_Venkate  Make sure that for the schema -   the primary key, identity and version descriptor are defined

AnuhyaY_0-1761642510495.png

 

 

And create a dataset using the schema and enable for “Orchestrated Campaigns”

AnuhyaY_1-1761642510496.png

 

 

 

Avatar

Level 1

Thanks @Anuhya-Y 

Now I can select this schema when creating the target dimension, since the dataset has been enabled for Orchestrated Campaigns. By default, the built-in 'Recipient' dataset was not enabled for Orchestrated Campaigns.

Avatar

Level 2

I am having the same issue. I have the new 'Recipients' schema and dataset enabled, however, it is not selectable when creating a target dimension. The dataset is enabled for Orchestrated Campaigns. The schema, however, only has a primary key defined. It does not have an identifier define, nor does it have a Version field. JSON is attached. 

 

Also, can the Recipients schema be edited? Many of these fields are not applicable to my business / use cases. I'd like to remove the fields that are not needed.