Scribe Integrations Overview¶
Plain Language Summary¶
- The project keeps core records in step between Dynamics GP and Microsoft Dynamics CRM 2011. GP remains the system of record for financial and product data; CRM presents the information to sales and service teams.
- Every GP-facing migration watches the
SCRIBESHADOWchange log that the template triggers maintain. When a GP record is marked as New (N) or Modified (M), the related publisher queues a message for the matching DTS. Once the DTS finishes successfully the publisher stamps the row as Synced (S). - CRM-to-GP migrations rely on CRM change tracking instead, but they still update
SCRIBESHADOWso GP-only monitoring reports stay accurate. - If reviewers remember "
SCRIBESHADOW= the change log/to-do list", they can read the detailed migration guides without keeping SQL statements in mind.
Integration Catalog¶
This table summarizes the DTS packages included in scope.
| Integration File | Source | Destination | Description |
|---|---|---|---|
AddressToCRM.dts |
GP | CRM | Sends new/updated Addresses from GP to CRM. |
AddressToERP.dts |
CRM | GP | Sends new/updated Addresses from CRM to GP. |
CustomerToCRM.dts |
GP | CRM | Sends new/updated Customers from GP to CRM. Used for two-way customer sync. |
CustomerToERP.dts |
CRM | GP | Sends new/updated Customers from CRM to GP. |
publishers-bridges-connections.spkg |
GP/CRM | Queue | Defines the publishers and SQL update sources that feed the DTS message queues. |
UofMToCRM.dts |
GP | CRM | Unable to read file, appears to be binary. Assumed to sync Units of Measure. |
How Polling Works¶
- GP ➜ CRM flows use the
MSGP Publisher(standard entities) which polls the GP database on short intervals (1 second). - Key status flags:
SYNCSTATUS1 = 'N'or'M'means "send this record". Once the DTS completes, the publisher updates the same row to'S'. If the DTS fails, the status remains unchanged and the record is retried. - CRM ➜ GP flows depend on CRM's native change feed. When they create or update GP rows they also inform
SCRIBESHADOWso GP-side monitoring queries continue to show accurate "last touched" information.