Originally posted by: TimUK
At some point the Idoc ido importer changed the field definitions from having a maximum size to haveing no max size specified but pad=yes to a fixed size.
This does cause a change of behaviour in mapping which is a little irritating - or maybe it just us!
As an example - we seem to recall that if a idoc field had a value of just spaces then it would cause an optional output xml element to be created. The current (8.2, 8.3) importer causes effectively the output xml element not to be created as in wtx terms the field isn't present.
Before you all shout - yes the xml schema shouldn't have the item as optional, if in fact its required - that is a different issue to the one I'm investigating here.
I'm looking for people's views on what release the ido importer changed and what the consenus is of whether its the right configuration for a fixed length record.
#DataExchange#IBM-Websphere-Transformation-Extender#IBMSterlingTransformationExtender