Connector for Microsoft Dynamics is an integration solution which is targeted specifically at the Microsoft Dynamics product family. Connector provides an out of the box integration between Microsoft Dynamics CRM and Dynamics ERP solutions.
Connector for Microsoft Dynamics gives administrators the ability to independently schedule integration runs between a source and destination entity at regular intervals. This provides the flexibility to optimize your network and system resources utilization and also allows you to tailor Connector to your business' unique requirements. This post will provide you with a walk through of how to actually change the schedule, as well as provide you with some business scenarios for why you might want to change the schedule for various maps.
The schedule for a given map can be accessed from that map's "Status" section, which appears at the top of the mapping window in the Connector client, as shown below:
After clicking the "Edit" link following the "Check for Changes:" row, you will be see the following dialog, which will then allow you to change the recurrence pattern and start time for this map.
The "Start" value listed above, is the date and time that this map will start running using the "Recurrence Pattern" listed next. For example, the settings in this screen shot will cause a map to start running on 1/19/2011 at 1:56 PM and will run the map again 30 seconds after that initial run has succeeded and again 30 seconds after every successful run. The "Start" value can be any valid date and time, but an interesting use of this field would be to schedule a map to run over a weekend or during some other low-traffic time. For example, if you are configuring your initial sync between a Dynamics ERP and Dynamics CRM and you know that there are several 10's of thousands of records that will be integrated using this map - you might want to have it start on a Saturday. This would allow for less network bandwidth requirements and also place less demand on your servers (assuming that your business is not operating at a high volume on Saturdays.)
The "Recurrence Pattern" value listed above is the interval between the last successful run of this map and the next attempted run of this map. In this example, the source entity for this map will be queried for changes 30 seconds after the current set of records have been successfully integrated. It's important to note that this is an interval between runs and not a fixed schedule. This means that this map will not be run every thirty seconds but rather every (total time required to integrate a set of records) + 30 seconds. So if the current run of this map will require 400 seconds to process its records, then the next run of this map will be 430 second from the starting point of the current run or 30 from the end of the current run. The options for the recurrence pattern are described in detail next.
Click the "Save" button after ALL map changes to persist those changes to the database.
Other Microsoft Sites
I'm a Customer
I'm a Partner
Follow Microsoft Dynamics