Skip to content

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

Template Information

  • Template: Dynamics GP to Dynamics CRM 2011
  • Version: 5.1
  • Integration Type: Bidirectional data synchronization
  • Change Tracking: Dynamics GP's SCRIBESHADOW table (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 in DocsAndScripts/CRMGP_TemplateConfig.sql keep those flags up to date.
  • The publishers defined in publishers-bridges-connections.spkg check that table on a short timer (1–10 seconds depending on the job). They pick up rows marked N or M and build the outbound messages (for example FromERP_Customer).
  • When the downstream DTS succeeds, that same publisher flips the status to S so the row drops off the to-do list. If the DTS errors, the status stays N/M and 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

  1. Review the Overview for architecture details
  2. Explore individual migration flows for specific entity synchronization patterns
  3. Reference the source DTS files in scribe-source/ directory
  4. Check monitoring queries in DocsAndScripts/DataViewQueries/