New answers tagged attachment
0
You're sending the data as "binary", but the data itself is base-64 encoded (apparently). Try adding Content-Transfer-Encoding: base64 to the body's headers.
0
While it is true that some REST resources are available at either https://yourinstance.salesforce.com or https://mydomain.my.salesforce.com or https://mycommunity.<pod>.force.com, the canonical service endpoint for all out of the box platform REST resources is https://yourinstance.salesforce.com or https://mydomain.my.salesforce.com . The latter works ...
0
Since you're pulling the info from an uploaded file, the body of the attachment is already a blob. If the requirement is just to pass the blob to another location then there's no need to manipulate it.
The error was you using base64Decode which expects a Base64-encoded String which .toString does not return
https://developer.salesforce.com/docs/atlas.en-...
0
You would need to detect this specific error condition and then handle the timeout in the way that makes sense for your business logic.
You could check for the string "Unable to complete action on FileStore in allotted time" and then retry the operation using a simple max retry count or exponential backoff algorithm.
Top 50 recent answers are included
