AEP schema 1 to N values stored and created audience.

Question

Hi Team,i want to create a schema with below fields where multiple values can be supported so what should be my approach in creating this schema and loading the data into AEP, plus once it is created how can i create audience? field1field2field3ABCFGHiABCEJDoABCABCDEXYAGCDEBIXy Just to update you, approach that i was thinking is more of creating Dummy field with object as a data type where i can store same field 1 with different values for field 2 and field 3 but while creating audience its causing issue where i am not able to select Field 1 as its is inside the Dummy field object so i am not able to store the all ABC into the audience. In ACS, we used to Have Insert or Update for creating records inside schema but not sure while schema what consideration i can take so that they are part of profile enabled schema plus i do have an option for inserting all records and fetching that inside audience. Any help would be appreciated?

jayakrishnaaparthasarathy · Accepted Answer

Hi @parthmo1 - Based on the sample data that you have shared, seems those fields are supposed to be a object array where it will avoid the data overriding and inject all the necessary values for a single profile. Below is the ideal way that can be created in schema along with other required fields and make sure for all those fields should have a other field that can be considered as primary identifier. Also, ingesting object array data will be bit different than other data type. Please have a complete read about ingesting object array based data.

_tenantname

threefields [ObjectArray]

- Field1 [String]

- Field2 [String]

- Field3 [String]

Also, refer here for how those fields will be treated in audience to play around on it where I have explained with example. You can also have a look on sample object array data that I have posted for reference. I hope this helps you to understand better.

Thank you,
Jayakrishnaa P.

supratim320 · Answer

I assume:it is a profile datasetfield2 & field3 cannot be enumeration (e.g. eventType)field2 & field3 are not dependentIt is a bit hard to think about the schema design without understanding what the fields and their usage in the audience criteria (you would know the field better and their relevant positioning) - however, I will put "field2" & "field3" as an array for "field1" while "field1" could be part of any of the existing field groups/ just below the tenant (custom field group) ACS has a RDBMS structure which cannot store array type, however NoSql DB of AEP can have a variety of data types. The way your schema is designed, you have to ensure the same type of data you are gathering either from source system or you have to transform the source data in data prep step during AEP ingestion. Hope this helps!

field1	field2	field3
ABC	FG	Hi
ABC	EJ	Do
ABC	A	B
CDE	XY	AG
CDE	BI	Xy

Sign up

Login with SSO

Login to the community

Login with SSO

Scanning file for viruses.

This file cannot be downloaded