When using the Convert Base64 String to Appian Document Smart Service, I've

prestonb over 9 years ago

When using the Convert Base64 String to Appian Document Smart Service, I've noticed that the resulting documents are identical to the original document except that all the carriage return characters (ASCII 0D) are removed. This is actually corrupting some PDF files, which do contain 0D characters internally.

The attached screenshot shows a hex comparison of the original pdf (left) and the resulting pdf after base64 encoding and decoding.

Has anyone seen this before? Is there a workaround? ...

Discussion posts and replies are publicly visible

Parents

0 Eduardo Fuentes
Appian Employee
over 9 years ago

Per our conversation the root cause was a downstream system was ftping the pdf files in ascii mode instead of binary mode. This corrupted them before they were even base64 encoded.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 Eduardo Fuentes
Appian Employee
over 9 years ago

Per our conversation the root cause was a downstream system was ftping the pdf files in ascii mode instead of binary mode. This corrupted them before they were even base64 encoded.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

No Data