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

CRMPro → Salesforce — Microsoft Dynamics GP 2017: 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-2017.md, and that skill’s ERP table is what points at it. What follows is only what the shipped Microsoft Dynamics GP 2017 → 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
MSD_GP Dynamic_GP	The templates push Dynamics_GP__c to Salesforce. New records are created and existing ones updated; none are deleted.	Dynamics_GP__c	SF_ERP_Salesforce_Clone_IV00200, SF_ERP_Salesforce_Clone_IV00101, SF_ERP_Salesforce_Clone_IV40700, SF_ERP_Salesforce_Clone_GL40200
SYNC SALES TRANSACTION HISTORY	ERP SOP10106, SOP10100, SOP30200 data becomes CommercientSF9__SOP30200__c in Salesforce. New records are created, existing ones updated, and records removed in the ERP are deleted.	CommercientSF9__SOP30200__c	SF_ERP_Salesforce_Clone_sop10100, SF_ERP_Salesforce_Clone_SOP10106, CommercientFlags, SF_ERP_Salesforce_Clone_sop30200, SF_ERP_Salesforce_Clone_RM20101, SF_ERP_Salesforce_Clone_RM30101
SYNC SALES TRANSACTION AMOUNT HISTORY	ERP SOP10200, SOP30300 data becomes CommercientSF9__SOP30300__c in Salesforce. New records are created, existing ones updated, and records removed in the ERP are deleted.	CommercientSF9__SOP30300__c	SF_ERP_Salesforce_Clone_sop30300, SF_ERP_Salesforce_Clone_sop10200
GET USER	The templates push users to Salesforce. New records are created, existing ones updated, and records removed in the ERP are deleted.	users	—
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, existing ones updated, and records removed in the ERP are deleted.	Account, Contact, CommercientSF9__RM00101__c	SF_ERP_Salesforce_Clone_RM00101, SF_ERP_Salesforce_Clone_RM00102
CRM Ownership	The templates push users to Salesforce. New records are created and existing ones updated; none are deleted.	users	—
Customer Multi Ship Addresses	If you are using multiple ship to addresses for a given AR Customer in your ERP system then you will be able to see all the addresses inside the CRM Account screen in a Commercient Multi Ship To Address MCO related list. New records are created, existing ones updated, and records removed in the ERP are deleted.	CommercientSF9__RM00102__c	SF_ERP_Salesforce_Clone_RM00102
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, existing ones updated, and records removed in the ERP are deleted.	CommercientSF9__SOP10100__c, CommercientSF9__SOP10200__c	SF_ERP_Salesforce_Clone_sop10100, SF_ERP_Salesforce_Clone_sop10200

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	Sync_Operation_Type
GET USER	users	—	0	vw_user	1=0	'' / ''	1
GET USER	users	—	0	vw_user	1=0	'' / ''	—
MSD_GP Dynamic_GP	Dynamics_GP__c	ExternalKey__c	1	vw_MSDYNAMICGP2017_Dynamic_GP	vw_MSDYNAMICGP2017_Dynamic_GP	'' / ''	—
SYNC ACCOUNT	Account	CommercientSF__Commercient_ArCustomerCode__c	1	vw_MSDYNAMICGP2017_Account	vw_MSDYNAMICGP2017_Account	'' / ''	1
SYNC CUSTOMER	CommercientSF9__RM00101__c	CommercientSF9__CUSTNMBR__c	2	vw_MSDYNAMICGP2017_Customer	vw_MSDYNAMICGP2017_Customer	CommercientSF9__ / __c	1
SYNC CUSTOMER TO ACCOUNT LOOKUP	Account	CommercientSF__Commercient_ArCustomerCode__c	3	vw_MSDYNAMICGP2017_CustomerToAccountLookup	vw_MSDYNAMICGP2017_CustomerToAccountLookup	'' / ''	1
SYNC SHIPTOADDRESS	CommercientSF9__RM00102__c	CommercientSF9__ExternalKey__c	5	vw_MSDYNAMICGP2017_ShipToAddress	vw_MSDYNAMICGP2017_ShipToAddress	CommercientSF9__ / __c	1
SYNC CONTACT	Contact	ExternalKey__c	6	vw_MSDYNAMICGP2017_Contact	vw_MSDYNAMICGP2017_Contact	'' / ''	1
SYNC SALES ORDER HEADER	CommercientSF9__SOP10100__c	CommercientSF9__ExternalKey__c	7	vw_MSDYNAMICGP2017_SalesOrderHeader	vw_MSDYNAMICGP2017_SalesOrderHeader	CommercientSF9__ / __c	1
SYNC SALESORDERDETAIL	CommercientSF9__SOP10200__c	CommercientSF9__ExternalKey__c	8	vw_MSDYNAMICGP2017_SalesOrderDetail	vw_MSDYNAMICGP2017_SalesOrderDetail	CommercientSF9__ / __c	1
SYNC SALES TRANSACTION HISTORY	CommercientSF9__SOP30200__c	CommercientSF9__ExternalKey__c	9	vw_MSDYNAMICGP2017_SalesTransactionHistory	vw_MSDYNAMICGP2017_SalesTransactionHistory	CommercientSF9__ / __c	1
SYNC SALES TRANSACTION AMOUNT HISTORY	CommercientSF9__SOP30300__c	CommercientSF9__ExternalKey__c	10	vw_MSDYNAMICGP2017_SalesTransactionAmountHistory	vw_MSDYNAMICGP2017_SalesTransactionAmountHistory	CommercientSF9__ / __c	1

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_Get_Records 0, Is_Active_Delete_Records 0, IsAccountMatching False, Sync_Batch_Size 200. Text columns a template does not use are inserted as '' rather than left NULL. Get_SOQL_Query carries a query on GET USER, SYNC ACCOUNT, GET USER — those rows read records back from Salesforce as well as pushing.

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_MSDYNAMICGP2017_Dynamic_GP	insert-only	vw_MSDYNAMICGP2017_Dynamic_GP:	—	ExternalKey__c	SF_ERP_Salesforce_Clone_IV00200, SF_ERP_Salesforce_Clone_IV00101, SF_ERP_Salesforce_Clone_IV40700, SF_ERP_Salesforce_Clone_GL40200
vw_MSDYNAMICGP2017_Account	insert + update	vw_MSDYNAMICGP2017_Account:	vw_user:	—	SF_ERP_Salesforce_Clone_RM00101, SF_ERP_Salesforce_Clone_RM00102
vw_MSDYNAMICGP2017_Customer	insert + update	vw_MSDYNAMICGP2017_Customer:	vw_MSDYNAMICGP2017_Account:	ExternalKey	SF_ERP_Salesforce_Clone_RM00101
vw_MSDYNAMICGP2017_CustomerToAccountLookup	insert + update	vw_MSDYNAMICGP2017_CustomerToAccountLookup:	vw_MSDYNAMICGP2017_Customer:	CommercientSF__Commercient_ArCustomerCode__c	SF_ERP_Salesforce_Clone_RM00101
vw_MSDYNAMICGP2017_ShipToAddress	insert + update	vw_MSDYNAMICGP2017_ShipToAddress:	vw_MSDYNAMICGP2017_Account:, vw_MSDYNAMICGP2017_Customer:	—	SF_ERP_Salesforce_Clone_RM00102
vw_MSDYNAMICGP2017_Contact	insert + update	vw_MSDYNAMICGP2017_Contact:	vw_MSDYNAMICGP2017_Account:, vw_MSDYNAMICGP2017_Customer:	ExternalKey__c	SF_ERP_Salesforce_Clone_RM00102, SF_ERP_Salesforce_Clone_RM00101
vw_MSDYNAMICGP2017_SalesOrderHeader	insert + update	vw_MSDYNAMICGP2017_SalesOrderHeader:	vw_MSDYNAMICGP2017_Account:, vw_MSDYNAMICGP2017_Customer:	—	SF_ERP_Salesforce_Clone_sop10100
vw_MSDYNAMICGP2017_SalesOrderDetail	insert + update	vw_MSDYNAMICGP2017_SalesOrderDetail:	vw_MSDYNAMICGP2017_SalesOrderHeader:	—	SF_ERP_Salesforce_Clone_sop10200
vw_MSDYNAMICGP2017_SalesTransactionHistory	insert + update	vw_MSDYNAMICGP2017_SalesTransactionHistory:	vw_MSDYNAMICGP2017_Account:, vw_user:	ExternalKey	SF_ERP_Salesforce_Clone_sop10100, SF_ERP_Salesforce_Clone_SOP10106, CommercientFlags, SF_ERP_Salesforce_Clone_sop30200, SF_ERP_Salesforce_Clone_RM20101
vw_MSDYNAMICGP2017_SalesTransactionAmountHistory	insert + update	vw_MSDYNAMICGP2017_SalesTransactionAmountHistory:	vw_MSDYNAMICGP2017_SalesTransactionHistory:	—	SF_ERP_Salesforce_Clone_sop30300, SF_ERP_Salesforce_Clone_sop10200

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 0 to 10. A run processes active rows in ascending Sync_Order, which is the order the templates put them in:

• 0 — GET USER
• 1 — MSD_GP Dynamic_GP, SYNC ACCOUNT
• 2 — SYNC CUSTOMER
• 3 — SYNC CUSTOMER TO ACCOUNT LOOKUP
• 5 — SYNC SHIPTOADDRESS
• 6 — SYNC CONTACT
• 7 — SYNC SALES ORDER HEADER
• 8 — SYNC SALESORDERDETAIL
• 9 — SYNC SALES TRANSACTION HISTORY
• 10 — SYNC SALES TRANSACTION AMOUNT HISTORY

Several of these rows share a Sync_Order value: each template group carries its own numbering, so give the imported processes an order across the whole set rather than taking the template values as one.

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_MSDYNAMICGP2017_SalesTransactionHistory reads vw_MSDYNAMICGP2017_Account:, vw_user:
• vw_MSDYNAMICGP2017_SalesTransactionAmountHistory reads vw_MSDYNAMICGP2017_SalesTransactionHistory:
• vw_MSDYNAMICGP2017_Account reads vw_user:
• vw_MSDYNAMICGP2017_CustomerToAccountLookup reads vw_MSDYNAMICGP2017_Customer:
• vw_MSDYNAMICGP2017_Contact reads vw_MSDYNAMICGP2017_Account:, vw_MSDYNAMICGP2017_Customer:
• vw_MSDYNAMICGP2017_Customer reads vw_MSDYNAMICGP2017_Account:
• vw_MSDYNAMICGP2017_ShipToAddress reads vw_MSDYNAMICGP2017_Account:, vw_MSDYNAMICGP2017_Customer:
• vw_MSDYNAMICGP2017_SalesOrderHeader reads vw_MSDYNAMICGP2017_Account:, vw_MSDYNAMICGP2017_Customer:
• vw_MSDYNAMICGP2017_SalesOrderDetail reads vw_MSDYNAMICGP2017_SalesOrderHeader:

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
MSD_GP Dynamic_GP	Dynamics_GP__c	14	ITEMNMBR,LOCNCODE,DATERECD,DTSEQNUM,QTYTYPE → ExternalKey__c, ITEMNMBR,LOCNCODE,DATERECD,DTSEQNUM,QTYTYPE → Name, ITEMDESC → Item_Description__c, ITMSHNAM → Item_Short_Name__c, ITMCLSCD → Item_Class_Code__c
SYNC ACCOUNT	Account	23	CommercientSFommercient_ArCustomerCode → CommercientSF__Commercient_ArCustomerCode__c, ShippingStreet → ShippingStreet, ShippingCity → ShippingCity, ShippingStateCode → ShippingStateCode, ShippingCountry → ShippingCountry
SYNC CUSTOMER	CommercientSF9__RM00101__c	104	CUSTNMBR → CommercientSF9__CUSTNMBR__c, ADDRESS1 → CommercientSF9__ADDRESS1__c, ADDRESS2 → CommercientSF9__ADDRESS2__c, ADDRESS3 → CommercientSF9__ADDRESS3__c, ADRSCODE → ADRSCODE
SYNC CUSTOMER TO ACCOUNT LOOKUP	Account	2	CommercientSFommercient_ArCustomerCode → CommercientSF__Commercient_ArCustomerCode__c, CommercientSF9ustomer → CommercientSF9__Customer__c
SYNC SHIPTOADDRESS	CommercientSF9__RM00102__c	31	SLPRSNID → CommercientSF9__SLPRSNID__c, UPSZONE → CommercientSF9__UPSZONE__c, SHIPMTHD → CommercientSF9__SHIPMTHD__c, TAXSCHID → TAXSCHID, CNTCPRSN → CNTCPRSN
SYNC CONTACT	Contact	9	LastName → LastName, Phone → Phone, Fax → Fax, MailingStreet → MailingStreet, MailingCity → MailingCity
SYNC SALES ORDER HEADER	CommercientSF9__SOP10100__c	91	ORIGNUMB → CommercientSF9__ORIGNUMB__c, DOCID → DOCID, DOCDATE → DOCDATE, QUOTEDAT → CommercientSF9__QUOTEDAT__c, QUOEXPDA → CommercientSF9__QUOEXPDA__c
SYNC SALESORDERDETAIL	CommercientSF9__SOP10200__c	94	SOPNUMBE → CommercientSF9__SOPNUMBE__c, ITEMNMBR → CommercientSF9__ITEMNMBR__c, ITEMDESC → ITEMDESC, UOFM → CommercientSF9__UOFM__c, LOCNCODE → LOCNCODE
SYNC SALES TRANSACTION HISTORY	CommercientSF9__SOP30200__c	18	GP_Invoice_Number → GP_Invoice_Number__c, PO_Number → PO_Number__c, CNTCPRSN → CNTCPRSN, SHIPMTHD → CommercientSF9__SHIPMTHD__c, SUBTOTAL → CommercientSF9__SUBTOTAL__c
SYNC SALES TRANSACTION AMOUNT HISTORY	CommercientSF9__SOP30300__c	10	ITEMNMBR → CommercientSF9__ITEMNMBR__c, ITEMDESC → ITEMDESC, UNITPRCE → UNITPRCE, XTNDPRCE → XTNDPRCE, Discount_Amount → Discount_Amount

6. Community templates

The catalogue carries 32 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: 32
• Default operations: insert on 32, update on 32, delete on 32
• Marked circular-sync: 0
• Licence groups they span: 8
• Destination objects: Account, Contact, PriceBookEntry, Product2, Tracking_Number__c, Dynamics_GP__c, Pricebook2, User, users and 9 custom objects
• Object display names: GET USER, SYNC ACCOUNT, SYNC CONTACT, SYNC CUSTOMER, SYNC CUSTOMER TO ACCOUNT LOOKUP, SYNC SALES ORDER HEADER, SYNC SALES TRANSACTION AMOUNT HISTORY, SYNC SALES TRANSACTION HISTORY, SYNC SALESORDERDETAIL, SYNC SHIPTOADDRESS, SYNC TRACKINGNUMBER, MSD_GP Dynamic_GP and 9 more
• Template groups: Account, Product, Salesorder, Customer Multi Ship Addresses

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:

• vw_MSDYNAMICGP2017_Dynamic_GP
• vw_MSDYNAMICGP2017_SalesTransactionHistory
• vw_MSDYNAMICGP2017_SalesTransactionAmountHistory
• vw_user
• vw_MSDYNAMICGP2017_Account
• vw_MSDYNAMICGP2017_CustomerToAccountLookup
• vw_MSDYNAMICGP2017_Contact
• vw_MSDYNAMICGP2017_Customer
• vw_MSDYNAMICGP2017_ShipToAddress
• vw_MSDYNAMICGP2017_SalesOrderHeader
• vw_MSDYNAMICGP2017_SalesOrderDetail

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 2017 → 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.