Salesforce connector and Attachment API (Blobs and whatnot)

Has anyone had any luck/experience with the Salesforce connector and successfully inserting new rows to the Attachment API? I have a simple workflow where I take a sample text file into the Blob Input input tool, convert the blob to base64 (per Salesforce API), then append an exisitng parentId and Name (along with renaming the Blob input to 'Body' and shove that into a Salesforce output tool pointing at the Attachment table.

The result is a target record generated, but the response from the Salesforce output tool is "0 records processed and 0 failed across 1 batch".

tool output.png

I've played around with some other combinations of adding other non-required fields (CreatedDate, Description etc) with no changes. If I add something that is not part of the table the Salesforce output tool properly errors out.

Any ideas?

Thanks!

Connectors

API

Salesforce

Accepted answers

NeilR

Blob fields are currently not supported with the Salesforce Output tool (see bottom of this page). The Salesforce Output tool uses the Bulk API, and it looks like this API does not support base64 fields. What API documentation are you referencing? You may be able to create your own custom workflow/macro using the Download tool to get at this functionality.

All comments

NeilR

mrthorne

Thanks for the response!

So if the Salesforce Output tool uses the Bulk API (and that Blob isn't supported), that at least tells me why things aren't working as designed. I was referencing the Attachment SOAP API which talks about the "Body" field (binary data), needing to be first converted to base64 before the insert.

Looking a little into the Spring '16 Salesforce documentation, it's interesting that in the same paragraph mentions this:

"The REST Bulk API lets you query, insert, update, upsert, or delete a large number of records asynchronously. The records can include binary attachments, such as Attachment objects or Salesforce CRM Content."

..and then at the end of that same paragrapoh states what you saw:

"Currently base64 fields are not supported in queries with the Bulk API."

It appears Attachments can be inserted using a batch request instead which will require the creation of a slightly different workflow/macro to make it work properly. A manifest file has to be created with the attachments included. I'll play around with this to see if I can get something working. Unfortunate that it's not quite as slick as using the built in tool, but at least I know where not to spend any more time!

Thanks for the pointing in the right direction.

Quick Links

This months top contributors

atcodedog05 19458

Qiu 15866

binu_acs 15708

MarqueeCrew 13708

apathetichell 13703