Hi,
I have a bit of an urgent ask.
Is there a way to create a mapping between a code we ingest in AEP and it's value which we won't be ingesting. As an example if we have the code [1 - 10000] ingested in AEP, is there an easy way to assign values to these codes such as 1 -> A and 2 -> B. We would also like to use these values in AJO?
Solved! Go to Solution.
Topics help categorize Community content and increase your ability to discover relevant content.
Views
Replies
Total Likes
Hi @trojan_horse ,
One way you can use this is to model the matching data as lookup data in the AEP. Like you ingest the code in the Actual dataset and profile reference through schema attribute to the value in the lookup schema. As your are going to mark the code as primary identity in the lookup schema (Use non-people identifier) you would be able to use the Entity lookup API from the AJO Journey to send a API request for the code and fetch the corresponding value and use in your journey.
Regards,
Vinod
Hi @trojan_horse ,
One way to handle this problem is by using Dataprep functionality and transform the data at the time of ingestion. This will require you to write a one time DECODE logic to implement it.
Regards,
Kumar Saurabh
@Kumar_Saurabh_ Is there an easier way to do this as we'll have thousands of records to map which won't be very efficient
Another way would be to use Enums, only if you have a known finite list, but not sure whether the source value or Display name appears in AJO.
Regards,
Kumar Saurabh
Hi @trojan_horse ,
One way you can use this is to model the matching data as lookup data in the AEP. Like you ingest the code in the Actual dataset and profile reference through schema attribute to the value in the lookup schema. As your are going to mark the code as primary identity in the lookup schema (Use non-people identifier) you would be able to use the Entity lookup API from the AJO Journey to send a API request for the code and fetch the corresponding value and use in your journey.
Regards,
Vinod
Views
Likes
Replies
Views
Likes
Replies
Views
Likes
Replies