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

CRMPro → Salesforce — Microsoft Dynamics NAV: 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-nav.md, and that skill’s ERP table is what points at it. What follows is only what the shipped Microsoft Dynamics NAV → 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
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__MSDYNAMICNAV_CUSTOMER__c	SF_ERP_Salesforce_Clone_COP, SF_ERP_Salesforce_Clone_Globe_Scientific__Inc_
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.	Commercient_MSDYNAMICSNAV_ShipToAddress__c, CommercientSF9__MSDYNAMICNAV_SHIPMENTHEADERS__c, CommercientSF9__MSDYNAMICNAV_SHIPMENTLINES__c	SF_ERP_Salesforce_Clone_COP, CommercientFlags
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, existing ones updated, and records removed in the ERP are deleted.	CommercientSF9__MSDYNAMICNAV_INVOICEHEADER__c, CommercientSF9__MSDYNAMICNAV_INVOICELINES__c	SF_ERP_Salesforce_Clone_COP, CommercientFlags
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__MSDYNAMICNAV_ORDERHEADER__c, CommercientSF9__MSDYNAMICNAV_ORDERLINES__c	SF_ERP_Salesforce_Clone_COP, CommercientFlags

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
SYNC ACCOUNT	Account	CommercientSF__Commercient_ArCustomerCode__c	1	vw_MSDYNAMICNAV_Account	vw_MSDYNAMICNAV_Account	'' / ''	1
SYNC CUSTOMER	CommercientSF9__MSDYNAMICNAV_CUSTOMER__c	CommercientSF9__ExternalKey__c	2	vw_MSDYNAMICNAV_Customer	vw_MSDYNAMICNAV_Customer	CommercientSF9__ / __c	1
SYNC CUSTOMER TO ACCOUNT LOOKUP	Account	CommercientSF__Commercient_ArCustomerCode__c	3	vw_MSDYNAMICNAV_CustomerToAccountLookup	vw_MSDYNAMICNAV_CustomerToAccountLookup	'' / ''	1
SYNC SHIP TO ADDRESS	Commercient_MSDYNAMICSNAV_ShipToAddress__c	ExternalKey__c	4	vw_MSDYNAMICNAV_ShipToAddress	vw_MSDYNAMICNAV_ShipToAddress	'' / __c	1
SYNC SALES ORDER HEADER	CommercientSF9__MSDYNAMICNAV_ORDERHEADER__c	CommercientSF9__ExternalKey__c	6	vw_MSDYNAMICNAV_SalesOrderHeader	vw_MSDYNAMICNAV_SalesOrderHeader	CommercientSF9__ / __c	1
SYNC SALES ORDER DETAIL	CommercientSF9__MSDYNAMICNAV_ORDERLINES__c	CommercientSF9__ExternalKey__c	7	vw_MSDYNAMICNAV_SalesOrderDetail	vw_MSDYNAMICNAV_SalesOrderDetail	CommercientSF9__ / __c	1
SYNC INVOICE HEADER	CommercientSF9__MSDYNAMICNAV_INVOICEHEADER__c	CommercientSF9__ExternalKey__c	8	vw_MSDYNAMICNAV_InvoiceHeader	vw_MSDYNAMICNAV_InvoiceHeader	CommercientSF9__ / __c	1
SYNC INVOICE DETAIL	CommercientSF9__MSDYNAMICNAV_INVOICELINES__c	CommercientSF9__ExternalKey__c	9	vw_MSDYNAMICNAV_InvoiceDetail	vw_MSDYNAMICNAV_InvoiceDetail	CommercientSF9__ / __c	1
SYNC SHIPMENT HEADER	CommercientSF9__MSDYNAMICNAV_SHIPMENTHEADERS__c	CommercientSF9__ExternalKey__c	10	vw_MSDYNAMICNAV_ShipmentHeader	vw_MSDYNAMICNAV_ShipmentHeader	CommercientSF9__ / __c	1
SYNC SHIPMENT DETAIL	CommercientSF9__MSDYNAMICNAV_SHIPMENTLINES__c	CommercientSF9__ExternalKey__c	11	vw_MSDYNAMICNAV_ShipmentDetail	vw_MSDYNAMICNAV_ShipmentDetail	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. Text columns a template does not use are inserted as '' rather than left NULL. Get_SOQL_Query carries a query on SYNC ACCOUNT — 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_MSDYNAMICNAV_Contact	insert + update	—	vw_MSDYNAMICNAV_Account:, vw_MSDYNAMICNAV_Contact:	ExternalKey__c	SF_ERP_Salesforce_Clone_Globe_Scientific__Inc_
vw_MSDYNAMICNAV_Account	insert + update	vw_MSDYNAMICNAV_Account:	—	CommercientSF__Commercient_ArCustomerCode__c	SF_ERP_Salesforce_Clone_COP
vw_MSDYNAMICNAV_Customer	insert + update	vw_MSDYNAMICNAV_Customer:	vw_MSDYNAMICNAV_Account:	ExternalKey	SF_ERP_Salesforce_Clone_COP
vw_MSDYNAMICNAV_CustomerToAccountLookup	insert + update	vw_MSDYNAMICNAV_CustomerToAccountLookup:	vw_MSDYNAMICNAV_Customer:	—	SF_ERP_Salesforce_Clone_COP
vw_MSDYNAMICNAV_ShipToAddress	insert + update	vw_MSDYNAMICNAV_ShipToAddress:	vw_MSDYNAMICNAV_Account:, vw_MSDYNAMICNAV_Customer:	ExternalKey	SF_ERP_Salesforce_Clone_COP
vw_MSDYNAMICNAV_SalesOrderHeader	insert + update	vw_MSDYNAMICNAV_SalesOrderHeader:	vw_MSDYNAMICNAV_Account:, vw_MSDYNAMICNAV_Customer:	ExternalKey	SF_ERP_Salesforce_Clone_COP, CommercientFlags
vw_MSDYNAMICNAV_SalesOrderDetail	insert + update	vw_MSDYNAMICNAV_SalesOrderDetail:	vw_MSDYNAMICNAV_SalesOrderHeader:	ExternalKey	SF_ERP_Salesforce_Clone_COP
vw_MSDYNAMICNAV_InvoiceHeader	insert + update	vw_MSDYNAMICNAV_InvoiceHeader:	vw_MSDYNAMICNAV_Account:, vw_MSDYNAMICNAV_Customer:	ExternalKey	SF_ERP_Salesforce_Clone_COP, CommercientFlags
vw_MSDYNAMICNAV_InvoiceDetail	insert + update	vw_MSDYNAMICNAV_InvoiceDetail:	vw_MSDYNAMICNAV_InvoiceHeader:	ExternalKey	SF_ERP_Salesforce_Clone_COP
vw_MSDYNAMICNAV_ShipmentHeader	insert + update	vw_MSDYNAMICNAV_ShipmentHeader:	vw_MSDYNAMICNAV_Account:, vw_MSDYNAMICNAV_Customer:	ExternalKey	SF_ERP_Salesforce_Clone_COP, CommercientFlags
vw_MSDYNAMICNAV_ShipmentDetail	insert + update	vw_MSDYNAMICNAV_ShipmentDetail:	vw_MSDYNAMICNAV_ShipmentHeader:	ExternalKey	SF_ERP_Salesforce_Clone_COP

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

• 1 — SYNC ACCOUNT
• 2 — SYNC CUSTOMER
• 3 — SYNC CUSTOMER TO ACCOUNT LOOKUP
• 4 — SYNC SHIP TO ADDRESS
• 6 — SYNC SALES ORDER HEADER
• 7 — SYNC SALES ORDER DETAIL
• 8 — SYNC INVOICE HEADER
• 9 — SYNC INVOICE DETAIL
• 10 — SYNC SHIPMENT HEADER
• 11 — SYNC SHIPMENT DETAIL

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_MSDYNAMICNAV_CustomerToAccountLookup reads vw_MSDYNAMICNAV_Customer:
• vw_MSDYNAMICNAV_Contact reads vw_MSDYNAMICNAV_Account:, vw_MSDYNAMICNAV_Contact:; no template in this set writes vw_MSDYNAMICNAV_Contact:
• vw_MSDYNAMICNAV_Customer reads vw_MSDYNAMICNAV_Account:
• vw_MSDYNAMICNAV_ShipToAddress reads vw_MSDYNAMICNAV_Account:, vw_MSDYNAMICNAV_Customer:
• vw_MSDYNAMICNAV_ShipmentHeader reads vw_MSDYNAMICNAV_Account:, vw_MSDYNAMICNAV_Customer:
• vw_MSDYNAMICNAV_ShipmentDetail reads vw_MSDYNAMICNAV_ShipmentHeader:
• vw_MSDYNAMICNAV_InvoiceHeader reads vw_MSDYNAMICNAV_Account:, vw_MSDYNAMICNAV_Customer:
• vw_MSDYNAMICNAV_InvoiceDetail reads vw_MSDYNAMICNAV_InvoiceHeader:
• vw_MSDYNAMICNAV_SalesOrderHeader reads vw_MSDYNAMICNAV_Account:, vw_MSDYNAMICNAV_Customer:
• vw_MSDYNAMICNAV_SalesOrderDetail reads vw_MSDYNAMICNAV_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
SYNC CONTACT	Contact	11	AccountId → AccountId, LastName → LastName, FirstName → FirstName, Email → Email, MailingStreet → MailingStreet
SYNC ACCOUNT	Account	12	CommercientSFommercient_ArCustomerCode → CommercientSF__Commercient_ArCustomerCode__c, BillingStreet → BillingStreet, BillingCity → BillingCity, BillingState → BillingState, BillingCountry → BillingCountry
SYNC CUSTOMER	CommercientSF9__MSDYNAMICNAV_CUSTOMER__c	54	No → CommercientSF9__No__c, Name2 → CommercientSF9__Name2__c, Address → CommercientSF9__Address__c, Address2 → CommercientSF9__Address2__c, City → CommercientSF9__City__c
SYNC CUSTOMER TO ACCOUNT LOOKUP	Account	2	CommercientSFommercient_ArCustomerCode → CommercientSF__Commercient_ArCustomerCode__c, MSDYNAMICS_NAV_Customers → MSDYNAMICS_NAV_Customers__c
SYNC SHIP TO ADDRESS	Commercient_MSDYNAMICSNAV_ShipToAddress__c	27	CustomerNo → customerno__c, Code → Code__c, Name2 → Name2__c, Address → Address__c, Address2 → Address2__c
SYNC SALES ORDER HEADER	CommercientSF9__MSDYNAMICNAV_ORDERHEADER__c	59	DocumentType → DocumentType, No → CommercientSF9__No__c, SelltoCustomerNo → SelltoCustomerNo, BilltoCustomerNo → BilltoCustomerNo, BilltoName → CommercientSF9__BilltoName__c
SYNC SALES ORDER DETAIL	CommercientSF9__MSDYNAMICNAV_ORDERLINES__c	79	DocumentType → DocumentType, DocumentNo → DocumentNo, LineNo → CommercientSF9__LineNo__c, SelltoCustomerNo → SelltoCustomerNo, Type → CommercientSF9__Type__c
SYNC INVOICE HEADER	CommercientSF9__MSDYNAMICNAV_INVOICEHEADER__c	55	No → CommercientSF9__No__c, SelltoCustomerNo → SelltoCustomerNo, BilltoCustomerNo → BilltoCustomerNo, BilltoName → CommercientSF9__BilltoName__c, BilltoAddress → CommercientSF9__BilltoAddress__c
SYNC INVOICE DETAIL	CommercientSF9__MSDYNAMICNAV_INVOICELINES__c	52	DocumentNo → DocumentNo, LineNo → CommercientSF9__LineNo__c, SelltoCustomerNo → SelltoCustomerNo, Type → CommercientSF9__Type__c, No → CommercientSF9__No__c
SYNC SHIPMENT HEADER	CommercientSF9__MSDYNAMICNAV_SHIPMENTHEADERS__c	61	No → CommercientSF9__No__c, SelltoCustomerNo → SelltoCustomerNo, BilltoCustomerNo → BilltoCustomerNo, BilltoName → CommercientSF9__BilltoName__c, BilltoAddress → CommercientSF9__BilltoAddress__c
SYNC SHIPMENT DETAIL	CommercientSF9__MSDYNAMICNAV_SHIPMENTLINES__c	58	DocumentNo → DocumentNo, LineNo → CommercientSF9__LineNo__c, SelltoCustomerNo → SelltoCustomerNo, Type → CommercientSF9__Type__c, No → CommercientSF9__No__c

6. Community templates

The catalogue carries 134 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: 134
• Default operations: insert on 134, update on 134, delete on 134
• Marked circular-sync: 5
• Licence groups they span: 14
• Destination objects: Account, CommercientSF9__MSDYNAMICNAV_CUSTOMER__c, CommercientSF9__MSDYNAMICNAV_INVOICEHEADER__c, CommercientSF9__MSDYNAMICNAV_ORDERHEADER__c, CommercientSF9__MSDYNAMICNAV_INVOICELINES__c, CommercientSF9__MSDYNAMICNAV_ORDERLINES__c, PricebookEntry, Product2, Contact, CommercientSF9__MSDYNAMICNAV_ADDRESS__c, CommercientSF9__MSDYNAMICNAV_SHIPMENTHEADERS__c, CommercientSF9__MSDYNAMICNAV_SHIPMENTLINES__c, Asset, CommercientSF9__MSDYNAMICNAV_Item__c, PriceBook2, Commercient_MSDYNAMICSNAV_ShipToAddress__c, Dimension_Value__c, Invoice_Payment__c, Opportunity, Payment_Terms__c, 8 more and 9 custom objects
• Object display names: SYNC ACCOUNT, SYNC CUSTOMER, SYNC CUSTOMER TO ACCOUNT LOOKUP, SYNC INVOICE DETAIL, SYNC INVOICE HEADER, SYNC SALES ORDER DETAIL, SYNC SALES ORDER HEADER, SYNC SHIP TO ADDRESS, SYNC CONTACT, SYNC SHIPMENT DETAIL, SYNC SHIPMENT HEADER, Product, 36 more and a further template
• Template groups: Account, Product, Customer Multi Ship Addresses, Invoice, Salesorder, CRM Quote and Line, CRM Opportunity and Line, Opportunity, QuoteLine

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_MSDYNAMICNAV_Account
• vw_MSDYNAMICNAV_CustomerToAccountLookup
• vw_MSDYNAMICNAV_Customer
• vw_MSDYNAMICNAV_ShipToAddress
• vw_MSDYNAMICNAV_ShipmentHeader
• vw_MSDYNAMICNAV_ShipmentDetail
• vw_MSDYNAMICNAV_InvoiceHeader
• vw_MSDYNAMICNAV_InvoiceDetail
• vw_MSDYNAMICNAV_SalesOrderHeader
• vw_MSDYNAMICNAV_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 NAV → 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.