2 things that surprised us while developing Attachment Exchange Interface for Salesforce instances with Mulesoft.
Our Task: Build interface for synchron iz ation of Cases with attachments between two Salesforce instances. Main assumption of the implementation: Attchaments linked directly to case and also attachments from emails are process separately. Exchange of Attachments should be triggered by successful transfer of Case. So generally first Case exange flow is process and when it is successfully done, Attachments exchange flow is triggered. Today we are focused on Attachment part. Implementation for the first sight seems to be easy. All we need to do is to query needed Attachment data basing on Case Id from one Salesforce instance and insert it to second Salesforce instead. Unexpected issue: The main problem was proper approach for querying Attachments data. As we know the best practice for that is to use for that Content Version object. Because we need to retrieve attachments that are linked directly with Case as well as attachments from linked ...