Scribe Insight – Message Filter

What if you don’t want every account or order to be picked by CRM Publisher. Do we have any option to filter out the messages coming in ScribeIn queue? The answer is Yes.

On MS CRM Publisher in Scribe Console, one can message filtering criteria on each CRM entity. As shown below, we have an option in ‘Message Filters’ section to define the filtering criteria.

Message Filter.JPG

Advertisements

Scribe Insight – Most Common Use Case

In my earlier post, you saw Scribe Insight’s Data Flow and different components.

In this post, we will see the most common use case of Scribe Insight – How Sales order in AX 2012 is to be created upon submission of order in MS CRM.

To implement this – Let us create an Integration Process to see how sales order integration works with Scribe Insight.

Step 1: Install & Configure MS CRM Publisher

First of all, we must have MS CRM Publisher in place with all settings of Message Labels for each published entity, MS CRM is connected well, MSMQ is installed and setup properly, XML Schema for each published entities are saved to Collaboration folder.

pub.png

Connect

Let Scribe know your MS CRM credentials on below screen:

Connect.JPG

MSMQ

Confirm if MSMQ are created and Scribe knows it.MSMQ.JPG

XML Schemas

Save the XML Schema of each published entities in the Collaboration folder.

XSD.JPG

Step 2: Create a DTS file

Once MS CRM Publisher setting looks okay, you can go ahead to create a DTS file.

DTS files are in Collaboration folder and a new file can be created using Scribe Workbench. Following are key stuff which are to be identified and documented before creating a DTS file. Once done, you can do the following:

  1. Define source data store as XML message which are coming in MSMQ upon submission of order in CRM via MS CRM Publisher.
  2. Define target data store as AX AIF Web service.
  3. Configure the steps to create a Sales order in AX.
  4. Define the source to target field mappings. Define Formulas used to convert, parse, or import selected source fields.
  5. Save the file.

DTS.JPG

Following is one of the ways you can configure the steps to create a sales order in AX leveraging AIF Web services:

Steps.JPG

Step 3: Configure an Integration Process

Now you must create an Integration Process and define your integration file. Scribe Integration Processor reads the message header and redirects to integration process based on message label and invokes the concerned DTS file.

IntProcess.JPG

As we are implementing Queue base integration, select Queue as Process Type, Process name of your choice, select your Collaboration Folder and off course the DTS file you created in above step.

IntProcess 01.JPG

Define Message Label as defined in MS CRM Publisher for the published entity.

You may select the message label so as to redirect to another Integration Process on Success or Failure of this Integration Process. For instance, of you want to AX sales Id to be updated back to CRM, you can have another DTS/Integration Process for that and you can define the message label in this IP so that Scribe Integration Processor know where to go after Success or Failure of this IP.

IntProcess 02.JPG

That’s it! As soon as CRM order is submitted, CRM Publisher will pick it up and drop it to ScribeIn queue and when Scribe Integration Processor will see a message in the queue and reads the message label, it will redirect to respective Integration Process, run the DTS file. Once message data passes through with AX validation and business logic, you will see Sales Order in AX 😊!!

Stay tuned for more tips and tricks…..

Scribe Insight Data Flow

If you are looking to integrate Microsoft CRM and Microsoft Dynamics AX 2012, then Scribe Insight is one of the software I came across recently. After playing with it quite around, realized it is one of best option to meet such requirements.

I would like to throw some insight on this. I am going to start with the data flow from MS CRM to AX 2012 and vice versa.

Let’s take an example of Account creation in CRM to understand more clearly:

  1. A customer is created in MS CRM.
  2. MS CRM Publishers monitors the activity and sends XML message in ScribeIn queue (MSMQ).
  3. Scribe Integration Processor reads the message header and redirects to integration process based on message label and invokes the concerned DTS file.
  4. DTS file has source and target connection settings, data massaging and transformation logic and steps to convert the request message into AX understandable message. So, it then makes a connection with Dynamics AX 2012, calls the AX Web service with the converted message.

Similarly, once the customer is created AX 2012, let’s say – AX customer id needs to be updated back to MS CRM:

  1. AX Publishing Routines, a class called ScribeMaster more specifically, facilitates in sending XML message in ScribeIn queue (MSMQ).
  2. Scribe Integration Processor reads the message header and redirects to integration process based on message label and invokes the concerned DTS file.
  3. DTS file has source and target connection settings, data massaging and transformation logic and steps to convert the request message into AX understandable message. So, it then makes a connection with MS CRM and gets the MS CRM updated with AX customer id.

The following diagram depicts how data flows in real-time integration between MS Dynamics CRM and MS Dynamics AX 2012:

Scribe Data Flow.JPG

To one level down, let’s look at different components of Scribe Insight:

 

Message Queue (MSMQ) — There are three publisher message queues:

  1. _CRMPubIn — Required. When a message arrives in the PubIn queue, the Microsoft Dynamics AX and CRM Publisher lets any publisher entities know that the related operation, Insert, Update, or Delete, has occurred. The PubIn queue is always created when you add a publisher.
  2. _CRMPubFailed — Optional. If no publisher entity exists to handle this message and you have configured your publisher to log failed messages, then the message is routed to the PubFailed queue.
  3. _CRMPubSucceeded — Optional. If the Microsoft Dynamics AX and CRM Publisher can resolve the message successfully, then a message is created in the ScribeIn queue. If you have configured your publisher to log successful messages in the PubSucceeded queue, then a single copy of the PubIn message is also created in the PubSucceeded queue.

 

1.png

2.jpg

Data Translation Script/Specification (DTS) — A DTS file created in Scribe Workbench that stores the information required to migrate or integrate data between source and target data stores. This file consists of:

  • Source and target data stores.
  • Data processing logic to use when the DTS file is run.
  • Formulas to link source fields to target fields, set constant values in target
  • fields, or define matching criteria.
  • Formulas used to convert, parse, or import selected source fields.

 

Integration Process (IP) — A part of Scribe Console – It detects an event and runs a DTS to modify and integrate your data. Events that an IP detects include:

  • A message being written into a queue.
  • The results of a SQL query.
  • A file being saved in a folder.
  • A specific time.

 

3.jpg

Collaboration — A set of Integration Processes, related files, and reports that

enables you to organize IPs into meaningful abstractions of business processes.

4.jpg

To reach out to Collaborations folder for ‘Dynamics AX to Dynamics CRM Jumpstart’, go to C:\Users\Public\Documents\Scribe\Collaborations:

5.jpg

Collaboration folder contains many:

  • DTS files
  • .xml & .xsd files
  • ini

 

Publishers

For CRM > AX data synchronization, CRM Publisher generates XML messages to Scribe input queue in the event of Account create/update/delete, Order create/update/delete provided message qualifying criteria is met. Similarly, for AX > CRM data synchronization AX Publishing routines generates XML messages to Scribe input queue in the event of Account create/update/delete, Order create/update/delete provided message qualifying criteria is met.

6.jpg

That’s it for now…but stay tuned…more to come on this.

 

Kindly note – take me just as a reviewer and not as a Sales Person.

 

Source:

https://help.scribesoft.com/scribeinsight/en/index.htm

https://crmconsultancy.wordpress.com