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

CRMPro → Salesforce — Microsoft Dynamics AX: 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-ax.md, and that skill’s ERP table is what points at it. What follows is only what the shipped Microsoft Dynamics AX → 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
SYNC SALESQUOTATIONTABLE	The templates push CommercientSF9__SALESQUOTATIONTABLE__c to Salesforce. New records are created and existing ones updated; none are deleted.	CommercientSF9__SALESQUOTATIONTABLE__c	SF_ERP_Salesforce_Clone_SalesQuotationTable
Get Salesforce User	The templates push User to Salesforce. New records are created, existing ones updated, and records removed in the ERP are deleted.	User	—
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, CommercientSF9__MSDYNAMICAX_PaymentTerms__c, Contact, CommercientSF9__MSDYNAMICAX_Customer__c, CommercientSF9__MSDYNAMICAX_SalesPerson__c	SF_ERP_Salesforce_Clone_CUSTTABLE, SF_ERP_Salesforce_Clone_CompanyInfo, SF_ERP_Salesforce_Clone_PAYMTERM, SF_ERP_Salesforce_Clone_CONTACTPERSON
CRM Opportunity and Line	The templates push OPPORTUNITY to Salesforce. New records are created and existing ones updated; none are deleted.	OPPORTUNITY	SF_ERP_Salesforce_Clone_smmOpportunityTable, SF_ERP_Salesforce_Clone_CUSTTABLE
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 and existing ones updated; none are deleted.	CommercientSF9__MSDYNAMICAX_Address__c	SF_ERP_Salesforce_Clone_ADDRESS
Product	The templates push CommercientSF9__MSDYNAMICAX_ItemWarehouse__c, CommercientSF9__MSDYNAMICAX_Item__c, Product2 to Salesforce. New records are created and existing ones updated; none are deleted.	CommercientSF9__MSDYNAMICAX_ItemWarehouse__c, CommercientSF9__MSDYNAMICAX_Item__c, Product2	SF_ERP_Salesforce_Clone_INVENTLOCATION, SF_ERP_Salesforce_Clone_INVENTTABLE
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__MSDYNAMICAX_InvoiceHeader__c, CommercientSF9__MSDYNAMICAX_InvoiceDetail__c	SF_ERP_Salesforce_Clone_SALESLINE, SF_ERP_Salesforce_Clone_CUSTINVOICETRANS, CT, SF_ERP_Salesforce_Clone_CUSTINVOICEJOUR
Pricebook	The templates push PricebookEntry to Salesforce. New records are created and existing ones updated; none are deleted.	PricebookEntry	SF_ERP_Salesforce_Clone_INVENTTABLE
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__MSDYNAMICAX_SalesOrderHeader__c, CommercientSF9__MSDYNAMICAX_SalesOrderDetail__c	SF_ERP_Salesforce_Clone_SALESTABLE, S, CommercientFlags, SF_ERP_Salesforce_Clone_SALESLINE

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 Salesforce User	User	CommercientSF6__SalespersonCode__c	0	vw_MSDYNAMICAX_GetUser	1=0	'' / ''	1
SYNC PAYMTERM	CommercientSF9__MSDYNAMICAX_PaymentTerms__c	CommercientSF9__ExternalKey__c	1	vw_MSDYNAMICAX_PAYMTERM	vw_MSDYNAMICAX_PAYMTERM	CommercientSF9__ / __c	—
SYNC ADDRESS	CommercientSF9__MSDYNAMICAX_Address__c	CommercientSF9__ExternalKey__c	2	vw_MSDYNAMICAX_Address	vw_MSDYNAMICAX_Address	CommercientSF9__ / __c	—
MSDYNAMICAX SalesPerson	CommercientSF9__MSDYNAMICAX_SalesPerson__c	CommercientSF9__ExternalKey__c	3	vw_MSDYNAMICAX_SalesPerson	vw_MSDYNAMICAX_SalesPerson	CommercientSF9__ / __c	—
Account	Account	CommercientSF__Commercient_ArCustomerCode__c	4	vw_MSDYNAMICAX_Account	vw_MSDYNAMICAX_Account	'' / ''	—
SYNC CUSTOMER	CommercientSF9__MSDYNAMICAX_Customer__c	CommercientSF9__ExternalKey__c	5	vw_MSDYNAMICAX_Customer	vw_MSDYNAMICAX_Customer	CommercientSF9__ / __c	—
SYNC CUSTOMERTOACCOUNTLOOKUP	Account	CommercientSF__Commercient_ArCustomerCode__c	6	vw_MSDYNAMICAX_CustomerToAccountLookup	vw_MSDYNAMICAX_CustomerToAccountLookup	'' / ''	—
SYNC ITEMWAREHOUSE	CommercientSF9__MSDYNAMICAX_ItemWarehouse__c	CommercientSF9__ExternalKey__c	7	vw_MSDYNAMICAX_ItemWarehouse	vw_MSDYNAMICAX_ItemWarehouse	CommercientSF9__ / __C	—
SYNC PRODUCT	Product2	CommercientSF__ExternalKey__c	8	vw_MSDYNAMICAX_Product	vw_MSDYNAMICAX_Product	'' / ''	—
SYNC ITEM	CommercientSF9__MSDYNAMICAX_Item__c	CommercientSF9__ExternalKey__c	9	vw_MSDYNAMICAX_Item	vw_MSDYNAMICAX_Item	CommercientSF9__ / __C	—
SYNC ITEMTOPRODUCTLOOKUP	Product2	CommercientSF__ExternalKey__c	10	vw_MSDYNAMICAX_ItemToProductLookup	vw_MSDYNAMICAX_ItemToProductLookup	'' / ''	—
SYNC STANDARDPRICEBOOK	PricebookEntry	ExternalKey__c	11	vw_MSDYNAMICAX_StandardPriceBook	vw_MSDYNAMICAX_StandardPriceBook	'' / ''	—
SYNC STANDARDPRICEBOOKUPDATE	PricebookEntry	ExternalKey__c	12	vw_MSDYNAMICAX_StandardPriceBook_Update	vw_MSDYNAMICAX_StandardPriceBook_Update	'' / ''	—
SYNC OPPORTUNITY	OPPORTUNITY	ExternalKey__c	13	vw_MSDYNAMICAX_Opportunity	vw_MSDYNAMICAX_Opportunity	'' / ''	—
SYNC SALESORDERHEADER	CommercientSF9__MSDYNAMICAX_SalesOrderHeader__c	CommercientSF9__ExternalKey__c	15	vw_MSDYNAMICAX_SALESORDERHEADER	vw_MSDYNAMICAX_SALESORDERHEADER	CommercientSF9__ / __c	—
SYNC SALESORDERDETAIL	CommercientSF9__MSDYNAMICAX_SalesOrderDetail__c	CommercientSF9__ExternalKey__c	16	vw_MSDYNAMICAX_SALESORDERDETAIL	vw_MSDYNAMICAX_SALESORDERDETAIL	CommercientSF9__ / __c	—
SYNC INVOICEHEADER	CommercientSF9__MSDYNAMICAX_InvoiceHeader__c	CommercientSF9__ExternalKey__c	17	vw_MSDYNAMICAX_INVOICEHEADER	vw_MSDYNAMICAX_INVOICEHEADER	CommercientSF9__ / __c	—
SYNC INVOICEDETAIL	CommercientSF9__MSDYNAMICAX_InvoiceDetail__c	CommercientSF9__ExternalKey__c	18	vw_MSDYNAMICAX_INVOICEDETAIL	vw_MSDYNAMICAX_INVOICEDETAIL	CommercientSF9__ / __c	—
SYNC SALESQUOTATIONTABLE	CommercientSF9__SALESQUOTATIONTABLE__c	CommercientSF9__ExternalKey__c	19	vw_MSDYNAMICAX_SalesQuotationTable	vw_MSDYNAMICAX_SalesQuotationTable	CommercientSF9__ / __c	—
Contact	Contact	ExternalKey__c	19	vw_MSDYNAMICAX_Contact	vw_MSDYNAMICAX_Contact	'' / ''	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_Delete_Records 0, Sync_Batch_Size 200. Is_Active_Get_Records is set on SYNC STANDARDPRICEBOOK; IsAccountMatching is set on Account, Contact. Text columns a template does not use are inserted as '' rather than left NULL. Get_SOQL_Query carries a query on Get Salesforce User, SYNC STANDARDPRICEBOOK — those rows read records back from Salesforce as well as pushing. On SYNC INVOICEHEADER the SQL_Query names a view the same template’s CreateViewQuery does not create (vw_MSDYNAMICAX_INVOICEHEADER against vw_MSDYNAMICAX_SALESORDERDETAIL), 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_MSDYNAMICAX_PAYMTERM	insert + update	vw_MSDYNAMICAX_PAYMTERM:	—	—	SF_ERP_Salesforce_Clone_PAYMTERM
vw_MSDYNAMICAX_Address	insert + update	vw_MSDYNAMICAX_Address:	—	—	SF_ERP_Salesforce_Clone_ADDRESS
vw_MSDYNAMICAX_SalesPerson	insert + update	vw_MSDYNAMICAX_SalesPerson:	—	ExternalKey	SF_ERP_Salesforce_Clone_CONTACTPERSON
vw_MSDYNAMICAX_Account	insert + update	vw_MSDYNAMICAX_Account:	—	CommercientSF__Commercient_ArCustomerCode__c	SF_ERP_Salesforce_Clone_CUSTTABLE, SF_ERP_Salesforce_Clone_CompanyInfo
vw_MSDYNAMICAX_Customer	insert + update	vw_MSDYNAMICAX_Customer:	vw_MSDYNAMICAX_Account:, vw_MSDYNAMICAX_PAYMTERM:	—	SF_ERP_Salesforce_Clone_CUSTTABLE
vw_MSDYNAMICAX_CustomerToAccountLookup	insert + update	vw_MSDYNAMICAX_CustomerToAccountLookup:	vw_MSDYNAMICAX_Customer:	—	SF_ERP_Salesforce_Clone_CUSTTABLE
vw_MSDYNAMICAX_ItemWarehouse	insert + update	vw_MSDYNAMICAX_ItemWarehouse:	—	—	SF_ERP_Salesforce_Clone_INVENTLOCATION
vw_MSDYNAMICAX_Product	insert + update	vw_MSDYNAMICAX_Product:	—	—	SF_ERP_Salesforce_Clone_INVENTTABLE
vw_MSDYNAMICAX_Item	insert + update	vw_MSDYNAMICAX_Item:	vw_MSDYNAMICAX_Product:	—	SF_ERP_Salesforce_Clone_INVENTTABLE
vw_MSDYNAMICAX_ItemToProductLookup	insert + update	vw_MSDYNAMICAX_ItemToProductLookup:	vw_MSDYNAMICAX_Item:	—	SF_ERP_Salesforce_Clone_INVENTTABLE
vw_MSDYNAMICAX_StandardPriceBook	insert + update	vw_MSDYNAMICAX_StandardPriceBook:	vw_MSDYNAMICAX_Product:	—	SF_ERP_Salesforce_Clone_INVENTTABLE
vw_MSDYNAMICAX_StandardPriceBook_Update	insert + update	—	vw_MSDYNAMICAX_Product:, vw_MSDYNAMICAX_StandardPriceBook:	—	SF_ERP_Salesforce_Clone_INVENTTABLE
vw_MSDYNAMICAX_Opportunity	insert + update	vw_MSDYNAMICAX_Opportunity:	vw_MSDYNAMICAX_Account:	—	SF_ERP_Salesforce_Clone_smmOpportunityTable, SF_ERP_Salesforce_Clone_CUSTTABLE
vw_MSDYNAMICAX_SALESORDERHEADER	insert + update	vw_MSDYNAMICAX_SALESORDERHEADER:	vw_MSDYNAMICAX_Account:, vw_MSDYNAMICAX_Customer:, vw_MSDYNAMICAX_SalesPerson:	ExternalKey	SF_ERP_Salesforce_Clone_SALESTABLE, S, CommercientFlags
vw_MSDYNAMICAX_SALESORDERDETAIL	insert + update	vw_MSDYNAMICAX_SALESORDERDETAIL:	vw_MSDYNAMICAX_SALESORDERHEADER:, vw_MSDYNAMICAX_Item:	—	SF_ERP_Salesforce_Clone_SALESLINE
vw_MSDYNAMICAX_SALESORDERDETAIL	insert + update	—	vw_MSDYNAMICAX_SALESORDERHEADER:, vw_MSDYNAMICAX_Item:, vw_MSDYNAMICAX_SALESORDERDETAIL:	—	SF_ERP_Salesforce_Clone_SALESLINE
vw_MSDYNAMICAX_INVOICEDETAIL	insert + update	vw_MSDYNAMICAX_INVOICEDETAIL:	vw_MSDYNAMICAX_INVOICEHEADER:, vw_MSDYNAMICAX_Item:	ExternalKey	SF_ERP_Salesforce_Clone_CUSTINVOICETRANS, CT, SF_ERP_Salesforce_Clone_CUSTINVOICEJOUR
vw_MSDYNAMICAX_Contact	insert + update	vw_MSDYNAMICAX_Contact:	—	ExternalKey__c	SF_ERP_Salesforce_Clone_CONTACTPERSON

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

• 0 — Get Salesforce User
• 1 — SYNC PAYMTERM
• 2 — SYNC ADDRESS
• 3 — MSDYNAMICAX SalesPerson
• 4 — Account
• 5 — SYNC CUSTOMER
• 6 — SYNC CUSTOMERTOACCOUNTLOOKUP
• 7 — SYNC ITEMWAREHOUSE
• 8 — SYNC PRODUCT
• 9 — SYNC ITEM
• 10 — SYNC ITEMTOPRODUCTLOOKUP
• 11 — SYNC STANDARDPRICEBOOK
• 12 — SYNC STANDARDPRICEBOOKUPDATE
• 13 — SYNC OPPORTUNITY
• 15 — SYNC SALESORDERHEADER
• 16 — SYNC SALESORDERDETAIL
• 17 — SYNC INVOICEHEADER
• 18 — SYNC INVOICEDETAIL
• 19 — SYNC SALESQUOTATIONTABLE, Contact

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_MSDYNAMICAX_CustomerToAccountLookup reads vw_MSDYNAMICAX_Customer:
• vw_MSDYNAMICAX_Opportunity reads vw_MSDYNAMICAX_Account:
• vw_MSDYNAMICAX_Customer reads vw_MSDYNAMICAX_Account:, vw_MSDYNAMICAX_PAYMTERM:
• vw_MSDYNAMICAX_Item reads vw_MSDYNAMICAX_Product:
• vw_MSDYNAMICAX_SALESORDERDETAIL reads vw_MSDYNAMICAX_SALESORDERHEADER:, vw_MSDYNAMICAX_Item:, vw_MSDYNAMICAX_SALESORDERDETAIL:
• vw_MSDYNAMICAX_INVOICEDETAIL reads vw_MSDYNAMICAX_INVOICEHEADER:, vw_MSDYNAMICAX_Item:
• vw_MSDYNAMICAX_StandardPriceBook reads vw_MSDYNAMICAX_Product:
• vw_MSDYNAMICAX_StandardPriceBook_Update reads vw_MSDYNAMICAX_Product:, vw_MSDYNAMICAX_StandardPriceBook:
• vw_MSDYNAMICAX_ItemToProductLookup reads vw_MSDYNAMICAX_Item:
• vw_MSDYNAMICAX_SALESORDERHEADER reads vw_MSDYNAMICAX_Account:, vw_MSDYNAMICAX_Customer:, vw_MSDYNAMICAX_SalesPerson:
• vw_MSDYNAMICAX_SALESORDERDETAIL reads vw_MSDYNAMICAX_SALESORDERHEADER:, vw_MSDYNAMICAX_Item:

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 PAYMTERM	CommercientSF9__MSDYNAMICAX_PaymentTerms__c	17	DATAAREAID, PAYMTERMID → CommercientSF9__ExternalKey__c, DATAAREAID, PAYMTERMID → Name, PAYMTERMID → CommercientSF9__PAYMTERMID__c, PAYMMETHOD → CommercientSF9__PAYMMETHOD__c, NUMOFDAYS → CommercientSF9__NUMOFDAYS__c
SYNC ADDRESS	CommercientSF9__MSDYNAMICAX_Address__c	15	DATAAREAID,RECID → CommercientSF9__ExternalKey__c, DATAAREAID,RECID → CommercientSF9__Name__c, ADDRESS → CommercientSF9__Address__c, COUNTRYREGIONID → CommercientSF9__COUNTRYREGIONID__c, ZIPCODE → CommercientSF9__ZIPCODE__c
MSDYNAMICAX SalesPerson	CommercientSF9__MSDYNAMICAX_SalesPerson__c	8	RECID → CommercientSF9__ExternalKey__c, NAME → Name, CREATEDBY → CREATEDBY, FIRSTNAME → FIRSTNAME, LASTNAME → LASTNAME
Account	Account	14	DATAAREAID, ACCOUNTNUM → CommercientSF__Commercient_ArCustomerCode__c, DATAAREAID, NAME → <org-prefix>_Company_account__c (an org-specific custom field; the shipped template names one customer org), NAME → Name, PHONE → Phone, ADDRESS → BillingStreet
SYNC CUSTOMER	CommercientSF9__MSDYNAMICAX_Customer__c	56	DATAAREAID,ACCOUNTNUM → CommercientSF9__ExternalKey__c, ACCOUNTNUM → Account, NAME → Name, INVOICEACCOUNT → InvoiceAccount, CUSTGROUP → CustGroup
SYNC CUSTOMERTOACCOUNTLOOKUP	Account	2	DATAAREAID, ACCOUNTNUM → CommercientSF__Commercient_ArCustomerCode__c, SFDCID → CommercientSF9__MSDYNAMICAX_Customer__c
SYNC ITEMWAREHOUSE	CommercientSF9__MSDYNAMICAX_ItemWarehouse__c	32	DATAAREAID,INVENTLOCATIONID → CommercientSF9__ExternalKey__c, NAME → Name, INVENTLOCATIONID → INVENTLOCATIONID, MANUAL → MANUAL, EMPTYPALLETLOCATION → EMPTYPALLETLOCATION
SYNC PRODUCT	Product2	4	DATAAREAID, ITEMID → CommercientSF__ExternalKey__c, ITEMID → ProductCode, ITEMNAME → Name, ITEMNAME → Description
SYNC ITEM	CommercientSF9__MSDYNAMICAX_Item__c	64	DATAAREAID, ITEMID → CommercientSF9__ExternalKey__c, DATAAREAID, ITEMID, ITEMNAME → Name, ITEMID → CommercientSF9__ITEMID__c, ITEMTYPE → CommercientSF9__ITEMTYPE__c, PURCHMODEL → CommercientSF9__PURCHMODEL__c
SYNC ITEMTOPRODUCTLOOKUP	Product2	2	DATAAREAID, ITEMID → CommercientSF__ExternalKey__c, SFDCID → CommercientSF9__MSDYNAMICAX_Item__c
SYNC STANDARDPRICEBOOK	PricebookEntry	6	DATAAREAID, ITEMID → ExternalKey__c, SFDCID → Pricebook2Id, SFDCID → Product2ID, IsActive → IsActive, UnitPrice → UnitPrice
SYNC STANDARDPRICEBOOKUPDATE	PricebookEntry	4	DATAAREAID, ITEMID → ExternalKey__c, IsActive → IsActive, UnitPrice → UnitPrice, TimeStamp → TimeStamp
SYNC OPPORTUNITY	OPPORTUNITY	8	DATAAREAID, OPPORTUNITYID → ExternalKey__c, DATAAREAID, OPPORTUNITYID → Name, SUBJECT → Description, STATUS → StageName, ESTIMATEDREVENUE → Budget__c
SYNC SALESORDERHEADER	CommercientSF9__MSDYNAMICAX_SalesOrderHeader__c	73	DATAAREAID,SALESID → CommercientSF9__ExternalKey__c, SALESID → CommercientSF9__SalesID__c, SALESNAME → CommercientSF9__SalesName__c, RESERVATION → CommercientSF9__Reservation__c, CUSTACCOUNT → CommercientSF9__CustAccount__c
SYNC SALESORDERDETAIL	CommercientSF9__MSDYNAMICAX_SalesOrderDetail__c	77	DATAAREAID,INVENTTRANSID → CommercientSF9__ExternalKey__c, DATAAREAID,INVENTTRANSID → CommercientSF9__Name__c, SALESID → CommercientSF9__SalesID__c, LINENUM → CommercientSF9__LineNum__c, ITEMID → CommercientSF9__ItemID__c
SYNC INVOICEHEADER	CommercientSF9__MSDYNAMICAX_InvoiceHeader__c	74	DATAAREAID,INVENTTRANSID → CommercientSF9__ExternalKey__c, SALESID → CommercientSF9__CommercientSF9__Sales_Order_Header__c, ITEMID → CommercientSF9__CommercientSF9__Item__c, LINENUM → CommercientSF9__CommercientSF9__LINENUM__c, SALESSTATUS → CommercientSF9__CommercientSF9__SALESSTATUS__c
SYNC INVOICEDETAIL	CommercientSF9__MSDYNAMICAX_InvoiceDetail__c	86	DATAAREAID, RECID → CommercientSF9__ExternalKey__c, INVOICEID → CommercientSF9__InvoiceID__c, INVOICEDATE → CommercientSF9__InvoiceDate__c, LINENUM → CommercientSF9__LineNumber__c, INVENTTRANSID → CommercientSF9__InventTransId__c
Contact	Contact	12	FirstName → FirstName, LastName → LastName, Title → Title, Email → Email, Phone → Phone

6. 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_MSDYNAMICAX_SalesQuotationTable
• vw_MSDYNAMICAX_GetUser
• vw_MSDYNAMICAX_Account
• vw_MSDYNAMICAX_CustomerToAccountLookup
• vw_MSDYNAMICAX_PAYMTERM
• vw_MSDYNAMICAX_Contact
• vw_MSDYNAMICAX_Opportunity
• vw_MSDYNAMICAX_Customer
• vw_MSDYNAMICAX_Address
• vw_MSDYNAMICAX_ItemWarehouse
• vw_MSDYNAMICAX_Item
• vw_MSDYNAMICAX_INVOICEHEADER
• vw_MSDYNAMICAX_INVOICEDETAIL
• vw_MSDYNAMICAX_StandardPriceBook
• vw_MSDYNAMICAX_StandardPriceBook_Update
• vw_MSDYNAMICAX_Product
• vw_MSDYNAMICAX_ItemToProductLookup
• vw_MSDYNAMICAX_SALESORDERHEADER
• vw_MSDYNAMICAX_SALESORDERDETAIL
• vw_MSDYNAMICAX_SalesPerson

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