Microsoft Dynamics 365 - Finance & Operations to Salesforce-Upsert of Customer (Account) data
Created by @asharifian, SnapLogic This pattern illustrates the upsert of customer account details from Dynamics 365 - Finance & Operations to Salesforce. Key points: API’s utilizing the data management framework from Dynamics 365 - Finance & Operations are utilized for this integration. Specifically, triggering the export project in Dynamics 365 - Finance & Operations and retrieving the generated export data from Dynamics 365 - Finance & Operations. The Dynamics 365 - Finance & Operations bulk export feature is used. The pipeline will first trigger an export in Dynamics 365 - Finance & Operations, then generate the exported data (as binary via the output view of the second bulk export snap). The exported data is generated as a zip file. The zip file is decompressed and its data streamed through to be upserted to Salesforce. The past 200 exports execution ID’s are stored for logging. The execution ID can be used to re-generate the export from 365 - Finance & Operations. Configuration A bulk export project in Dynamics 365 - Finance & Operations would need to be created for the entity being used in the pipeline. In the case of this pattern, Customers. In addition, the Bulk Export outputs a different data type when one result is returned vs more than one (an object for a single record and an array for more than one). That is why this pattern has a router to differentiate and handle the two data types. Sources: Dynamics 365 - Finance & Operations Customers Targets: Salesforce Account Snaps used: REST Post, Join, Copy, Mapper, File Reader, JSON Parser, Head JSON Formatter, File Writer, ZipFile Read, Binary to Document, Document to Binary, XML Parser, Router, Union, Filter, Salesforce Upsert Downloads Dynamics FO-Salesforce-Customer Upsert.slp (47.2 KB)Microsoft Dynamics 365 - Finance & Operations to Salesforce-Customer Upsert
Created by @asharifian, SnapLogic This pattern illustrates the insert of customer accounts from Salesforce to Dynamics 365 - Finance & Operations. Key points: The Dynamics 365 - Finance & Operations OData REST API is used for the insert operation. A Salesforce Subscriber Snap is used to capture account creations in Salesforce, via a platform event in Salesforce. A customer account identifier value is generated within SnapLogic to send to Dynamics 365 - Finance & Operations, and upon the insert in Dynamics 365 - Finance & Operations, send back to Salesforce. This will marry the record between Dynamics 365 - Finance & Operations and Salesforce. To prevent duplicates, you can modify the pipeline to either: a. Filter out Salesforce records that have the ERP_Customer_Id__c custom field populated because if that field is populated, it means that record was already sent to Dynamics 365 - Finance & Operations in the past. b. Use a Router Snap to update the record in Dynamics 365 - Finance & Operations unless the ERP_Customer_Id__c custom field is already populated in Salesforce. In that case, you can use the Dynamics 365 - Finance & Operations Update custom Snap. Configuration OData API’s need to be enabled/set up in Dynamics 365 - Finance & Operations in order to use them. OData API’s are used for CRUD operations. Sources: Salesforce Account Targets: Dynamics 365 - Finance & Operations Customers Snaps used: Salesforce Subscriber, Salesforce Read, Router, Mapper, Union, Salesforce Update Downloads Salesforce-Dynamics FO Customer Profiles.slp (21.2 KB)ServiceNow-Microsoft Dynamics 365-Leads Integration
Created by @asharifian, SnapLogic This pattern retrieves leads from ServiceNow and sends them to Microsoft Dynamics 365 for Sales CRM application. Upon success or error, the integration log is sent back to a different table in ServiceNow for monitoring/tracking purposes. Within Dynamics 365, leads can be managed and tracked throughout their lifecycle. This also allows for lead automation to enter your sales funnel, and from there you can utilize social media, campaigns, marketing, etc. to further your sales. Configuration This is a bi-directional integration in that leads data is first retrieved from ServiceNow, created in Dynamics 365, and the result of that creation attempt is sent back to ServiceNow for further logging. Sources: ServiceNow Leads Targets: Microsoft Dynamics 365 Lead Snaps used: Rest GET, Mapper, Rest POST, Copy, Join, Union, JSON Formatter, Binary to Document, Dynamics 365 For Sales Create, JSON Splitter Downloads ServiceNow-MS Dynamics 365-Leads Integration.slp (21.6 KB)