I second @_Manoj_Kumar_ ! They are merge policy specific, I had encountered this same query in the past.

@Indra ok I understand now. It should be erroring out due to same field group id, name, etc. One thing I notice is that you are using an OOTB field group, to which i’m not entirely sure if that could be of any reason why. It may be worth logging a ticket with Adobe support referencing your sandbox a...

Hello @Indra could you provide a little more context on what the expected outcome you are looking for here? Why are you wanting duplicate field groups in the schema? David

Hi all!My name is Dave, and I'm located in Pittsburgh, Pa. I’m a certified AEP business practitioner and currently work as a Business Consultant for TAP CXM. I have been involved in 2 AEP RTCDP implementations over the past 3 years. I previously worked as a Product Analyst for DSG, focusing on their...

@Indra it seems as if you are trying to use the {{schema_id}} as a variable. You need to remove it from the headers section and only have it defined within the params. If using as a variable, see the documentation here:Store and reuse values using variables | Postman Learning Center You can also try...

Hi @Indra Ok so that is the problem. You need to add the schema ID into the parameters, and not the headers. Let me know if that works.David

Hi @TapasMahalik @gkalyan is correct. You can use the GET call via API to pull your list of schemas and copy from there. You could also edit the scripts function in Postman in order to pull only what you need via the list. David

Hi @Indra Are you inputting the Schema ID itself into the parameters of the PATCH request? The error message is referencing {{schema_id}} and not the specific Schema ID that you provided above. Could you provide some more context? Thanks! https://developer.adobe.com/experience-platform-apis/referenc...

awesome job @Ankit_Chaudhary !

Hello-Looking for open suggestions on how anyone has successfully continued to keep overall processing time of Global Segmentation Evaluation job, to a minimum, even as more and more audiences are being created. Does number of Schemas and/or dataSets also directly impact this? Or maybe just the size...