CRMPro → Salesforce — Microsoft Dynamics GP 2016: what the shipped templates set up

CRMPro → Salesforce — Microsoft Dynamics GP 2016: what the shipped templates set up

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-salesforce is the destination skill this page is a child of, and the authority for the Salesforce 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-salesforce/erps/microsoft-dynamics-gp-2016.md, and that skill’s ERP table is what points at it. What follows is only what the shipped Microsoft Dynamics GP 2016 → Salesforce templates themselves set, read from their Insert_Query, CreateViewQuery and MappingJson. This page grows as the catalogue does.

1. What the templates deliver

Group	Business outcome	Objects	Source tables and views
Sale User Define & Track No Work History	ERP SOP10106, SOP10107 data becomes CommercientSF9__SOP10106__c in Salesforce. New records are created and existing ones updated; none are deleted.	CommercientSF9__SOP10106__c	SF_ERP_Salesforce_Clone_SOP10106, SF_ERP_Salesforce_Clone_SOP10107
Account	In addition to creating the Account record from your ERP customer records, Commercient syncs over the entire Accounting AR Customer record into a Commercient AR Customer object which is a Managed Custom Object (MCO). A lookup field is provided to lookup to the default AR Customer record MCO from the Account record. New records are created and existing ones updated; none are deleted.	Account, CommercientSF9__RM00101__c, CommercientSF9__RM00102__c, CommercientSF9__RM00103__c, CommercientSF9__RM00104__c	CustomerCodeGUID, SF_ERP_Salesforce_Clone_RM00101, SF_ERP_Salesforce_Clone_RM00102, SF_ERP_Salesforce_Clone_RM00103, SF_ERP_Salesforce_Clone_RM00104
Product	ERP IV00101, IV00102 data becomes CommercientSF9__IV00101__c, CommercientSF9__IV00102__c, Product2 in Salesforce. New records are created and existing ones updated; none are deleted.	CommercientSF9__IV00101__c, CommercientSF9__IV00102__c, Product2	SF_ERP_Salesforce_Clone_IV00101, SF_ERP_Salesforce_Clone_IV00102
Invoice	Both Open and Historical invoices are synchronized. Open invoice changes, such as a balance change, or a terms change are reflected in the CRM as they sync based on the frequency of the sync you have chosen (e.g. every hour for example). New records are created and existing ones updated; none are deleted.	CommercientSF9__IVC10100__c, CommercientSF9__IVC10101__c, CommercientSF9__IVC30101__c, CommercientSF9__IVC30102__c, CommercientSF9__IVC10102__c, CommercientSF9__IVC10103__c, CommercientSF9__IVC10200__c	SF_ERP_Salesforce_Clone_IVC10100, SF_ERP_Salesforce_Clone_IVC10101, SF_ERP_Salesforce_Clone_IVC30101, SF_ERP_Salesforce_Clone_IVC30102, SF_ERP_Salesforce_Clone_IVC10102, SF_ERP_Salesforce_Clone_IVC10103
Pricebook	ERP IV00101, IV00108 data becomes PricebookEntry in Salesforce. New records are created and existing ones updated; none are deleted.	PricebookEntry	SF_ERP_Salesforce_Clone_IV00101, SF_ERP_Salesforce_Clone_IV00108
Salesorder	Commercient will sync the Sales Orders from the ERP Sales Order Entry module to the Commercient Sales Order Header (MCO) objects in CRM. In the CRM, customer service and sales people can visualize the status of the order such as on hold, backorder, forward order, scheduled for delivery, whether it has shipped, and completion status. New records are created and existing ones updated; none are deleted.	CommercientSF9__SOP10100__c, CommercientSF9__SOP10200__c, CommercientSF9__SOP30200__c, CommercientSF9__SOP30300__c	SF_ERP_Salesforce_Clone_SOP10100, SF_ERP_Salesforce_Clone_SOP10200, SF_ERP_Salesforce_Clone_SOP30200, SF_ERP_Salesforce_Clone_SOP30300

2. The process rows the templates create

Each template’s Insert_Query writes one CRM_Configuration row. These are the values it sets; a column the inserts never set is not listed.

Display name	CRM_Object_API_Name	CRM_PK_API_Name	Sync_Order	TimeStamp_Prefix	SQL_Query target	field prefix / postfix
Account	Account	CommercientSF__Commercient_ArCustomerCode__c	1	Account	1=0	'' / ''
Customer	CommercientSF9__RM00101__c	CommercientSF9__CUSTNMBR__c	2	RM00101	vw_MSDYNAMICGP2016_SalesForceRM00101	CommercientSF9__ / __C
Customer Master Address	CommercientSF9__RM00102__c	CommercientSF9__ExternalKey__c	3	RM00102	vw_MSDYNAMICGP2016_SalesForceRM00102	CommercientSF9__ / __C
Customer Master Summary	CommercientSF9__RM00103__c	CommercientSF9__CUSTNMBR__c	4	RM00103	vw_MSDYNAMICGP2016_SalesForceRM00103	CommercientSF9__ / __C
Customer Period Summary	CommercientSF9__RM00104__c	CommercientSF9__ExternalKey__c	5	RM00104	vw_MSDYNAMICGP2016_SalesForceRM00104	CommercientSF9__ / __C
Sales Transaction Works	CommercientSF9__SOP10100__c	CommercientSF9__ExternalKey__c	6	SOP10100	vw_MSDYNAMICGP2016_SalesForceSOP10100	CommercientSF9__ / __C
Sales Transaction Amounts Work	CommercientSF9__SOP10200__c	CommercientSF9__ExternalKey__c	7	SOP10200	vw_MSDYNAMICGP2016_SalesForceSOP10200	CommercientSF9__ / __C
Sales Transaction History	CommercientSF9__SOP30200__c	CommercientSF9__ExternalKey__c	8	SOP30200	vw_MSDYNAMICGP2016_SalesForceSOP30200	CommercientSF9__ / __C
Sales Transaction Amounts History	CommercientSF9__SOP30300__c	CommercientSF9__ExternalKey__c	9	SOP30300	vw_MSDYNAMICGP2016_SalesForceSOP30300	CommercientSF9__ / __C
Sale User Define & Track No Work History	CommercientSF9__SOP10106__c	CommercientSF9__ExternalKey__c	10	SOP10106	vw_MSDYNAMICGP2016_SalesForceSOP10106	CommercientSF9__ / __C
Invoicing Transaction Work	CommercientSF9__IVC10100__c	CommercientSF9__ExternalKey__c	11	IVC10100	vw_MSDYNAMICGP2016_SalesForceIVC10100	CommercientSF9__ / __C
Invoicing Transaction Amounts Work	CommercientSF9__IVC10101__c	CommercientSF9__ExternalKey__c	12	IVC10101	vw_MSDYNAMICGP2016_SalesForceIVC10101	CommercientSF9__ / __C
Invoicing Transaction History	CommercientSF9__IVC30101__c	CommercientSF9__ExternalKey__c	13	IVC30101	vw_MSDYNAMICGP2016_SalesForceIVC30101	CommercientSF9__ / __C
Invoicing Transaction Amounts History	CommercientSF9__IVC30102__c	CommercientSF9__ExternalKey__c	14	IVC30102	vw_MSDYNAMICGP2016_SalesForceIVC30102	CommercientSF9__ / __C
Invoicing Serial and Lot Number Work	CommercientSF9__IVC10102__c	CommercientSF9__ExternalKey__c	15	IVC10102	vw_MSDYNAMICGP2016_SalesForceIVC10102	CommercientSF9__ / __C
Invoicing Line Comments	CommercientSF9__IVC10103__c	CommercientSF9__ExternalKey__c	16	IVC10103	vw_MSDYNAMICGP2016_SalesForceIVC10103	CommercientSF9__ / __C
Invoicing Payments Work	CommercientSF9__IVC10200__c	CommercientSF9__ExternalKey__c	17	IVC10200	vw_MSDYNAMICGP2016_SalesForceIVC10200	CommercientSF9__ / __C
Product	Product2	CommercientSF__ExternalKey__c	18	vw_Product	vw_MSDYNAMICGP2016_Product	'' / ''
Item Master	CommercientSF9__IV00101__c	CommercientSF9__ExternalKey__c	19	IV00101	vw_MSDYNAMICGP2016_IV00101	CommercientSF9__ / __C
Item Quantity Master	CommercientSF9__IV00102__c	CommercientSF9__ExternalKey__c	20	IV00102	vw_MSDYNAMICGP2016_IV00102	CommercientSF9__ / __C
Product Item reverse lookup	Product2	CommercientSF__ExternalKey__c	21	vw_ProductReverseLookup	vw_MSDYNAMICGP2016_PRODUCT_REVERSE_LOOKUP	CommercientSF9__ / __C
Account Customer Reverse Lookup	Account	CommercientSF__Commercient_ArCustomerCode__c	22	Account_ReverseLookup	vw_MSDYNAMICGP2016_AccountReverseLookup	'' / ''
Create PriceBook	PricebookEntry	ExternalKey__c	23	vw_PriceBook	vw_MSDYNAMICGP2016_PriceBook_Create	'' / ''
Update PriceBook	PricebookEntry	ExternalKey__c	24	vw_PriceBook	vw_MSDYNAMICGP2016_PriceBook_Update	'' / ''

Every one of these inserts Is_Active as 0, so an imported process is inactive until an operator activates it. Across the set they insert Is_Create_Entity 0, Is_Create_Fields 0, Is_Active_Delete_Records 0, IsAccountMatching 1. Is_Active_Get_Records is set on Create PriceBook. The insert column lists do not include Sync_Operation_Type, Sync_Batch_Size, Document_Source_Path, so those columns take their CRM_Configuration defaults. Text columns a template does not use are inserted as '' rather than left NULL. Get_SOQL_Query carries a query on Account, Create PriceBook — those rows read records back from Salesforce as well as pushing. On Product Item reverse lookup the SQL_Query names a view the same template’s CreateViewQuery does not create (vw_MSDYNAMICGP2016_PRODUCT_REVERSE_LOOKUP against vw_MSDYNAMICGP2016_Product), so check the view exists under the name the row selects from before activating it.

3. The views

Each template creates its view with CreateViewQuery, in the gateway dbo schema. “Change detection” names which of the three kinds dlake-crmpro defines the view’s own WHERE makes it; where a view’s shape is not one of those three the column is left empty and the view’s own WHERE is the authority.

View	Change detection	Repository key	Reads other prefixes	Identity column	Source tables
vw_MSDYNAMICGP2016_SalesForceAccountExtract2	insert + update	Account:	—	—	CustomerCodeGUID, SF_ERP_Salesforce_Clone_RM00101, SF_ERP_Salesforce_Clone_RM00102
vw_MSDYNAMICGP2016_SalesForceRM00101	insert + update	RM00101:	Account:	—	SF_ERP_Salesforce_Clone_RM00101
vw_MSDYNAMICGP2016_SalesForceRM00102	insert + update	RM00102:	Account:, RM00101:	—	SF_ERP_Salesforce_Clone_RM00102
vw_MSDYNAMICGP2016_SalesForceRM00103	insert + update	RM00103:	Account:, RM00101:	—	SF_ERP_Salesforce_Clone_RM00103
vw_MSDYNAMICGP2016_SalesForceRM00104	insert + update	RM00104:	Account:, RM00101:	—	SF_ERP_Salesforce_Clone_RM00104
vw_MSDYNAMICGP2016_SalesForceSOP10100	insert + update	SOP10100:	Account:	—	SF_ERP_Salesforce_Clone_SOP10100
vw_MSDYNAMICGP2016_SalesForceSOP10200	insert + update	SOP10200:	SOP10100:	—	SF_ERP_Salesforce_Clone_SOP10200
vw_MSDYNAMICGP2016_SalesForceSOP30200	insert + update	SOP30200:	Account:, RM00101:	—	SF_ERP_Salesforce_Clone_SOP30200
vw_MSDYNAMICGP2016_SalesForceSOP30300	insert + update	SOP30300:	SOP30200:	—	SF_ERP_Salesforce_Clone_SOP30300
vw_MSDYNAMICGP2016_SalesForceSOP10106	insert + update	SOP10106:	SOP10100:, SOP30200:	—	SF_ERP_Salesforce_Clone_SOP10106, SF_ERP_Salesforce_Clone_SOP10107
vw_MSDYNAMICGP2016_SalesForceIVC10100	insert + update	IVC10100:	Account:, RM00101:	—	SF_ERP_Salesforce_Clone_IVC10100
vw_MSDYNAMICGP2016_SalesForceIVC10101	insert + update	IVC10101:	IVC10100:	—	SF_ERP_Salesforce_Clone_IVC10101
vw_MSDYNAMICGP2016_SalesForceIVC30101	insert + update	IVC30101:	Account:, RM00101:	—	SF_ERP_Salesforce_Clone_IVC30101
vw_MSDYNAMICGP2016_SalesForceIVC30102	insert + update	IVC30102:	IVC30101:	—	SF_ERP_Salesforce_Clone_IVC30102
vw_MSDYNAMICGP2016_SalesForceIVC10102	insert + update	IVC10102:	IVC10101:	—	SF_ERP_Salesforce_Clone_IVC10102
vw_MSDYNAMICGP2016_SalesForceIVC10103	insert + update	IVC10103:	IVC10100:	—	SF_ERP_Salesforce_Clone_IVC10103
vw_MSDYNAMICGP2016_SalesForceIVC10200	insert + update	IVC10200:	IVC30101:	—	SF_ERP_Salesforce_Clone_IVC10200
vw_MSDYNAMICGP2016_Product	insert + update	vw_Product:	—	CommercientSF__ExternalKey__c	SF_ERP_Salesforce_Clone_IV00101
vw_MSDYNAMICGP2016_IV00101	insert + update	IV00101:	vw_Product:	—	SF_ERP_Salesforce_Clone_IV00101
vw_MSDYNAMICGP2016_IV00102	insert + update	IV00102:	IV00101:, vw_Product:	—	SF_ERP_Salesforce_Clone_IV00102
vw_MSDYNAMICGP2016_Product	insert + update	—	vw_Product:	CommercientSF__ExternalKey__c	SF_ERP_Salesforce_Clone_IV00101
vw_MSDYNAMICGP2016_AccountReverseLookup	insert + update	Account_ReverseLookup:	RM00101:	—	SF_ERP_Salesforce_Clone_RM00101
vw_MSDYNAMICGP2016_PriceBook_Create	insert-only	vw_PriceBook:	vw_Product:	—	SF_ERP_Salesforce_Clone_IV00101, SF_ERP_Salesforce_Clone_IV00108
vw_MSDYNAMICGP2016_PriceBook_Update	insert + update	vw_PriceBook:	vw_Product:	—	SF_ERP_Salesforce_Clone_IV00101, SF_ERP_Salesforce_Clone_IV00108

The repository key these templates build is <TimeStamp_Prefix>:<key>. The literal in the view and the TimeStamp_Prefix on the configuration row have to be the same string, case included.

4. Order of work

The templates set Sync_Order from 1 to 24. A run processes active rows in ascending Sync_Order, which is the order the templates put them in:

• 1 — Account
• 2 — Customer
• 3 — Customer Master Address
• 4 — Customer Master Summary
• 5 — Customer Period Summary
• 6 — Sales Transaction Works
• 7 — Sales Transaction Amounts Work
• 8 — Sales Transaction History
• 9 — Sales Transaction Amounts History
• 10 — Sale User Define & Track No Work History
• 11 — Invoicing Transaction Work
• 12 — Invoicing Transaction Amounts Work
• 13 — Invoicing Transaction History
• 14 — Invoicing Transaction Amounts History
• 15 — Invoicing Serial and Lot Number Work
• 16 — Invoicing Line Comments
• 17 — Invoicing Payments Work
• 18 — Product
• 19 — Item Master
• 20 — Item Quantity Master
• 21 — Product Item reverse lookup
• 22 — Account Customer Reverse Lookup
• 23 — Create PriceBook
• 24 — Update PriceBook

These views read another process’s repository prefix, which is what makes the order a dependency order: the row appears in the view only once the process that writes that prefix has run, so a parent flows on one run and its children on the next.

• vw_MSDYNAMICGP2016_SalesForceSOP10106 reads SOP10100:, SOP30200:
• vw_MSDYNAMICGP2016_AccountReverseLookup reads RM00101:
• vw_MSDYNAMICGP2016_SalesForceRM00101 reads Account:
• vw_MSDYNAMICGP2016_SalesForceRM00102 reads Account:, RM00101:
• vw_MSDYNAMICGP2016_SalesForceRM00103 reads Account:, RM00101:
• vw_MSDYNAMICGP2016_SalesForceRM00104 reads Account:, RM00101:
• vw_MSDYNAMICGP2016_IV00101 reads vw_Product:
• vw_MSDYNAMICGP2016_IV00102 reads IV00101:, vw_Product:
• vw_MSDYNAMICGP2016_SalesForceIVC10100 reads Account:, RM00101:
• vw_MSDYNAMICGP2016_SalesForceIVC10101 reads IVC10100:
• vw_MSDYNAMICGP2016_SalesForceIVC30101 reads Account:, RM00101:
• vw_MSDYNAMICGP2016_SalesForceIVC30102 reads IVC30101:
• vw_MSDYNAMICGP2016_SalesForceIVC10102 reads IVC10101:
• vw_MSDYNAMICGP2016_SalesForceIVC10103 reads IVC10100:
• vw_MSDYNAMICGP2016_SalesForceIVC10200 reads IVC30101:
• vw_MSDYNAMICGP2016_PriceBook_Create reads vw_Product:
• vw_MSDYNAMICGP2016_PriceBook_Update reads vw_Product:
• vw_MSDYNAMICGP2016_Product reads vw_Product:
• vw_MSDYNAMICGP2016_SalesForceSOP10100 reads Account:
• vw_MSDYNAMICGP2016_SalesForceSOP10200 reads SOP10100:
• vw_MSDYNAMICGP2016_SalesForceSOP30200 reads Account:, RM00101:
• vw_MSDYNAMICGP2016_SalesForceSOP30300 reads SOP30200:

5. Field mapping

CRM_FieldList carries one row per pushed column, with Object_Name equal to the CRM_Object_API_Name value — as dlake-crmpro puts it, an object with no CRM_FieldList rows pushes nothing and records no error. Each template carries its intended mapping in MappingJson. Read that with dlake admin crmpro_templates, then check crmpro_field_mapping on the created process before activating it.

Template	Object	Mapped fields	First ERP → Salesforce pairs
Account	Account	14	CUSTNMBR → CommercientSF__Commercient_ArCustomerCode__c, CUSTNAME → Name, CustomerGUID → CommercientSF__Commercient_CustomerGUID__c, ADDRESS1,ADDRESS2,ADDRESS3 → BillingStreet, CITY → BillingCity
Customer	CommercientSF9__RM00101__c	98	CUSTNMBR → CommercientSF9__CUSTNMBR__c, CUSTNAME → Name, SFDCID → CommercientSF9__Account__c, CUSTCLAS → CUSTCLAS, CPRCSTNM → CPRCSTNM
Customer Master Address	CommercientSF9__RM00102__c	33	CUSTNMBR, ADRSCODE → CommercientSF9__ExternalKey__c, CUSTNMBR, ADRSCODE → CommercientSF9__Name__c, SFDCID → CommercientSF9__Account__c, SFDCID → CommercientSF9__RM00101__c, SLPRSNID → CommercientSF9__SLPRSNID__c
Customer Master Summary	CommercientSF9__RM00103__c	81	CUSTNMBR → CommercientSF9__CUSTNMBR__c, CUSTNMBR → Name, LASTAGED → CommercientSF9__LASTAGED__c, FRSTINDT → CommercientSF9__FRSTINDT__c, LSTNSFCD → CommercientSF9__LSTNSFCD__c
Customer Period Summary	CommercientSF9__RM00104__c	16	CUSTNMBR,PERIODID,YEAR1,HISTTYPE → CommercientSF9__ExternalKey__c, CUSTNMBR → CommercientSF9__Account__c, CUSTNMBR → CommercientSF9__RM00101__c, PERIODID → CommercientSF9__PERIODID__c, YEAR1 → CommercientSF9__YEAR1__c
Sales Transaction Works	CommercientSF9__SOP10100__c	91	SOPTYPE,SOPNUMBE → CommercientSF9__ExternalKey__c, CUSTNMBR → CommercientSF9__Account__c, ORIGNUMB → CommercientSF9__ORIGNUMB__c, DOCID → CommercientSF9__DOCID__c, DOCDATE → CommercientSF9__DOCDATE__c
Sales Transaction Amounts Work	CommercientSF9__SOP10200__c	96	SOPTYPE, SOPNUMBE, LNITMSEQ, CMPNTSEQ → ExternalKey, SOPTYPE, SOPNUMBE, LNITMSEQ, CMPNTSEQ → Name, SOPNUMBE → SOPNUMBE, SFDCID → SOP10100, ITEMNMBR → ITEMNMBR
Sales Transaction History	CommercientSF9__SOP30200__c	96	SOPTYPE, SOPNUMBE → CommercientSF9__ExternalKey__c, SOPTYPE, SOPNUMBE → CommercientSF9__Name__c, CUSTNMBR → Account, CUSTNMBR → RM00101, ORIGNUMB → CommercientSF9__ORIGNUMB__c
Sales Transaction Amounts History	CommercientSF9__SOP30300__c	95	SOPTYPE, SOPNUMBE, LNITMSEQ, CMPNTSEQ → CommercientSF9__ExternalKey__c, SOPTYPE, SOPNUMBE, LNITMSEQ, CMPNTSEQ → CommercientSF9__Name__c, SFDCID → CommercientSF9__SOP30200__c, ITEMNMBR → CommercientSF9__ITEMNMBR__c, ITEMDESC → CommercientSF9__ITEMDESC__c
Sale User Define & Track No Work History	CommercientSF9__SOP10106__c	21	SOPTYPE, SOPNUMBE → CommercientSF9__ExternalKey__c, SOPTYPE, SOPNUMBE → CommercientSF9__Name__c, SFDCID → SOP10100, SFDCID → SOP30200, SOPTYPE → CommercientSF9__SOPTYPE__c
Invoicing Transaction Work	CommercientSF9__IVC10100__c	104	DOCTYPE,INVCNMBR → CommercientSF9__ExternalKey__c, CUSTNMBR → CommercientSF9__Account__c, CUSTNMBR → RM00101, BACHNUMB → BACHNUMB, BCHSOURC → BCHSOURC
Invoicing Transaction Amounts Work	CommercientSF9__IVC10101__c	60	DOCTYPE,INVCNMBR,LNITMSEQ,CMPNTSEQ → CommercientSF9__ExternalKey__c, DOCTYPE,INVCNMBR,LNITMSEQ,CMPNTSEQ → CommercientSF9__Name__c, SFDCID → CommercientSF9__IVC10100__c, ITEMNMBR → CommercientSF9__ITEMNMBR__c, ITMTSHID → CommercientSF9__ITMTSHID__c
Invoicing Transaction History	CommercientSF9__IVC30101__c	94	DOCTYPE,INVCNMBR → CommercientSF9__ExternalKey__c, DOCTYPE,INVCNMBR → CommercientSF9__Name__c, CUSTNMBR → CommercientSF9__Account__c, CUSTNMBR → RM00101, BACHNUMB → BACHNUMB
Invoicing Transaction Amounts History	CommercientSF9__IVC30102__c	48	DOCTYPE,INVCNMBR,LNITMSEQ,CMPNTSEQ → CommercientSF9__ExternalKey__c, DOCTYPE,INVCNMBR,LNITMSEQ,CMPNTSEQ → CommercientSF9__Name__c, IVC30101 → CommercientSF9__IVC30101__c, ITEMNMBR → CommercientSF9__ITEMNMBR__c, ITMTSHID → CommercientSF9__ITMTSHID__c
Invoicing Serial and Lot Number Work	CommercientSF9__IVC10102__c	14	INVCNMBR,DOCTYPE,CMPNTSEQ,LNITMSEQ,QTYTYPE,SLTSQNUM → CommercientSF9__ExternalKey__c, INVCNMBR,DOCTYPE,CMPNTSEQ,LNITMSEQ,QTYTYPE,SLTSQNUM → CommercientSF9__Name__c, SFDCID → CommercientSF9__IVC10101__c, ITEMNMBR → CommercientSF9__ITEMNMBR__c, SERLTNUM → CommercientSF9__SERLTNUM__c
Invoicing Line Comments	CommercientSF9__IVC10103__c	8	DOCTYPE,INVCNMBR,LNITMSEQ → CommercientSF9__ExternalKey__c, DOCTYPE,INVCNMBR,LNITMSEQ → CommercientSF9__Name__c, SFDCID → IVC10100, COMMENT_1 → COMMENT_1, COMMENT_2 → COMMENT_2
Invoicing Payments Work	CommercientSF9__IVC10200__c	16	DOCTYPE,INVCNMBR,SEQNUMBR → CommercientSF9__ExternalKey__c, SFDCID → CommercientSF9__IVC30101__c, DOCNUMBR → DOCNUMBR, CURNCYID → CURNCYID, CHEKBKID → CHEKBKID
Product	Product2	5	ITEMNMBR → CommercientSF__ExternalKey__c, ITEMDESC → Name, ITEMNMBR → ProductCode, ITEMDESC → Description, INACTIVE → IsActive
Item Master	CommercientSF9__IV00101__c	91	ITEMNMBR → CommercientSF9__ExternalKey__c, ITEMNMBR → Name, SFDCID → Product, ITEMNMBR → ITEMNMBR, ITEMDESC → ITEMDESC
Item Quantity Master	CommercientSF9__IV00102__c	81	ITEMNMBR, LOCNCODE, RCRDTYPE → CommercientSF9__ExternalKey__c, ITEMNMBR, LOCNCODE, RCRDTYPE → CommercientSF9__Name__c, SFDCID → CommercientSF9__Item_Master__c, SFDCID → CommercientSF9__Product__c, LOCNCODE → CommercientSF9__LOCNCODE__c
Product Item reverse lookup	Product2	5	ITEMNMBR → CommercientSF__ExternalKey__c, ITEMDESC → Name, ITEMNMBR → ProductCode, ITEMDESC → Description, INACTIVE → IsActive
Account Customer Reverse Lookup	Account	2	CUSTNMBR → CommercientSF__Commercient_ArCustomerCode__c, SFDCID → CommercientSF9__Customer__c
Create PriceBook	PricebookEntry	5	PRCLEVEL, ITEMNMBR → ExternalKey__c, SFDCID → Pricebook2Id, SFDCID → Product2Id, IsActive → IsActive, UOMPRICE → UnitPrice
Update PriceBook	PricebookEntry	3	PRCLEVEL, ITEMNMBR → ExternalKey__c, UOMPRICE → UnitPrice, IsActive → IsActive

6. Community templates

The catalogue carries 39 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. They are not part of the shipped set described above.

• Templates: 39
• Default operations: insert on 39, update on 39, delete on 39
• Marked circular-sync: 0
• Licence groups they span: 10
• Destination objects: Account, PricebookEntry, Product2, Contact and 22 custom objects
• Object display names: Account, Account Customer Reverse Lookup, Customer, Customer Master Address, Customer Master Summary, Customer Period Summary, Sales Transaction Amounts History, Sales Transaction Amounts Work, Sales Transaction History, Sales Transaction Works, AR Invoice Payments, Create PriceBook and 17 more
• Template groups: Account, Product, Customer Multi Ship Addresses, AR Invoice Payments, Invoice, Open AR Invoice Header

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.

7. 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 ::.

The prefixes these templates set:

• SOP10106
• Account
• Account_ReverseLookup
• RM00101
• RM00102
• RM00103
• RM00104
• IV00101
• IV00102
• IVC10100
• IVC10101
• IVC30101
• IVC30102
• IVC10102
• IVC10103
• IVC10200
• vw_PriceBook
• vw_Product
• vw_ProductReverseLookup
• SOP10100
• SOP10200
• SOP30200
• SOP30300

8. 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 shipped Microsoft Dynamics GP 2016 → Salesforce templates set up. dlake-crmpro-salesforce is the destination skill this page sits under: its own text is the authority for the Salesforce 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.