wmlearn,
I’m not sure what the doc statement exactly means but this is one mistake that might happen.
Ok, do this small change to your service and see what happens.
- In a map step create a document say “targetDoc”, under it create a document array say “targetDocArray” with one string variable under it say “targetVar”. Now populate this with some 3 elements of “targetDocArray[0] - [2]”
- In the input of the service create the same structure but named say “sourceDoc” and so.
- In the next map step map the “sourceVar” to “targetVar”. Note: map only String variable, not document level.
Now execute the service with some 5 elements in the input document. End of the service you will notice that the last 2 elements from the “sourceDoc” are missing and not mapped to the “targetDoc”. This is because the “targetDoc” has already defined length. At the same time if you do a docuemnt level mapping (targetDocArray–> sourceDocArray) you can see the entire array getting mapped.
This might happen when you are doing some mapping where you ve to create a temp array under a loop using appendToDoclist and then out of loop by mistake if you happened to map the temp array to the publishable doc on variable level and dont drop the target array, you will end up in losing the data which is more than the minimum number of records you mapped earlier. Ok, thats a silly mistake but I have made it!
Again not sure what the document meant but this is one thing you can keep in mind.
Hope this helps.
#Integration-Server-and-ESB#Flow-and-Java-services#webMethods