Forum Discussion
robin
8 years agoFormer Employee
I helped out on this one. Yes, I believe the root cause was successfully identified.
A custom object was being used directly as the Document data and hence this behavior was experienced.
To ensure compatibility, an instance of SnapLogic’s Jackson ObjectMapper
can be injected and then used to create a JSON-compatible version of your custom object:
@Inject
private ObjectMapper mapper;
Instead of:
outputViews.write(documentUtility.newDocument(edi835Message));
do this:
outputViews.write(documentUtility.newDocument(mapper.convertValue(edi835Messsage, Map.class));
This ensures that the Document written to the output view contains a Map, which the Mapper will then be able to introspect and display in its input schema.
ryagnik
8 years agoNew Contributor
Thank you for helping us out…