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.
Let Scribe know your MS CRM credentials on below screen:
Confirm if MSMQ are created and Scribe knows it.
Save the XML Schema of each published entities in the Collaboration folder.
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:
- Define source data store as XML message which are coming in MSMQ upon submission of order in CRM via MS CRM Publisher.
- Define target data store as AX AIF Web service.
- Configure the steps to create a Sales order in AX.
- Define the source to target field mappings. Define Formulas used to convert, parse, or import selected source fields.
- Save the file.
Following is one of the ways you can configure the steps to create a sales order in AX leveraging AIF Web services:
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.
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.
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.
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…..