I have a scenario to overwrite existing AEP RTCDP profile attribute with a null using upsert data ingestion
Example:
profile- FN: test, LN: test 2, City: NY
replace City with null
expected profile- FN- test, LN: test2
I tried with data prep mapping iif((upper(FN)).equalsIgnoreCase("TEST"), nullify, City)), it is doesn't overwrite profile attribute 'City', AEP just omit this mapping because of null.
Thanks,
Anandhi
Solved! Go to Solution.
Views
Replies
Total Likes
Hi @AnandhiMa2 ,
AEP ingestion does not accept null values for profile attributes via upsert. The practical workaround is to overwrite with "" (empty string) for strings, or use sentinel values and filter downstream. If you must truly remove a field, it requires explicit Profile API calls, not upsert ingestion.
Reference:
https://experienceleague.adobe.com/en/docs/experience-platform/xdm/schema/composition
Thanks,
Ankit
Hi @AnandhiMa2 ,
AEP ingestion does not accept null values for profile attributes via upsert. The practical workaround is to overwrite with "" (empty string) for strings, or use sentinel values and filter downstream. If you must truly remove a field, it requires explicit Profile API calls, not upsert ingestion.
Reference:
https://experienceleague.adobe.com/en/docs/experience-platform/xdm/schema/composition
Thanks,
Ankit
Thanks for the quick response.
My preference is to avoid zero length strings at all times. Otherwise this complications the logic required when testing in an audience. This is why best practice is to set a min=1 length on string fields even when optional.
If you need to nullify one or fields then I'd recommend sending a complete record not as an upsert.
Views
Replies
Total Likes
Views
Likes
Replies
Views
Likes
Replies