CRMPro → Dynamics CRM — Sage X3: what the template catalogue carries

CRMPro → Dynamics CRM — Sage X3: what the template catalogue carries

Keep this skill current. dlake ships updates often and this text is embedded in the CLI you have installed. Before relying on it, compare dlake --version with npm view @commercient/dlake version; if they differ, run npm install -g @commercient/dlake@latest and then dlake skills install, which overwrites the installed skill files with the current text.

dlake-crmpro is the parent skill and the authority for everything general: the crmpro_* tools, CRM_Configuration and CRM_FieldList, TimeStampRepository, the three kinds of source view, the NULL-cursor rule and the silent zero-record run. Read it first; this page does not repeat it. dlake-crmpro-dynamicscrm is the destination skill this page is a child of, and the authority for the Dynamics CRM conventions that hold across every ERP: read it first, then come back here for what this source’s own templates set. This page is dlake-crmpro-dynamicscrm/erps/sage-x3.md, and that skill’s ERP table is what points at it. The catalogue spells this destination DynamicCRM, so that is the value to pass as a tool argument — dlake admin crmpro_templates --crmName DynamicCRM — but the product is Dynamics CRM, which is what this page calls it. The catalogue ships no Standard template for this pair. Its templates are community templates, authored in a tenant and imported the same way as any other, so what follows is what that set amounts to — how many templates, which operations they default to, which destination objects they write and which groups they fall in. A community template’s own names, notes, field mapping and SQL are tenant content and are not published here; read them with dlake admin crmpro_templates against the tenant that holds them. This page grows as the catalogue does.

1. Community templates

The catalogue carries 33 community templates for this pair. A community template is authored in a tenant rather than shipped with the product, and it imports the same way as any other. Its own names, notes, field mapping and SQL are tenant content, so what this section states is what the set amounts to: how many templates there are, what they default to doing, which destination objects they write and which groups they fall in.

• Templates: 33
• Default operations: insert on 33, update on 33, delete on 33
• Marked circular-sync: 0
• Licence groups they span: 4
• Destination objects: account, comrcint_sagex3_address, comrcint_sagex3_customer, CommercientSF8__ACCOUNTMATCHING2__c, comrcint_sagex3_arinvoice, comrcint_sagex3_arinvoicedetail, comrcint_sagex3_bom, comrcint_sagex3_invoicedetail, comrcint_sagex3_invoiceheader, comrcint_sagex3_paymentdetail, comrcint_sagex3_paymentheader, comrcint_sagex3_paymentterm, comrcint_sagex3_product, comrcint_sagex3_quote, comrcint_sagex3_quotedetail, comrcint_sagex3_quoteheader, comrcint_sagex3_quoteline, comrcint_sagex3_salesorder, comrcint_sagex3_salesorderdetail, comrcint_sagex3_salesrep, 5 more and 4 custom objects
• Object display names: CRM Account, CRM Product, CRM UOM, SageX3 Address, SAGEX3 Address, SAGEX3 AR Invoice, SAGEX3 AR Invoice Detail, SageX3 BOM, SageX3 Customer, SAGEX3 Customer, SageX3 Invoice Detail, SageX3 Invoice Header, 14 more and 5 further templates
• Template groups: CRM Quote and Line, Account, CRM Order and Line

A community template is imported the way a shipped one is, and the same rules apply to what it creates: read the process it creates with crmpro_get_process, its mapping with crmpro_field_mapping, and the view it selects from, before activating it.

2. Verifying

# per-prefix counts; every synced record carries its destination id
dlake tool query --profile <tenant> --sql "SELECT LEFT([Key], CHARINDEX(':',[Key])-1) AS prefix, COUNT(*) n, COUNT(NULLIF(SFDCID,'')) withId FROM dbo.TimeStampRepository WHERE CHARINDEX(':',[Key])>0 GROUP BY LEFT([Key], CHARINDEX(':',[Key])-1)"

withId = n for every prefix is the success condition dlake-crmpro defines. The split is on the first colon, which is the prefix boundary whether the key separator is : or ::.

3. Where this sits

dlake-crmpro is the general operating surface — the crmpro_* tools, the setup and transaction tables, field mapping, and the source-view contract that applies to every destination. This page adds what the Sage X3 → Dynamics CRM template catalogue carries. dlake-crmpro-dynamicscrm is the destination skill this page sits under: its own text is the authority for the Dynamics CRM conventions that hold across every ERP, and its ERP table lists this page alongside every sibling ERP page for this destination. For the extract leg that fills the clone tables, see dlake-normalsync; for the on-premises agent that runs it, dlake-syncagent; for the writeback leg, dlake-txdownloaderpro; for standing an integration up, dlake-integration-setup.