CRMPro → Salesforce — Microsoft Business Central: what the shipped templates set up

CRMPro → Salesforce — Microsoft Business Central: 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-business-central.md, and that skill’s ERP table is what points at it. What follows is only what the shipped Microsoft Business Central → 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
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, Contact, CommercientSF9__MSBusinessCentral_Customer__c, MS_Business_Central_Salesperson__c	SF_ERP_Salesforce_Clone_Customer, SF_ERP_Salesforce_Clone_ShipToAddress, SF_ERP_Salesforce_Clone_Contacts, SF_ERP_Salesforce_Clone_SalesRep
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.	MS_Business_Central_ShipToAddress__c	SF_ERP_Salesforce_Clone_ShipToAddress, SF_ERP_Salesforce_Clone_Customer
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__MSBusinessCentral_SalesInvoice__c, CommercientSF9__MSBusinessCentral_SalesInvoiceLine__c	SF_ERP_Salesforce_Clone_SalesInvoice, CommercientFlags, SF_ERP_Salesforce_Clone_SalesInvoiceLine
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__MSBusinessCentral_SalesOrder__c, CommercientSF9__MSBusinessCentral_SalesOrderLine__c	SF_ERP_Salesforce_Clone_SalesOrder, CommercientFlags, SF_ERP_Salesforce_Clone_SalesOrderLine

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_MICROSOFTBUSINESSCENTRAL_GetUser	1=0	'' / ''	1
MS Business Central SalesPerson	MS_Business_Central_Salesperson__c	ExternalKey__c	1	vw_MICROSOFTBUSINESSCENTRAL_SalesPerson	vw_MICROSOFTBUSINESSCENTRAL_SalesPerson	'' / __c	1
Accounts	Account	CommercientSF__Commercient_ArCustomerCode__c	2	vw_MICROSOFTBUSINESSCENTRAL_Account	vw_MICROSOFTBUSINESSCENTRAL_Account	'' / ''	1
MS_Business_Central_Customer	CommercientSF9__MSBusinessCentral_Customer__c	CommercientSF9__ExternalKey__c	2	vw_MICROSOFTBUSINESSCENTRAL_Customer	vw_MICROSOFTBUSINESSCENTRAL_Customer	CommercientSF9__ / __c	1
Customer To Account Lookup	Account	CommercientSF__Commercient_ArCustomerCode__c	5	vw_MICROSOFTBUSINESSCENTRAL_CustomerToAccountLooku	vw_MICROSOFTBUSINESSCENTRAL_CustomerToAccountLookup	'' / ''	1
MS Business Central Ship To Address	MS_Business_Central_ShipToAddress__c	ExternalKey__c	6	vw_MICROSOFTBUSINESSCENTRAL_ShipToAddress	vw_MICROSOFTBUSINESSCENTRAL_ShipToAddress	'' / __c	1
MS Business Central Sales Order	CommercientSF9__MSBusinessCentral_SalesOrder__c	CommercientSF9__ExternalKey__c	7	vw_MICROSOFTBUSINESSCENTRAL_SalesOrder	vw_MICROSOFTBUSINESSCENTRAL_SalesOrder	CommercientSF9__ / __c	1
MS Business Central Sales Order Line	CommercientSF9__MSBusinessCentral_SalesOrderLine__c	CommercientSF9__ExternalKey__c	8	vw_MICROSOFTBUSINESSCENTRAL_SalesOrderLine	vw_MICROSOFTBUSINESSCENTRAL_SalesOrderLine	CommercientSF9__ / __c	1
MS Business Central Sales Invoice	CommercientSF9__MSBusinessCentral_SalesInvoice__c	CommercientSF9__ExternalKey__c	9	vw_MICROSOFTBUSINESSCENTRAL_SalesInvoice	vw_MICROSOFTBUSINESSCENTRAL_SalesInvoice	CommercientSF9__ / __c	1
MS Business Central Sales Invoice Line	CommercientSF9__MSBusinessCentral_SalesInvoiceLine__c	CommercientSF9__ExternalKey__c	10	vw_MICROSOFTBUSINESSCENTRAL_SalesInvoiceLine	vw_MICROSOFTBUSINESSCENTRAL_SalesInvoiceLine	CommercientSF9__ / __c	1
Contact	Contact	ExternalKey__c	16	vw_MICROSOFTBUSINESSCENTRAL_Contact	vw_MICROSOFTBUSINESSCENTRAL_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_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 Salesforce User, Accounts, Contact — 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_MICROSOFTBUSINESSCENTRAL_SalesPerson	insert + update	vw_MICROSOFTBUSINESSCENTRAL_SalesPerson:	—	ExternalKey	SF_ERP_Salesforce_Clone_SalesRep
vw_MICROSOFTBUSINESSCENTRAL_Account	insert + update	vw_MICROSOFTBUSINESSCENTRAL_Account:	vw_MICROSOFTBUSINESSCENTRAL_SalesPerson:, vw_MICROSOFTBUSINESSCENTRAL_GetUser:	—	SF_ERP_Salesforce_Clone_Customer, SF_ERP_Salesforce_Clone_ShipToAddress
vw_MICROSOFTBUSINESSCENTRAL_Customer	insert + update	vw_MICROSOFTBUSINESSCENTRAL_Customer:	vw_MICROSOFTBUSINESSCENTRAL_Account:, vw_MICROSOFTBUSINESSCENTRAL_SalesPerson:, vw_MICROSOFTBUSINESSCENTRAL_GetUser:	ExternalKey	SF_ERP_Salesforce_Clone_Customer
vw_MICROSOFTBUSINESSCENTRAL_CustomerToAccountLookup	insert + update	vw_MICROSOFTBUSINESSCENTRAL_CustomerToAccountLooku:	vw_MICROSOFTBUSINESSCENTRAL_Customer:, vw_MICROSOFTBUSINESSCENTRAL_Account:	—	SF_ERP_Salesforce_Clone_Customer
vw_MICROSOFTBUSINESSCENTRAL_ShipToAddress	insert + update	vw_MICROSOFTBUSINESSCENTRAL_ShipToAddress:	vw_MICROSOFTBUSINESSCENTRAL_Account:, vw_MICROSOFTBUSINESSCENTRAL_Customer:	ExternalKey	SF_ERP_Salesforce_Clone_ShipToAddress, SF_ERP_Salesforce_Clone_Customer
vw_MICROSOFTBUSINESSCENTRAL_SalesOrder	insert + update	vw_MICROSOFTBUSINESSCENTRAL_SalesOrder:	vw_MICROSOFTBUSINESSCENTRAL_Account:, vw_MICROSOFTBUSINESSCENTRAL_Customer:	ExternalKey	SF_ERP_Salesforce_Clone_SalesOrder, CommercientFlags
vw_MICROSOFTBUSINESSCENTRAL_SalesOrderLine	insert + update	vw_MICROSOFTBUSINESSCENTRAL_SalesOrderLine:	vw_MICROSOFTBUSINESSCENTRAL_SalesOrder:	ExternalKey	SF_ERP_Salesforce_Clone_SalesOrderLine
vw_MICROSOFTBUSINESSCENTRAL_SalesInvoice	insert + update	vw_MICROSOFTBUSINESSCENTRAL_SalesInvoice:	vw_MICROSOFTBUSINESSCENTRAL_Account:, vw_MICROSOFTBUSINESSCENTRAL_Customer:	ExternalKey	SF_ERP_Salesforce_Clone_SalesInvoice, CommercientFlags
vw_MICROSOFTBUSINESSCENTRAL_SalesInvoiceLine	insert + update	vw_MICROSOFTBUSINESSCENTRAL_SalesInvoiceLine:	vw_MICROSOFTBUSINESSCENTRAL_SalesInvoice:	ExternalKey	SF_ERP_Salesforce_Clone_SalesInvoiceLine
vw_MICROSOFTBUSINESSCENTRAL_Contact	insert + update	vw_MICROSOFTBUSINESSCENTRAL_Contact:	vw_MICROSOFTBUSINESSCENTRAL_Account:	—	SF_ERP_Salesforce_Clone_Contacts, SF_ERP_Salesforce_Clone_Customer

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

• 0 — Get Salesforce User
• 1 — MS Business Central SalesPerson
• 2 — Accounts, MS_Business_Central_Customer
• 5 — Customer To Account Lookup
• 6 — MS Business Central Ship To Address
• 7 — MS Business Central Sales Order
• 8 — MS Business Central Sales Order Line
• 9 — MS Business Central Sales Invoice
• 10 — MS Business Central Sales Invoice Line
• 16 — 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_MICROSOFTBUSINESSCENTRAL_Account reads vw_MICROSOFTBUSINESSCENTRAL_SalesPerson:, vw_MICROSOFTBUSINESSCENTRAL_GetUser:
• vw_MICROSOFTBUSINESSCENTRAL_CustomerToAccountLookup reads vw_MICROSOFTBUSINESSCENTRAL_Customer:, vw_MICROSOFTBUSINESSCENTRAL_Account:
• vw_MICROSOFTBUSINESSCENTRAL_Contact reads vw_MICROSOFTBUSINESSCENTRAL_Account:
• vw_MICROSOFTBUSINESSCENTRAL_Customer reads vw_MICROSOFTBUSINESSCENTRAL_Account:, vw_MICROSOFTBUSINESSCENTRAL_SalesPerson:, vw_MICROSOFTBUSINESSCENTRAL_GetUser:
• vw_MICROSOFTBUSINESSCENTRAL_ShipToAddress reads vw_MICROSOFTBUSINESSCENTRAL_Account:, vw_MICROSOFTBUSINESSCENTRAL_Customer:
• vw_MICROSOFTBUSINESSCENTRAL_SalesInvoice reads vw_MICROSOFTBUSINESSCENTRAL_Account:, vw_MICROSOFTBUSINESSCENTRAL_Customer:
• vw_MICROSOFTBUSINESSCENTRAL_SalesInvoiceLine reads vw_MICROSOFTBUSINESSCENTRAL_SalesInvoice:
• vw_MICROSOFTBUSINESSCENTRAL_SalesOrder reads vw_MICROSOFTBUSINESSCENTRAL_Account:, vw_MICROSOFTBUSINESSCENTRAL_Customer:
• vw_MICROSOFTBUSINESSCENTRAL_SalesOrderLine reads vw_MICROSOFTBUSINESSCENTRAL_SalesOrder:

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
MS Business Central SalesPerson	MS_Business_Central_Salesperson__c	3	Code → code__c, EMail → email__c, PhoneNo → phoneno__c
Accounts	Account	13	CommercientSFommercient_ArCustomerCode → CommercientSF__Commercient_ArCustomerCode__c, Phone → Phone, BillingStreet → BillingStreet, BillingCity → BillingCity, BillingStateCode → BillingStateCode
MS_Business_Central_Customer	CommercientSF9__MSBusinessCentral_Customer__c	22	Account → Account, addresscountryLetterCode → addresscountryLetterCode, addresscity → addresscity, addresspostalCode → addresspostalCode, addressstate → CommercientSF9__addressstate__c
Customer To Account Lookup	Account	2	CommercientSFommercient_ArCustomerCode → CommercientSF__Commercient_ArCustomerCode__c, MS_Business_Central_Customer → MS_Business_Central_Customer__c
MS Business Central Ship To Address	MS_Business_Central_ShipToAddress__c	16	Account → Account__c, MS_Business_Central_Customer → MS_Business_Central_Customer__c, CustomerNo → customerno__c, Code → code__c, Name2 → name2__c
MS Business Central Sales Order	CommercientSF9__MSBusinessCentral_SalesOrder__c	43	Account → Account, MS_Business_Central_Customer → MS_Business_Central_Customer, billingPostalAddresscity → billingPostalAddresscity, billingPostalAddresspostalCode → billingPostalAddresspostalCode, billingPostalAddressstate → CommercientSF9__billingPostalAddressstate__c
MS Business Central Sales Order Line	CommercientSF9__MSBusinessCentral_SalesOrderLine__c	18	MS_Business_Central_Sales_Order_Header → CommercientSF9__ms_business_central_sales_order_header__c, DocumentType → documenttype__c, DocumentNo → documentno__c, LineNoo → linenoo__c, accountId → CommercientSF9__accountid__c
MS Business Central Sales Invoice	CommercientSF9__MSBusinessCentral_SalesInvoice__c	44	Account → Account, MS_Business_Central_Customer → MS_Business_Central_Customer, billingPostalAddresscity → billingPostalAddresscity, billingPostalAddresspostalCode → billingPostalAddresspostalCode, billingPostalAddressstate → CommercientSF9__billingPostalAddressstate__c
MS Business Central Sales Invoice Line	CommercientSF9__MSBusinessCentral_SalesInvoiceLine__c	14	MS_Business_Central_Invoice_Header → MS_Business_Central_Invoice_Header, accountId → accountId, description → description, discountAppliedBeforeTax → discountAppliedBeforeTax, documentId → documentId
Contact	Contact	11	AccountID → AccountID, FirstName → FirstName, LastName → LastName, Email → Email, Phone → Phone

6. Community templates

The catalogue carries 45 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: 45
• Default operations: insert on 45, update on 45, delete on 45
• Marked circular-sync: 3
• Licence groups they span: 11
• Destination objects: Account, PriceBookEntry, Product2, Contact, MS_Business_Central_Customer__c, MS_Business_Central_Item__c, MS_Business_Central_SalesInvoice__c, MS_Business_Central_SalesInvoiceLine__c, MS_Business_Central_ShipToAddress__c, User, ACCOUNTMATCHING__c, CommercientSF9__MSBusinessCentral_Customer__c, CommercientSF9__MSBusinessCentral_SalesInvoice__c, CommercientSF9__MSBusinessCentral_SalesInvoiceLine__c, CommercientSF9__MSBusinessCentral_SalesOrder__c, CommercientSF9__MSBusinessCentral_SalesOrderLine__c, CONTACTMATCHING__c, ExternalKey__c, MS_Business_Central_Item_Location__c, MS_Business_Central_Sales_Order_Header__c and 7 more
• Object display names: Accounts, Contact, Customer To Account Lookup, MS Business Central Sales Invoice, MS Business Central Sales Invoice Line, MS Business Central Sales Order, MS Business Central Sales Order Line, MS Business Central Ship To Address, MS_Business_Central_Customer, Account, Child Accounts, Custom PriceBook Create, 23 more and a further template
• Template groups: Account, Product, Invoice, Salesorder, Customer Multi Ship Addresses, Opportunity

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_MICROSOFTBUSINESSCENTRAL_GetUser
• vw_MICROSOFTBUSINESSCENTRAL_Account
• vw_MICROSOFTBUSINESSCENTRAL_CustomerToAccountLooku
• vw_MICROSOFTBUSINESSCENTRAL_Contact
• vw_MICROSOFTBUSINESSCENTRAL_Customer
• vw_MICROSOFTBUSINESSCENTRAL_ShipToAddress
• vw_MICROSOFTBUSINESSCENTRAL_SalesInvoice
• vw_MICROSOFTBUSINESSCENTRAL_SalesInvoiceLine
• vw_MICROSOFTBUSINESSCENTRAL_SalesOrder
• vw_MICROSOFTBUSINESSCENTRAL_SalesOrderLine
• vw_MICROSOFTBUSINESSCENTRAL_SalesPerson

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 Business Central → 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.