Skip to main content
Level 2
Jan 17, 2024 8:16 PM UTC
Solved

Issue in Creating a Mapping set for a destination data flow using AEP API's

Hi,

 

Need help with error received when creating mapping set for a destination data flow using API. This error is received at create mapping step in this document.  https://experienceleague.adobe.com/docs/experience-platform/destinations/api/activate-segments-file-based-destinations.html?lang=en#create-mapping-set

 

Error:

{
"status": "FAILED",
"source": "segmentMembership.seg_namespace.seg_id.status",
"destination": "segmentMembership_status",
"sourceType": "text/x.schema-path",
"errors": [
{
"exception": "The XDM path: segmentMembership_status is invalid. Please update the XDM path and try again.",
"errorCode": "MAPPER-3809-400",
"errorType": "ERROR",
"missingRequiredFieldError": false
}
],
"warnings": [],
"hasMissingRequiredFieldMapping": false,
"destAccessEnabled": true,
"accessDeniedOnRequiredField": false,
"srcAccessEnabled": true
},
 

 

 Any help is appreciated!
Thanks.
 
Rakesh786Accepted solution
Level 2
Mar 25, 2025 6:05 PM UTC

thanks @derekselby for the info.

Found it really difficult to create a mapping set by manually mapping fields. But Use an existing mapping set ID really solved the problem.

4 replies

derekselby
Level 2
Jan 17, 2024 8:57 PM UTC

Your mapping for the segmentMembership_status looks fine to me, but I don't think you need the \\ escaping the periods on the first name and contactID mappings. Those are only needed if you're referencing an identity namespace with a period in the string. It looks like those are just standard XDM paths. That should fix those.

 

Can you share which connection spec ID you used to create your output schema? I'm guessing the segmentMembership_status has something to do with the output schema that was created.

 

Something else you can do too is create this mapping in the UI, then use the API afterwards to pull out the created mapping set. That way you have a known working payload to use a comparison to see what's different from your request.

Translate
UpasnaShAuthor
Level 2
Jan 17, 2024 11:04 PM UTC

Thank you for your response. I have tried using the working payload but no luck.

 

I am using Amazon S3 connection spec (4fce964d-3f37-408f-9778-e597338a21ee) for output schema.

 

https://platform.adobe.io/data/foundation/flowservice/connectionSpecs/4fce964d-3f37-408f-9778-e597338a21ee

Translate
kautuk_sahni
Level 9
Feb 26, 2025 11:31 AM UTC

@user48 @alokla @prateek-garg @suvodas @elizabethes1 @krish829 @pratheeparunraj @rodolfoch @narendragandhi @jennifer_dungan Can you take a quick look at this question? Any guidance you can provide would be much appreciated!

Translate
Kautuk Sahni