Scribe Migration Documentation¶
Welcome to the Bio-Cat Scribe Migration Documentation. This site documents the Dynamics GP to Dynamics CRM 2011 integration project using Scribe.
Project Overview¶
This project analyzes and documents a Scribe data integration that synchronizes data between:
- Source: Dynamics GP (ERP)
- Target: Microsoft Dynamics CRM 2011
Documentation Sections¶
Migration Flows¶
- Overview - Complete project architecture and concepts
- Customer to CRM - GP customer synchronization to CRM accounts
- Customer to ERP - CRM account synchronization to GP customers
- Address to CRM - GP address synchronization to CRM
- Address to ERP - CRM address synchronization to GP
- Publishers & Connections - Real-time publishers and update-source feeds
Template Information¶
- Template: Dynamics GP to Dynamics CRM 2011
- Version: 5.1
- Integration Type: Bidirectional data synchronization
- Change Tracking: Dynamics GP's
SCRIBESHADOWtable (see below)
How Change Tracking Works (Plain Language)¶
- Dynamics GP writes every relevant insert or update into a helper table named
SCRIBESHADOW. Think of it as the integration team's to-do list. - Each row carries a one-letter status:
N= new,M= modified,S= synced,I= ignore,H= on hold. The triggers inDocsAndScripts/CRMGP_TemplateConfig.sqlkeep those flags up to date. - The publishers defined in
publishers-bridges-connections.spkgcheck that table on a short timer (1–10 seconds depending on the job). They pick up rows markedNorMand build the outbound messages (for exampleFromERP_Customer). - When the downstream DTS succeeds, that same publisher flips the status to
Sso the row drops off the to-do list. If the DTS errors, the status staysN/Mand the record is retried on the next polling cycle. - Because every migration follows this pattern, reviewers can read "SCRIBESHADOW" as "the GP change log we watch for new work"—no deeper SQL knowledge required.
Quick Start¶
- Review the Overview for architecture details
- Explore individual migration flows for specific entity synchronization patterns
- Reference the source DTS files in
scribe-source/directory - Check monitoring queries in
DocsAndScripts/DataViewQueries/