Creating UPSERT dataflow from DLZ into a XDM Individual Profile class schema | Community
Skip to main content
June 28, 2024
Solved

Creating UPSERT dataflow from DLZ into a XDM Individual Profile class schema

  • June 28, 2024
  • 1 reply
  • 939 views

Hi everyone,

I have tried reading the documentation but it's pretty unclear how to do this.
Let me explain the situation, to put it simply, we have a XDM Individual Profile class schema, with its dataset. We need to do a partial profile update (updating one object in a profile using the primary ID). Basically the primary dataflow brings all the data except the one object which comes from this dataflow.

I updated the dataset with "isUpsert:true" to the unifiedProfile tag, but seems it still acts like create and just takes the last insert as the whole profile.

To be more specific we are uploading test data over DLZ, and should later connect the dataflow to a GCS bucket.

Thanks in advance.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by abhinavbalooni

Hey @florijanga 

 

I assume when you mentioned above you read the documentation, you referred to this link ? https://experienceleague.adobe.com/en/docs/experience-platform/catalog/datasets/enable-upsert

 

Basee on what you just mentioned, it should work except there is one thing you need to ensure. If this is an existing dataset, enabled for profile, then you would first beed to disable it for profile then set the upsert flag to true and then enable it back for profile.

 

Did you follow the above steps in order?

 

Cheers,

Abhinav

1 reply

abhinavbalooni
Community Advisor
abhinavbalooniCommunity AdvisorAccepted solution
Community Advisor
June 28, 2024

Hey @florijanga 

 

I assume when you mentioned above you read the documentation, you referred to this link ? https://experienceleague.adobe.com/en/docs/experience-platform/catalog/datasets/enable-upsert

 

Basee on what you just mentioned, it should work except there is one thing you need to ensure. If this is an existing dataset, enabled for profile, then you would first beed to disable it for profile then set the upsert flag to true and then enable it back for profile.

 

Did you follow the above steps in order?

 

Cheers,

Abhinav

August 14, 2025

FYI, I just ran into this exact issue (existing dataset enabled for profile). I figured it out on my own by just trying some combinations, but you should really update your document to reflect this use case and save people a lot of frustrating troubleshooting of this issue.