CRMPro → Salesforce — VAI S2K: what the shipped templates set up

CRMPro → Salesforce — VAI S2K: 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/vai-s2k.md, and that skill’s ERP table is what points at it. What follows is only what the shipped VAI S2K → 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
VCMENOT Sync	ERP VCMENOT data becomes VCMENOT__c in Salesforce. New records are created and existing ones updated; none are deleted.	VCMENOT__c	SF_ERP_Salesforce_Clone_VCMENOT
VCNENOT Sync	ERP VCNENOT data becomes VCNENOT__c in Salesforce. New records are created and existing ones updated; none are deleted.	VCNENOT__c	SF_ERP_Salesforce_Clone_VCNENOT
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 and existing ones updated; none are deleted.	Account, Contact, Commercient36__VARCUST__c	SF_ERP_Salesforce_Clone_VARCUST, SF_ERP_Salesforce_Clone_VARSHIP, SF_ERP_Salesforce_Clone_VCRPROS, SF_ERP_Salesforce_Clone_VXACNAD, SF_ERP_Salesforce_Clone_VXACNTC
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.	Commercient36__VARSHIP__c	SF_ERP_Salesforce_Clone_VARSHIP
Product	ERP VINITEM, VINLOC, VINITMB data becomes VINITEM__c, VINLOC__c, VINITMB__c in Salesforce. New records are created and existing ones updated; none are deleted.	VINITEM__c, VINLOC__c, VINITMB__c, Product2	SF_ERP_Salesforce_Clone_VINITEM, SF_ERP_Salesforce_Clone_VINLOC, SF_ERP_Salesforce_Clone_VINITMB
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.	Commercient36__VCOHEAD__c, Commercient36__VCODETL__c	SF_ERP_Salesforce_Clone_VCOHEAD, SF_ERP_Salesforce_Clone_VCODETL

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
Account	Account	CommercientSF__Commercient_ArCustomerCode__c	1	vw_Account	vw_VAIS2K_Account	'' / ''
Contact	Contact	ExternalKey__c	2	vw_Contact	vw_VAIS2K_Contact	'' / ''
Customer	Commercient36__VARCUST__c	Commercient36__ExternalKey__c	3	vw_Customer	vw_VAIS2K_Customer	Commercient36__ / __c
Account To Customer Reverse Lookup	Account	CommercientSF__Commercient_ArCustomerCode__c	4	vw_CustomerToAccountLookup	vw_VAIS2K_CustomerToAccountLookup	'' / ''
ShipToAddress	Commercient36__VARSHIP__c	Commercient36__ExternalKey__c	5	vw_ShipToAddress	vw_VAIS2K_ShipToAddress	Commercient36__ / __c
SalesOrderHeader	Commercient36__VCOHEAD__c	Commercient36__ExternalKey__c	6	vw_SalesOrderHeader	vw_VAIS2K_SalesOrderHeader	Commercient36__ / __c
SalesOrderDetail	Commercient36__VCODETL__c	Commercient36__ExternalKey__c	7	vw_SalesOrderDetail	vw_VAIS2K_SalesOrderDetail	Commercient36__ / __c
Product	Product2	CommercientSF__ExternalKey__c	8	vw_Product	vw_VAIS2K_Product	'' / ''
Item	VINITEM__c	ExternalKey__c	9	vw_Item	vw_VAIS2K_Item	'' / __c
Product To Item Reverse Lookup	Product2	CommercientSF__ExternalKey__c	10	vw_ProductToItemMasterLookup	vw_VAIS2K_ProductToItemMasterLookup	'' / ''
Warehouse	VINLOC__c	ExternalKey__c	11	vw_Warehouse	vw_VAIS2K_Warehouse	'' / __c
Item Warehouse	VINITMB__c	ExternalKey__c	12	vw_ItemWarehouse	vw_VAIS2K_ItemWarehouse	'' / __c
VCMENOT Sync	VCMENOT__c	ExternalKey__c	15	vw_VCMENOT	vw_VAIS2K_VCMENOT	'' / __c
VCNENOT Sync	VCNENOT__c	ExternalKey__c	16	vw_VCNENOT	vw_VAIS2K_VCNENOT	'' / __c
Prospect Account	Account	CommercientSF__Commercient_ArCustomerCode__c	17	vw_ProspectAccount	vw_VAIS2K_ProspectAccount	'' / ''
Prospect Contact	Contact	ExternalKey__c	18	vw_ProspectContact	vw_VAIS2K_ProspectContact	'' / ''

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. The insert column lists do not include Sync_Operation_Type, Sync_Batch_Size, IsAccountMatching, Document_Source_Path, so those columns take their CRM_Configuration defaults. Text columns a template does not use are inserted as '' rather than left NULL.

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	Source tables
vw_VAIS2K_Account	insert + update	vw_Account:	—	SF_ERP_Salesforce_Clone_VARCUST, SF_ERP_Salesforce_Clone_VARSHIP
vw_VAIS2K_Contact	insert + update	vw_Contact:	vw_Account:	SF_ERP_Salesforce_Clone_VARCUST, SF_ERP_Salesforce_Clone_VXACNAD, SF_ERP_Salesforce_Clone_VXACNTC, SF_ERP_Salesforce_Clone_VARSHIP
vw_VAIS2K_Customer	insert + update	vw_Customer:	vw_Account:	SF_ERP_Salesforce_Clone_VARCUST
vw_VAIS2K_CustomerToAccountLookup	insert + update	vw_CustomerToAccountLookup:	vw_Customer:	SF_ERP_Salesforce_Clone_VARCUST
vw_VAIS2K_ShipToAddress	insert + update	vw_ShipToAddress:	vw_Account:, vw_Customer:	SF_ERP_Salesforce_Clone_VARSHIP
vw_VAIS2K_SalesOrderHeader	insert + update	vw_SalesOrderHeader:	vw_Account:, vw_Customer:	SF_ERP_Salesforce_Clone_VCOHEAD
vw_VAIS2K_SalesOrderDetail	insert + update	vw_SalesOrderDetail:	vw_SalesOrderHeader:	SF_ERP_Salesforce_Clone_VCODETL
vw_VAIS2K_Product	insert + update	vw_Product:	—	SF_ERP_Salesforce_Clone_VINITEM
vw_VAIS2K_Item	insert + update	vw_Item:	vw_Product:	SF_ERP_Salesforce_Clone_VINITEM
vw_VAIS2K_ProductToItemMasterLookup	insert + update	vw_ProductToItemMasterLookup:	vw_Item:	SF_ERP_Salesforce_Clone_VINITEM
vw_VAIS2K_Warehouse	insert + update	vw_Warehouse:	—	SF_ERP_Salesforce_Clone_VINLOC
vw_VAIS2K_ItemWarehouse	insert + update	vw_ItemWarehouse:	vw_Product:, vw_Item:, vw_Warehouse:	SF_ERP_Salesforce_Clone_VINITMB
vw_VAIS2K_VCMENOT	insert + update	vw_VCMENOT:	vw_Account:, vw_Customer:	SF_ERP_Salesforce_Clone_VCMENOT
vw_VAIS2K_VCNENOT	insert + update	vw_VCNENOT:	vw_Account:, vw_Customer:	SF_ERP_Salesforce_Clone_VCNENOT
vw_VAIS2K_ProspectAccount	insert + update	vw_ProspectAccount:	—	SF_ERP_Salesforce_Clone_VCRPROS
vw_VAIS2K_ProspectContact	insert + update	vw_ProspectContact:	vw_ProspectAccount:	SF_ERP_Salesforce_Clone_VCRPROS, SF_ERP_Salesforce_Clone_VXACNAD, SF_ERP_Salesforce_Clone_VXACNTC

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

• 1 — Account
• 2 — Contact
• 3 — Customer
• 4 — Account To Customer Reverse Lookup
• 5 — ShipToAddress
• 6 — SalesOrderHeader
• 7 — SalesOrderDetail
• 8 — Product
• 9 — Item
• 10 — Product To Item Reverse Lookup
• 11 — Warehouse
• 12 — Item Warehouse
• 15 — VCMENOT Sync
• 16 — VCNENOT Sync
• 17 — Prospect Account
• 18 — Prospect Contact

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_VAIS2K_VCMENOT reads vw_Account:, vw_Customer:
• vw_VAIS2K_VCNENOT reads vw_Account:, vw_Customer:
• vw_VAIS2K_CustomerToAccountLookup reads vw_Customer:
• vw_VAIS2K_Contact reads vw_Account:
• vw_VAIS2K_ProspectContact reads vw_ProspectAccount:
• vw_VAIS2K_Customer reads vw_Account:
• vw_VAIS2K_ShipToAddress reads vw_Account:, vw_Customer:
• vw_VAIS2K_Item reads vw_Product:
• vw_VAIS2K_ItemWarehouse reads vw_Product:, vw_Item:, vw_Warehouse:
• vw_VAIS2K_ProductToItemMasterLookup reads vw_Item:
• vw_VAIS2K_SalesOrderHeader reads vw_Account:, vw_Customer:
• vw_VAIS2K_SalesOrderDetail reads vw_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
Account	Account	14	RMCMP,RMCUST → CommercientSF__Commercient_ArCustomerCode__c, RMNAME → Name, RMMFON → Phone, RMCP → Type, RMADD1,RMADD2,RMADD3 → BillingStreet
Customer	Commercient36__VARCUST__c	10	RMCMP, RMCUST → Commercient36__ExternalKey__c, RMNAME → Name, RMADD1, RMADD2, RMADD3 → BillingStreet, RMCITY → BillingCity, RMSTAT → BillingState
Account To Customer Reverse Lookup	Account	2	RMCMP, RMCUST → CommercientSF__Commercient_ArCustomerCode__c, SFDCID → Commercient36__VAIS2K_Customer_Master__c
ShipToAddress	Commercient36__VARSHIP__c	90	RVCMP, RVCUST, RVSHIP → Commercient36__ExternalKey__c, RVCMP, RVCUST → Commercient36__Account__c, RVCMP, RVCUST → Commercient36__VAIS2K_Customer_Master__c, RVNAME → Name, RVDEL → Commercient36__RVDEL__c
SalesOrderHeader	Commercient36__VCOHEAD__c	99	OACMP, OAORD, OABOCD → Commercient36__ExternalKey__c, OACMP, OACUST → Commercient36__Account__c, OACMP, OACUST → Commercient36__VAIS2K_Customer_Master__c, OACMP, OAORD, OABOCD → Name, OADEL → Commercient36__OADEL__c
SalesOrderDetail	Commercient36__VCODETL__c	97	OBCMP, OBORD, OBBOCD, OBLINE → ExternalKey, OBCMP, OBORD, OBBOCD, OBLINE → Name, OBDEL → OBDEL, OBCMP → OBCMP, OBORD → OBORD
Product	Product2	5	ICCMP, ICITEM → CommercientSF__ExternalKey__c, ICITEM → ProductCode, ICDSC1, ICDSC2, ICDSC3 → Description, ICDSC1, ICDSC2, ICDSC3, ICITEM → Name
Item	VINITEM__c	99	ICCMP, ICITEM → ExternalKey__c, SFDCID → Product__c, ICDSC1, ICDSC2, ICDSC3, ICITEM → Name, ICDEL → ICDEL__c, ICCMP → ICCMP__c
Product To Item Reverse Lookup	Product2	2	ICCMP, ICITEM → CommercientSF__ExternalKey__c, SFDCID → VAIS2K_Item_Master__c
Warehouse	VINLOC__c	99	IACMP, IALOC → ExternalKey__c, IACMP, IALOC, IANAME → Name, IADEL → IADEL, IACMP → IACMP, IALOC → IALOC
Item Warehouse	VINITMB__c	101	IFDEL, IFCOMP, IFLOC, IFITEM → ExternalKey__c, IFCOMP, IFITEM → Product__c, IFCOMP, IFITEM → VAIS2K_Item_Master__c, IFCOMP, IFLOC → VAIS2K_Warehouse__c, IFDEL, IFCOMP, IFLOC, IFITEM → Name
VCMENOT Sync	VCMENOT__c	27	CCCMP, CCCUST, CCDATE, CCTIME, CCNOT1, CCNOT2, CCNOT3 → ExternalKey__c, CCCMP, CCCUST → Account, CCCMP, CCCUST → VAIS2K_Customer_Master, CCCMP, CCCUST, CCDATE, CCTIME → Name, CCDEL → CCDEL
VCNENOT Sync	VCNENOT__c	27	CCCMP, CCCUST, CCDATE, CCTIME, CCNOT1 → ExternalKey__c, CCCMP, CCCUST → Account, CCCMP, CCCUST → VAIS2K_Customer_Master, CCCMP, CCCUST, CCDATE, CCTIME → Name, CCDEL → CCDEL
Prospect Account	Account	14	CPCMP, CPPROS → CommercientSF__Commercient_ArCustomerCode__c, CPNAME → Name, CPMFON → Phone, Type → Type, CPADD1, CPADD2, CPADD3 → BillingStreet

6. Community templates

The catalogue carries 68 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: 68
• Default operations: insert on 68, update on 68, delete on 68
• Marked circular-sync: 7
• Licence groups they span: 14
• Destination objects: Account, Contact, Order, Pricebookentry, Product2, OrderItem, Commercient36__VARSHIP__c, Commercient36__VARCUST__c, Commercient36__VCODETL__c, Commercient36__VCOHEAD__c, Quote, QuoteLineItem, Commercient36_Division__c, Commercient36_Division_Class__c, Commercient36_SalesOrderHistoryDetail__c, Commercient36_SalesOrderHistoryHeader__c, Commercient36_SalesPerson__c, Commercient36_VINITEM__c, Commercient36_VINITMB__c, Commercient36_VINLOC__c, 10 more and 6 custom objects
• Object display names: Account, Account To Customer Reverse Lookup, Contact, Customer, Item, Item Warehouse, Product, Product To Item Reverse Lookup, SalesOrderDetail, SalesOrderHeader, ShipToAddress, Standard Pricebook Create, 28 more and 15 further templates
• Template groups: Account, Product, CRM Order and Line, Salesorder, CRM Quote and Line, Customer Multi Ship Addresses, CRM Opportunity and Line, 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_VCMENOT
• vw_VCNENOT
• vw_Account
• vw_CustomerToAccountLookup
• vw_ProspectAccount
• vw_Contact
• vw_ProspectContact
• vw_Customer
• vw_ShipToAddress
• vw_Item
• vw_Warehouse
• vw_ItemWarehouse
• vw_Product
• vw_ProductToItemMasterLookup
• vw_SalesOrderHeader
• vw_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 VAI S2K → 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.