KB Article #177732
EDIFACT mapping : null values are handled differently (1.5.0 vs 2.1.0)
Problem
-- related to mapping xxx to edifact
-- for a migrated flow from Map Designer 2.4.0 to Mapping Services 3.0.1, we are getting different outputs :
MS 2.4.0 : UNH+2JR'BGM'UNT+3+2JR'
MS 3.0.1 : UNH+2JR+ : : : : + 'BGM+++ + 'DTM+ : : 'UNS+ 'UNT+5+2JR'
Resolution
* the correct behavior is on MS 3.0.1
* UNH fields D0065 / D0052 / D0054 /D0051 and DTM D2005 / D2380 / D2379 fields are mandatory (Cardinality 1-1) and their min Definition is 1 , so the mapper automatically add a space and the related separator to be conform to the standard