Create the pipeline by performing Addition, Substraction, Multiplication and Division operations

Also, if I take the raw BASE64 data from Salesforce and decode it with “base64 -d” it decodes just fine, like the bottom branch decodes it just fine (twice).

Can you give a little more information on the configuration of the “REST GET_FILE” snap? Is it a REST Get snap with the response type set to BINARY? Or, is the response type set to TEXT and $entity is a string?

Hi Tim,

The REST GET is setup with response type BINARY which puts the BASE64 encoded data into the entity field with a “_snaptype_binary_base64”, which I can’t decode directly with the Base64.decodeAsBinary($entity) function.

However, if I BASE64 decode it with the Document-To-Binary snap and then re-BASE64 encode it with the Binary-To-Document snap, I end up with the same BASE64 data in a content field, without any “_snaptype_binary_base64”, which then decodes fine with the Base64.decodeAsBinary($content) function.

Hmm… I wonder how the DECODE BASE64 on the lower branch works then?

I’ll mess with it more.

Hi @christwr , I believe that the base64 encode-decode inbuilt functions has some limitations and the encoding-decoding doesnt support all characters.
In the second approach i guess the data is not being transferred as it is supposed to be even though its working (please verify it).

my suggestion: use a script snap with python code for base64 encoding and decoding functionality.

Thanks.