2. Data-Migration Example
Life
will be easier for you if you create a CRM Adapter publisher as the
first step, because the CRM Adapter publisher is responsible for
capturing changes that occur in CRM, and uses that change event to
trigger an integration to occur (for example, integrate a new account
into the ERP system.)
The publisher will
publish data in a specific schema, however. Creating the publisher
first will allow you to get that schema for use when creating the
actual integration.
Note
Depending
on your version of Microsoft Dynamics CRM, you may need to customize
CRM to publish changes before creating a Scribe CRM adapter publisher.
CRM 3.0 uses the “call-out” functionality.
CRM Live uses workflow to publish changes.
Microsoft Dynamics CRM 4.0 makes use of “plug-in” technology.
The Scribe CRM adapter Help outlines how to configure these various versions of Microsoft Dynamics CRM.
This section assumes you have already made any necessary customizations to Microsoft Dynamics CRM based on the version.
Creating a CRM Adapter Publisher
1. | Open the Console and go to the Publisher and Bridges node under Integration Server.
|
2. | Create
a new publisher, and make its type Microsoft Dynamics CRM Publisher.
You will be prompted for connection information when you move to the
next step of the creation process.
|
3. | After
the connection to CRM has been established, you need to indicate what
CRM entities you want to monitor for change; where a change in an
entity of that type (add/delete/update) triggers some event in your
integration solution (for example, starts an integration). To indicate
which entities you want to use as indicators of change, go to step 4 of
the publisher-creation process and click the Add button.
|
4. | Select
Account as your Dynamics CRM entity that will be used to start an
integration. Select the Insert operation to indicate that when new
accounts are created you want Scribe to publish information about the
related account. Select the Update operation to indicate that when
existing accounts are changed you want Scribe to publish information
about the related account.
Figure 5 shows the publisher entry that is created at this step.
Note
Be
sure to remember this label because you will need it when creating the
integration process that gets started when a new CRM account is created
(or updated)
|
5. | While
still on step 4 of the publisher-creation process, click the XML
Schema’s button and save the XDR someplace you can get to later. This
is the schema that you can use to create integrations against (for
example, create an integration definition for what should happen when a
new account is created).
|
Now that you’ve created the CRM adapter publisher, we’ll create a data migration.