Whats the relevance of XDM compliant in JSON source ingestion in AEP ?

[suyashkansal]

Hello Folks!, 

Need your 2 cents on the usage of drop down options for XDM compliant options - "Yes" or "No" while ingesting source data in JSON format. Any documentation will also help, as need to know what goes in behind when working with both options. 

Note: Just an observation, while ingesting json data as XDM compliant, we skips the mapping fields part in UI, why is that and data gets properly mapped for even array of object fields.

[gengaipandi03]

you are right that xdm compliant option is to load the array objects without any mapping issues. For example, you have the following file 

firstname:xyz

lastname:abc

email:email@email.com

when you load this csv file, you need to map the source file which is csv file fields and target values from aep schema's xdm attributes. But, when you load the second option called json, it is a proper key value pair which is structures instead the AEP schema. So, it will automatically map to those values

{_tenant:{"firstname":"xyz","lastName":"abc","email":"email@email.com"}}

[suyashkansal]

Thanks @gengaipandi03 and for encrypted PGP data ingestion, do we have to select the XDM compliance as "No", so that we can do the source and schema fields mapping ? 

[bjoern__koth]

Hi @suyashkansal 

that is the exact behavior you observed. Toggling the XDM compliance tells the system that the incoming data structure is already in the correct JSON format and requires no additional mapping. If your data fails to match the expected the format, the import will fail.