That worked, thank you for the getfirst syntax and idea. I dont mean to complain, just that this requires multiple steps per mapper row and more time and potential for human error. I have to 1. Map the field. 2. Copy the field from snaplogic to text editor 3. review the path, and 4. make adjustments to include the get first. Copy/paste back into the field in snap. (I copy out of snap because the editor window is to tight to work with.)
This is actually more time than using [0]. Is there any advantage to using mapfirst rather than jsonpath [0]?
I think I answered my own question on the downside of using [0] in a mapper, if the value is null, the expression will fail.
Yeah with null safe access enabled especially it is a safer expression was my thought. I can’t see any ways to save any time from establishing/developing these mappings necessarily.
