CRMPro → Salesforce — Steelviking: what the shipped templates set up

CRMPro → Salesforce — Steelviking: 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/steelviking.md, and that skill’s ERP table is what points at it. What follows is only what the shipped Steelviking → 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
Part	ERP PART data becomes CommercientSF14__Part__c in Salesforce. New records are created, existing ones updated, and records removed in the ERP are deleted.	CommercientSF14__Part__c	SF_ERP_Salesforce_Clone_Part
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, CommercientSF14__Customer__c	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.	CommercientSF14__Invoice__c, CommercientSF14__InvoiceLine__c	SF_ERP_Salesforce_Clone_Invoice, SF_ERP_Salesforce_Clone_SalesOrder, CommercientFlags, SF_ERP_Salesforce_Clone_Customer, SF_ERP_Salesforce_Clone_InvoiceLine
Product	ERP PART, PRICEBOOK data becomes Product2, CommercientSF14__Steel_Viking_PriceBook__c in Salesforce. New records are created, existing ones updated, and records removed in the ERP are deleted.	Product2, CommercientSF14__Steel_Viking_PriceBook__c	SF_ERP_Salesforce_Clone_Part, SF_ERP_Salesforce_Clone_PriceBook
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.	CommercientSF14__SalesOrder__c, CommercientSF14__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
CRM Account	account	CommercientSF__Commercient_ArCustomerCode__c	1	CRM_Account:	vw_STEELVIKING_CRM_Account	'' / ''	1
Customer	CommercientSF14__Customer__c	CommercientSF14__ExternalKey__c	2	Customer:	vw_STEELVIKING_Customer	CommercientSF14__ / __c	1
Part	CommercientSF14__Part__c	CommercientSF14__ExternalKey__c	3	Part	vw_STEELVIKING_Part	CommercientSF14__ / __c	1
Product	Product2	CommercientSF__ExternalKey__c	4	Product	vw_STEELVIKING_Product	'' / ''	1
SalesOrder	CommercientSF14__SalesOrder__c	CommercientSF14__ExternalKey__c	5	SalesOrder:	vw_STEELVIKING_SalesOrder	CommercientSF14__ / __c	1
Invoice	CommercientSF14__Invoice__c	CommercientSF14__ExternalKey__c	6	Invoice:	vw_STEELVIKING_Invoice	CommercientSF14__ / __c	1
SalesOrderLine	CommercientSF14__SalesOrderLine__c	CommercientSF14__ExternalKey__c	7	SalesOrderLine:	vw_STEELVIKING_SalesOrderLine	CommercientSF14__ / __c	1
InvoiceLine	CommercientSF14__InvoiceLine__c	CommercientSF14__ExternalKey__c	8	InvoiceLine:	vw_STEELVIKING_InvoiceLine	CommercientSF14__ / __c	1
PriceBook	CommercientSF14__Steel_Viking_PriceBook__c	CommercientSF14__ExternalKey__c	9	PriceBook:	vw_STEELVIKING_PriceBook	CommercientSF14__ / __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 CRM Account, Product — 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_STEELVIKING_CRM_Account	insert-only	—	CRM_Account:	CommercientSF__Commercient_ArCustomerCode__c	SF_ERP_Salesforce_Clone_Customer
vw_STEELVIKING_Customer	insert + update	—	CRM_Account:, Customer:	ExternalKey	SF_ERP_Salesforce_Clone_Customer
vw_STEELVIKING_Part	insert + update	Part:	—	ExternalKey	SF_ERP_Salesforce_Clone_Part
vw_STEELVIKING_Product	insert + update	Product:	—	CommercientSF__ExternalKey__c	SF_ERP_Salesforce_Clone_Part
vw_STEELVIKING_SalesOrder	insert + update	—	CRM_Account:, Customer:, SalesOrder:	ExternalKey	SF_ERP_Salesforce_Clone_SalesOrder, CommercientFlags
vw_STEELVIKING_Invoice	insert + update	—	CRM_Account:, Customer:, SalesOrder:, Invoice:	ExternalKey	SF_ERP_Salesforce_Clone_Invoice, SF_ERP_Salesforce_Clone_SalesOrder, CommercientFlags, SF_ERP_Salesforce_Clone_Customer
vw_STEELVIKING_SalesOrderLine	insert + update	—	SalesOrder:, Part:, Product:, SalesOrderLine:	ExternalKey	SF_ERP_Salesforce_Clone_SalesOrderLine
vw_STEELVIKING_InvoiceLine	insert + update	—	Invoice:, Part:, Product:, InvoiceLine:	ExternalKey	SF_ERP_Salesforce_Clone_InvoiceLine
vw_STEELVIKING_PriceBook	insert + update	—	CRM_Account:, Product:, PriceBook:	ExternalKey	SF_ERP_Salesforce_Clone_PriceBook

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

• 1 — CRM Account
• 2 — Customer
• 3 — Part
• 4 — Product
• 5 — SalesOrder
• 6 — Invoice
• 7 — SalesOrderLine
• 8 — InvoiceLine
• 9 — 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_STEELVIKING_CRM_Account reads CRM_Account:; no template in this set writes CRM_Account:
• vw_STEELVIKING_Customer reads CRM_Account:, Customer:; no template in this set writes CRM_Account:, Customer:
• vw_STEELVIKING_Invoice reads CRM_Account:, Customer:, SalesOrder:, Invoice:; no template in this set writes CRM_Account:, Customer:, SalesOrder:, Invoice:
• vw_STEELVIKING_InvoiceLine reads Invoice:, Part:, Product:, InvoiceLine:; no template in this set writes Invoice:, InvoiceLine:
• vw_STEELVIKING_PriceBook reads CRM_Account:, Product:, PriceBook:; no template in this set writes CRM_Account:, PriceBook:
• vw_STEELVIKING_SalesOrder reads CRM_Account:, Customer:, SalesOrder:; no template in this set writes CRM_Account:, Customer:, SalesOrder:
• vw_STEELVIKING_SalesOrderLine reads SalesOrder:, Part:, Product:, SalesOrderLine:; no template in this set writes SalesOrder:, SalesOrderLine:

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
CRM Account	account	9	CommercientSFommercient_ArCustomerCode → CommercientSF__Commercient_ArCustomerCode__c, BillingStreet → BillingStreet, BillingCity → BillingCity, BillingState → BillingState, BillingCountry → BillingCountry
Customer	CommercientSF14__Customer__c	25	Account → Account, CustomerID → CommercientSF14__CustomerID__c, CustomerNbr → CommercientSF14__CustomerNbr__c, CustomerName → CommercientSF14__CustomerName__c, SalesRepID → CommercientSF14__SalesRepID__c
Part	CommercientSF14__Part__c	2	PartID → CommercientSF14__PartID__c, PartNbr → CommercientSF14__PartNbr__c
Product	Product2	4	CommercientSF__ExternalKey → CommercientSF__ExternalKey__c, ProductCode → ProductCode, Description → Description, IsActive → IsActive
SalesOrder	CommercientSF14__SalesOrder__c	29	Account → Account, SalesOrderID → CommercientSF14__SalesOrderID__c, SalesOrderNbr → CommercientSF14__SalesOrderNbr__c, CustomerID → CommercientSF14__CustomerID__c, OrderDate → CommercientSF14__OrderDate__c
Invoice	CommercientSF14__Invoice__c	32	Account → Account, InvoiceID → InvoiceID, InvoiceNbr → InvoiceNbr, CustomerID → CommercientSF14__CustomerID__c, InvoiceDate → InvoiceDate
SalesOrderLine	CommercientSF14__SalesOrderLine__c	13	SalesOrderLineID → CommercientSF14__SalesOrderLineID__c, SalesOrderID → CommercientSF14__SalesOrderID__c, PartID → CommercientSF14__PartID__c, LineNbr → CommercientSF14__LineNbr__c, OrderQty → CommercientSF14__OrderQty__c
InvoiceLine	CommercientSF14__InvoiceLine__c	13	InvoiceLineID → InvoiceLineID, InvoiceID → InvoiceID, InvoiceLineSeqNbr → InvoiceLineSeqNbr, InvoiceLineType → InvoiceLineType, InvoiceLineDescr → InvoiceLineDescr
PriceBook	CommercientSF14__Steel_Viking_PriceBook__c	14	Account → Account, Product → Product, PartCustomerPriceID → PartCustomerPriceID, PriceType → PriceType, CustomerID → CommercientSF14__CustomerID__c

6. Community templates

The catalogue carries 9 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: 9
• Default operations: insert on 9, update on 9, delete on 9
• Marked circular-sync: 0
• Licence groups they span: 6
• Destination objects: account, CommercientSF14__Customer__c, CommercientSF14__Invoice__c, CommercientSF14__InvoiceLine__c, CommercientSF14__Part__c, CommercientSF14__SalesOrder__c, CommercientSF14__SalesOrderLine__c, CommercientSF14__Steel_Viking_PriceBook__c, Product2
• Object display names: CRM Account, Customer, Invoice, InvoiceLine, Part, PriceBook, Product, SalesOrder, SalesOrderLine
• Template groups: Account, Invoice, Product, Salesorder

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:

• Part
• CRM_Account:
• Customer:
• Invoice:
• InvoiceLine:
• Product
• PriceBook:
• SalesOrder:
• SalesOrderLine:

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