1 ACCEPTED SOLUTION
To accomplish translation of a rest call (via the rest or http client snaps) to the actual binary, you need to follow it by a Mapper and Document to Binary, with your request snap entity being displayed as “Base64 encoded data” that just means it’s binary data under the covers and there’s just really not a way for that to be displayed in the JSON representation. You can auto-map the data in the mapper, but the big thing is translating the $entity in the upstream value to $content going into the Document to Binary snap, then you can set the encoding to “NONE”. I’ve added to your example pipeline to show you and am attaching that here.
to get file along with filename_2023_03_22.slp (376.4 KB)
To accomplish translation of a rest call (via the rest or http client snaps) to the actual binary, you need to follow it by a Mapper and Document to Binary, with your request snap entity being displayed as “Base64 encoded data” that just means it’s binary data under the covers and there’s just really not a way for that to be displayed in the JSON representation. You can auto-map the data in the mapper, but the big thing is translating the $entity in the upstream value to $content going into the Document to Binary snap, then you can set the encoding to “NONE”. I’ve added to your example pipeline to show you and am attaching that here.
to get file along with filename_2023_03_22.slp (376.4 KB)
You can also drop the Document to Binary and just change the Mapper’s output view type from Document to Binary:
to get file along with filename, just mapper_2023_03_22.slp (375.3 KB)
