| More Information: |
Some EDI message types use a numeric version, for example EDIFACT ENGDAT messages, which include a numeric value of 1 or 2 in the UNH segment.
It is possible for some implementations of these messages to use preceding zeros in the version field, for example 001 and some contain a version of 1.
XE treats these as two distinct values, so if a map has been configured for version 1, a file containing version 001 will not be processed. This can be circumvented by adding duplicate "EDI ID" and "trans ID" sections in the Index, covering both values:
This makes it difficult to deploy a map directly from the XE Developer application as it is not possible to duplicate entries in the index without completely duplicating everything map related (creating a completely new map). The index changes would therefore need to be made manually, after deploying the original map and index.
|