Did you ever figure out the issue?
Bumping up if not since there were no comments yet.
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;
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.
Thank you for helping us out…
@robin what do you import at the top? Right now I’m importing from: org.codehaus.jackson.map.ObjectMapper
org.codehaus.jackson-package version is from an older version of Jackson. The
com.fasterxml.jackson-package version is the right one. See https://stackoverflow.com/a/30782762/277133 for more.
The implementation that is injected is
SnapObjectMapper, which extends
com.fasterxml.jackson.databind.ObjectMapper. It enables some Jackson serialization features by default, as well as some custom serializers for Dates/Times/DateTimes.