on 11-26-2015 8:06 PM
Hi Gurus,
My Message Mapping suppose to be very simple, since I am using the same Message Type for both Source and Target.
I think there might be a reason I get the error message, since after I created everything, I changed few elements in my Data Type from 1..1 to 0...1. I am not sure if that caused my Message Mapping to corrupt. But later I copied my Data Type to a new one and created everything again, still getting the same error. My Data Type have 400 fields, so I didn't want to recreate.
And I did refresh my CPA cache many times during the testing.
I don't understand where the problem is.
Can any of you experts give some hints, I am stuck here for few days already, it is frustrating......
Many thanks in advance!
Blue
The error message in Message Mapping step is as below:
My Message Mapping is as below, for RecordSet, Heaher, and Record the higher level node, I used one to to one mapping
For the lowest level element, I used mapWithDefault as below:
Blue,
Did you actually copy the payload and checked if it's exactly matching with Schema you have it in the mapping program... Even small changes like namespace , element name(Case sensitive) can be big problem.. Do one thing.. since Recordset in the target is also 1..1, don't map Recordset from the source to the target for RecordSet. Just remove that mapping alone and test it.
Thank you,
Justin.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Blue,
What is the mapping for a target field RecordSet (according to error message, mapping failed because of that field)? And what source message did you use to test mapping (please check if source message fields that are used in mapping logic for target field RecordSet, existed and were populated correctly)?
Regards,
Vadim
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
87 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.