9 Mar’17

BIIntegration between source as CRM and target as Multiple CRM’s

Use case: 

Let’s say there are multiple service providers (SP) who are on CRM platform and send out the data to single repository Target which is also a CRM system. Based on certain validations and Business logic, the data that is sent from SP can be accepted or rejected. In this case the repository CRM system needs to communicate back to service provider about the status of their data submission. We are using Scribe Insight as the middleware or Integration tool. So how does the Scribe determines, the message that is sent from repository CRM is intended for which service providers CRM? This is done using Scribe Publisher.

What is Scribe Publisher?

Scribe Publisher is a component in Scribe console that produced XML messages based on real time triggering events. Example: If an account is created or updated in CRM then it will trigger publisher to generate XML message. This XML message is then forwarded to Scribe In Queue. This message is then processed by Integration process.

Integration Approach:

To integrate between a single CRM source to Multiple CRM instance as Target. Data needs to be pushed correctly to Target CRM instance based on a value of the data field in the source CRM.

Create a CRM Publisher with same entities published multiple times. Each time it will be process based on the source field value and will output the message to Scribe In Queue with a different message label.

Create Multiple DTS each with different Target CRM, where the data is intended to be pushed.

Create Integration Process (IP) with this DTS and each IP will process the message based on the specific message label.

In the above screen capture, publisher will generate XML message whenever a new account is created or existing account is updated. However based on the value of the field that holds the data for the Target Service Provider (In above example – “description” field in repository CRM holds target CRM of which this account belongs to), publisher will publish a message with different message label. (FromSP1_account.xml, FromSP2_account.xml etc)

These messages come to Scribe in Queue. Integration Process can be then created that will consume these messages based on their message label.

Above Integration was tested on Scribe Insight version 7.9.2.

Written by

Team Member


Leave a Reply

Your email address will not be published. Required fields are marked *

Time limit is exhausted. Please reload the CAPTCHA.

Want to streamline your business processes?

  • This field is for validation purposes and should be left unchanged.

Recent Articles

  • Managing mailbox through Email Archiving

    20 March’ 2018

    Introduction: Email can fill your Outlook Inbox quickly – new messages, replies, and forwards. Before you know it, yo...

    Read more
  • Workaround to Report.SAVEASPDF in NAV 2018

    20 March’ 2018

    Objective: In NAV 2017 Emailing the PDF by running the report using Report.SAVEASPDF is now not allowed in NAV 2018. Th...

    Read more
  • Dynamics 365 Client Diagnostics

    15 March’ 2018

    Main cause of Performance Issues: Bandwidth and latency are the primary characteristics which affects the performance o...

    Read more
  • Closing Blind Shift in MPOS and CPOS in Dynamics 365 for Retail

    15 March’ 2018

    Manual For closing Blind shift in POS: Blind shifts terminate the currently ongoing shift and when logged in a new shif...

    Read more
  • Persistent Filters in the Power BI Service

    13 March’ 2018

    Introduction: The feature is finally release, and it is power BI has announced general availability of persistent filt...

    Read more