CRMPro → Salesforce — Traverse Process PRO Global: what the shipped templates set up

CRMPro → Salesforce — Traverse Process PRO Global: 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/traverse-process-pro-global.md, and that skill’s ERP table is what points at it. What follows is only what the shipped Traverse Process PRO Global → 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	—
TRAVERSEPROCESSPROGLOBAL SoTransHeader	ERP TBLSOTRANSHEADER data becomes CommercientSF7__tblSoTransHeader__c in Salesforce. New records are created, existing ones updated, and records removed in the ERP are deleted.	CommercientSF7__tblSoTransHeader__c	SF_ERP_Salesforce_Clone_tblSoTransHeader, CommercientFlags
TRAVERSEPROCESSPROGLOBAL SoTransDetail	ERP TBLSOTRANSDETAIL data becomes CommercientSF7__tblSoTransDetail__c in Salesforce. New records are created, existing ones updated, and records removed in the ERP are deleted.	CommercientSF7__tblSoTransDetail__c	SF_ERP_Salesforce_Clone_tblSoTransDetail
TRAVERSEPROCESSPROGLOBAL ArHistHeader	ERP TBLARHISTHEADER data becomes CommercientSF7__tblArHistHeader__c in Salesforce. New records are created, existing ones updated, and records removed in the ERP are deleted.	CommercientSF7__tblArHistHeader__c	SF_ERP_Salesforce_Clone_tblArHistHeader, CommercientFlags
TRAVERSEPROCESSPROGLOBAL ArHistDetail	ERP TBLARHISTDETAIL data becomes CommercientSF7__tblArHistDetail__c in Salesforce. New records are created, existing ones updated, and records removed in the ERP are deleted.	CommercientSF7__tblArHistDetail__c	SF_ERP_Salesforce_Clone_tblArHistDetail
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, CommercientSF7__tblArCust__c	SF_ERP_Salesforce_Clone_tblArCust, SF_CustSales, SF_ERP_Salesforce_Clone_tblArShipTo
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.	CommercientSF7__tblArShipTo__c	SF_ERP_Salesforce_Clone_tblArShipTo
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.	CommercientSF7__tblArOpenInvoice__c, Invoice__c, Invoice_Detail__c	SF_ERP_Salesforce_Clone_tblArOpenInvoice, CommercientFlags, trav_tblArHistHeader_view, SF_ERP_Salesforce_Clone_tblArHistHeader, ERP, trav_tblArHistDetail_view
Product	The templates push Product2 to Salesforce. New records are created, existing ones updated, and records removed in the ERP are deleted.	Product2	—
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.	Order_Header__c, Order_Detail__c	trav_tblSoTransHeader_view, SF_ERP_Salesforce_Clone_tblSoTransHeader, CommercientFlags, trav_tblSoTransDetail_view, SF_ERP_Salesforce_Clone_tblSoTransDetail, ERP

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_TRAVERSEPROCESSPROGLOBAL_GetUser	1=0	'' / ''	1
Get Salesforce Product	Product2	—	0	vw_TRAVERSEPROCESSPROGLOBAL_Product	1=0	'' / ''	1
Account	Account	CommercientSF__Commercient_ArCustomerCode__c	1	vw_TRAVERSEPROCESSPROGLOBAL_Account	vw_TRAVERSEPROCESSPROGLOBAL_Account	'' / ''	1
Child Account	Account	CommercientSF__Commercient_ArCustomerCode__c	2	vw_TRAVERSEPROCESSPROGLOBAL_Account	vw_TRAVERSEPROCESSPROGLOBAL_ChildAccount	'' / ''	1
TRAVERSEPROCESSPROGLOBAL Customer	CommercientSF7__tblArCust__c	CommercientSF7__CustId__c	3	vw_TRAVERSEPROCESSPROGLOBAL_Customer	vw_TRAVERSEPROCESSPROGLOBAL_Customer	CommercientSF7__ / __c	1
TRAVERSEPROCESSPROGLOBAL CustomerToAccountLookup	Account	CommercientSF__Commercient_ArCustomerCode__c	4	vw_TRAVERSEPROCESSPROGLOBAL_CustomerToAccountLooku	vw_TRAVERSEPROCESSPROGLOBAL_CustomerToAccountLookup	'' / ''	1
TRAVERSEPROCESSPROGLOBAL ShipTo	CommercientSF7__tblArShipTo__c	CommercientSF7__ExternalKey__c	5	vw_TRAVERSEPROCESSPROGLOBAL_ShipTo	vw_TRAVERSEPROCESSPROGLOBAL_ShipTo	CommercientSF7__ / __c	1
TRAVERSEPROCESSPROGLOBAL SoTransHeader	CommercientSF7__tblSoTransHeader__c	CommercientSF7__TransId__c	6	vw_TRAVERSEPROCESSPROGLOBAL_SoTransHeader	vw_TRAVERSEPROCESSPROGLOBAL_SoTransHeader	CommercientSF7__ / __c	1
TRAVERSEPROCESSPROGLOBAL SoTransDetail	CommercientSF7__tblSoTransDetail__c	CommercientSF7__ExternalKey__c	7	vw_TRAVERSEPROCESSPROGLOBAL_SoTransDetail	vw_TRAVERSEPROCESSPROGLOBAL_SoTransDetail	CommercientSF7__ / __c	1
TRAVERSEPROCESSPROGLOBAL ArHistHeader	CommercientSF7__tblArHistHeader__c	CommercientSF7__ExternalKey__c	8	vw_TRAVERSEPROCESSPROGLOBAL_ArHistHeader	vw_TRAVERSEPROCESSPROGLOBAL_ArHistHeader	CommercientSF7__ / __c	1
TRAVERSEPROCESSPROGLOBAL ArHistDetail	CommercientSF7__tblArHistDetail__c	CommercientSF7__ExternalKey__c	9	vw_TRAVERSEPROCESSPROGLOBAL_ArHistDetail	vw_TRAVERSEPROCESSPROGLOBAL_ArHistDetail	CommercientSF7__ / __c	1
TRAVERSEPROCESSPROGLOBAL ArOpenInvoice	CommercientSF7__tblArOpenInvoice__c	CommercientSF7__Counter__c	10	vw_TRAVERSEPROCESSPROGLOBAL_ArOpenInvoice	vw_TRAVERSEPROCESSPROGLOBAL_ArOpenInvoice	CommercientSF7__ / __c	1
Order Header	Order_Header__c	somast_id_col__c	11	vw_TRAVERSEPROCESSPROGLOBAL_OrderHeader	vw_TRAVERSEPROCESSPROGLOBAL_OrderHeader	'' / __c	1
Order Detail	Order_Detail__c	sotran_id_col__c	12	vw_TRAVERSEPROCESSPROGLOBAL_OrderDetail	vw_TRAVERSEPROCESSPROGLOBAL_OrderDetail	'' / __c	1
Invoice Header	Invoice__c	armast_id_col__c	13	vw_TRAVERSEPROCESSPROGLOBAL_InvoiceHeader	vw_TRAVERSEPROCESSPROGLOBAL_InvoiceHeader	'' / __c	1
Invoice Detail	Invoice_Detail__c	adtran_id__c	14	vw_TRAVERSEPROCESSPROGLOBAL_InvoiceDetail	vw_TRAVERSEPROCESSPROGLOBAL_InvoiceDetail	'' / __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 Get Salesforce User, Account, Get Salesforce Product, Order Header — 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_TRAVERSEPROCESSPROGLOBAL_Account	insert + update	vw_TRAVERSEPROCESSPROGLOBAL_Account:	vw_TRAVERSEPROCESSPROGLOBAL_GetUser:	—	SF_ERP_Salesforce_Clone_tblArCust, SF_CustSales
vw_TRAVERSEPROCESSPROGLOBAL_ChildAccount	insert + update	vw_TRAVERSEPROCESSPROGLOBAL_Account:	vw_TRAVERSEPROCESSPROGLOBAL_GetUser:	—	SF_ERP_Salesforce_Clone_tblArShipTo, SF_ERP_Salesforce_Clone_tblArCust
vw_TRAVERSEPROCESSPROGLOBAL_Customer	insert + update	vw_TRAVERSEPROCESSPROGLOBAL_Customer:	vw_TRAVERSEPROCESSPROGLOBAL_Account:	—	SF_ERP_Salesforce_Clone_tblArCust
vw_TRAVERSEPROCESSPROGLOBAL_CustomerToAccountLookup	insert + update	vw_TRAVERSEPROCESSPROGLOBAL_CustomerToAccountLooku:	vw_TRAVERSEPROCESSPROGLOBAL_Customer:, vw_TRAVERSEPROCESSPROGLOBAL_Account:	—	SF_ERP_Salesforce_Clone_tblArCust
vw_TRAVERSEPROCESSPROGLOBAL_ShipTo	insert + update	vw_TRAVERSEPROCESSPROGLOBAL_ShipTo:	vw_TRAVERSEPROCESSPROGLOBAL_Account:, vw_TRAVERSEPROCESSPROGLOBAL_Customer:	ExternalKey	SF_ERP_Salesforce_Clone_tblArShipTo
vw_TRAVERSEPROCESSPROGLOBAL_SoTransHeader	insert + update	vw_TRAVERSEPROCESSPROGLOBAL_SoTransHeader:	vw_TRAVERSEPROCESSPROGLOBAL_Account:, vw_TRAVERSEPROCESSPROGLOBAL_Customer:	—	SF_ERP_Salesforce_Clone_tblSoTransHeader, CommercientFlags
vw_TRAVERSEPROCESSPROGLOBAL_SoTransDetail	insert + update	vw_TRAVERSEPROCESSPROGLOBAL_SoTransDetail:	vw_TRAVERSEPROCESSPROGLOBAL_SoTransHeader:	ExternalKey	SF_ERP_Salesforce_Clone_tblSoTransDetail
vw_TRAVERSEPROCESSPROGLOBAL_ArHistHeader	insert + update	vw_TRAVERSEPROCESSPROGLOBAL_ArHistHeader:	vw_TRAVERSEPROCESSPROGLOBAL_Account:, vw_TRAVERSEPROCESSPROGLOBAL_Customer:, vw_TRAVERSEPROCESSPROGLOBAL_SoTransHeader:	ExternalKey	SF_ERP_Salesforce_Clone_tblArHistHeader, CommercientFlags
vw_TRAVERSEPROCESSPROGLOBAL_ArHistDetail	insert + update	vw_TRAVERSEPROCESSPROGLOBAL_ArHistDetail:	vw_TRAVERSEPROCESSPROGLOBAL_ArHistHeader:	ExternalKey	SF_ERP_Salesforce_Clone_tblArHistDetail
vw_TRAVERSEPROCESSPROGLOBAL_ArOpenInvoice	insert + update	vw_TRAVERSEPROCESSPROGLOBAL_ArOpenInvoice:	vw_TRAVERSEPROCESSPROGLOBAL_Account:	—	SF_ERP_Salesforce_Clone_tblArOpenInvoice, CommercientFlags
vw_TRAVERSEPROCESSPROGLOBAL_OrderHeader	insert + update	vw_TRAVERSEPROCESSPROGLOBAL_OrderHeader:	vw_TRAVERSEPROCESSPROGLOBAL_Account:	somast_id_col__c	trav_tblSoTransHeader_view, SF_ERP_Salesforce_Clone_tblSoTransHeader, CommercientFlags
vw_TRAVERSEPROCESSPROGLOBAL_OrderDetail	insert + update	vw_TRAVERSEPROCESSPROGLOBAL_OrderDetail:	vw_TRAVERSEPROCESSPROGLOBAL_OrderHeader:, vw_TRAVERSEPROCESSPROGLOBAL_Product:	sotran_id_col__c	trav_tblSoTransDetail_view, SF_ERP_Salesforce_Clone_tblSoTransDetail, SF_ERP_Salesforce_Clone_tblSoTransHeader, trav_tblSoTransHeader_view, ERP
vw_TRAVERSEPROCESSPROGLOBAL_InvoiceHeader	insert + update	vw_TRAVERSEPROCESSPROGLOBAL_InvoiceHeader:	vw_TRAVERSEPROCESSPROGLOBAL_Account:, vw_TRAVERSEPROCESSPROGLOBAL_OrderHeader:	armast_id_col__c	trav_tblArHistHeader_view, SF_ERP_Salesforce_Clone_tblArHistHeader, ERP
vw_TRAVERSEPROCESSPROGLOBAL_InvoiceDetail	insert + update	vw_TRAVERSEPROCESSPROGLOBAL_InvoiceDetail:	vw_TRAVERSEPROCESSPROGLOBAL_InvoiceHeader:, vw_TRAVERSEPROCESSPROGLOBAL_Product:	adtran_id__c	trav_tblArHistDetail_view, SF_ERP_Salesforce_Clone_tblArHistDetail, trav_tblArHistHeader_view, ERP

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

• 0 — Get Salesforce User, Get Salesforce Product
• 1 — Account
• 2 — Child Account
• 3 — TRAVERSEPROCESSPROGLOBAL Customer
• 4 — TRAVERSEPROCESSPROGLOBAL CustomerToAccountLookup
• 5 — TRAVERSEPROCESSPROGLOBAL ShipTo
• 6 — TRAVERSEPROCESSPROGLOBAL SoTransHeader
• 7 — TRAVERSEPROCESSPROGLOBAL SoTransDetail
• 8 — TRAVERSEPROCESSPROGLOBAL ArHistHeader
• 9 — TRAVERSEPROCESSPROGLOBAL ArHistDetail
• 10 — TRAVERSEPROCESSPROGLOBAL ArOpenInvoice
• 11 — Order Header
• 12 — Order Detail
• 13 — Invoice Header
• 14 — Invoice Detail

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_TRAVERSEPROCESSPROGLOBAL_SoTransHeader reads vw_TRAVERSEPROCESSPROGLOBAL_Account:, vw_TRAVERSEPROCESSPROGLOBAL_Customer:
• vw_TRAVERSEPROCESSPROGLOBAL_SoTransDetail reads vw_TRAVERSEPROCESSPROGLOBAL_SoTransHeader:
• vw_TRAVERSEPROCESSPROGLOBAL_ArHistHeader reads vw_TRAVERSEPROCESSPROGLOBAL_Account:, vw_TRAVERSEPROCESSPROGLOBAL_Customer:, vw_TRAVERSEPROCESSPROGLOBAL_SoTransHeader:
• vw_TRAVERSEPROCESSPROGLOBAL_ArHistDetail reads vw_TRAVERSEPROCESSPROGLOBAL_ArHistHeader:
• vw_TRAVERSEPROCESSPROGLOBAL_Account reads vw_TRAVERSEPROCESSPROGLOBAL_GetUser:
• vw_TRAVERSEPROCESSPROGLOBAL_ChildAccount reads vw_TRAVERSEPROCESSPROGLOBAL_GetUser:
• vw_TRAVERSEPROCESSPROGLOBAL_CustomerToAccountLookup reads vw_TRAVERSEPROCESSPROGLOBAL_Customer:, vw_TRAVERSEPROCESSPROGLOBAL_Account:
• vw_TRAVERSEPROCESSPROGLOBAL_Customer reads vw_TRAVERSEPROCESSPROGLOBAL_Account:
• vw_TRAVERSEPROCESSPROGLOBAL_ShipTo reads vw_TRAVERSEPROCESSPROGLOBAL_Account:, vw_TRAVERSEPROCESSPROGLOBAL_Customer:
• vw_TRAVERSEPROCESSPROGLOBAL_ArOpenInvoice reads vw_TRAVERSEPROCESSPROGLOBAL_Account:
• vw_TRAVERSEPROCESSPROGLOBAL_InvoiceHeader reads vw_TRAVERSEPROCESSPROGLOBAL_Account:, vw_TRAVERSEPROCESSPROGLOBAL_OrderHeader:
• vw_TRAVERSEPROCESSPROGLOBAL_InvoiceDetail reads vw_TRAVERSEPROCESSPROGLOBAL_InvoiceHeader:, vw_TRAVERSEPROCESSPROGLOBAL_Product:
• vw_TRAVERSEPROCESSPROGLOBAL_OrderHeader reads vw_TRAVERSEPROCESSPROGLOBAL_Account:
• vw_TRAVERSEPROCESSPROGLOBAL_OrderDetail reads vw_TRAVERSEPROCESSPROGLOBAL_OrderHeader:, vw_TRAVERSEPROCESSPROGLOBAL_Product:

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	20	CommercientSFommercient_ArCustomerCode → CommercientSF__Commercient_ArCustomerCode__c, BillingStreet → BillingStreet, BillingCity → BillingCity, BillingState → BillingState, BillingCountry → BillingCountry
Child Account	Account	13	CommercientSFommercient_ArCustomerCode → CommercientSF__Commercient_ArCustomerCode__c, ParentID → ParentID, BillingStreet → BillingStreet, BillingCity → BillingCity, BillingState → BillingState
TRAVERSEPROCESSPROGLOBAL Customer	CommercientSF7__tblArCust__c	65	CustId → CommercientSF7__CustId__c, Account → Account, AcctType → AcctType, Addr1 → CommercientSF7__Addr1__c, Addr2 → CommercientSF7__Addr2__c
TRAVERSEPROCESSPROGLOBAL CustomerToAccountLookup	Account	2	CommercientSFommercient_ArCustomerCode → CommercientSF__Commercient_ArCustomerCode__c, CommercientSF7__Traverse_Customer_Record → CommercientSF7__Traverse_Customer_Record__c
TRAVERSEPROCESSPROGLOBAL ShipTo	CommercientSF7__tblArShipTo__c	24	Addr1 → CommercientSF7__Addr1__c, Addr2 → CommercientSF7__Addr2__c, AddressType → CommercientSF7__AddressType__c, Attn → CommercientSF7__Attn__c, City → CommercientSF7__City__c
TRAVERSEPROCESSPROGLOBAL SoTransHeader	CommercientSF7__tblSoTransHeader__c	75	TransId → CommercientSF7__TransId__c, Account → Account, Traverse_Customer_Record → Traverse_Customer_Record__c, TransType → CommercientSF7__TransType__c, BatchId → BatchId
TRAVERSEPROCESSPROGLOBAL SoTransDetail	CommercientSF7__tblSoTransDetail__c	71	tblSoTransHeader → CommercientSF7__tblSoTransHeader__c, TransId → CommercientSF7__TransId__c, EntryNum → CommercientSF7__EntryNum__c, ItemJob → CommercientSF7__ItemJob__c, LocId → LocId
TRAVERSEPROCESSPROGLOBAL ArHistHeader	CommercientSF7__tblArHistHeader__c	95	Account → Account, Traverse_Customer_Record → CommercientSF7__Traverse_Customer_Record__c, tblSoTransHeader → CommercientSF7__tblSoTransHeader__c, PostRun → CommercientSF7__PostRun__c, TransId → CommercientSF7__TransId__c
TRAVERSEPROCESSPROGLOBAL ArHistDetail	CommercientSF7__tblArHistDetail__c	80	tblArHistHeader → CommercientSF7__tblArHistHeader__c, TransId → CommercientSF7__TransId__c, EntryNum → CommercientSF7__EntryNum__c, ItemJob → CommercientSF7__ItemJob__c, WhseId → CommercientSF7__WhseId__c
TRAVERSEPROCESSPROGLOBAL ArOpenInvoice	CommercientSF7__tblArOpenInvoice__c	30	Counter → CommercientSF7__Counter__c, Account → Account, CustId → CommercientSF7__CustId__c, InvcNum → InvcNum, RecType → RecType
Order Header	Order_Header__c	16	somast_id_col → somast_id_col__c, Account → Account__c, Required_Date → Required_Date__c, Order_Total → Order_Total__c, Customer_Ship_To_Number → Customer_Ship_To_Number__c
Order Detail	Order_Detail__c	10	sotran_id_col → sotran_id_col__c, Order_Header → Order_Header__c, Product → Product__c, Description → Description__c, Quantity → Quantity__c
Invoice Header	Invoice__c	17	armast_id_col → armast_id_col__c, Account → Account__c, Order → Order__c, PO_Number → PO_Number__c, Invoice_Date → Invoice_Date__c
Invoice Detail	Invoice_Detail__c	11	adtran_id → adtran_id__c, Invoice → Invoice__c, Product → Product__c, Description → Description__c, Quantity → Quantity__c

6. Community templates

The catalogue carries 19 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: 19
• Default operations: insert on 19, update on 19, delete on 19
• Marked circular-sync: 0
• Licence groups they span: 8
• Destination objects: Account, Product2, CommercientSF7__tblArCust__c, CommercientSF7__tblArHistDetail__c, CommercientSF7__tblArHistHeader__c, CommercientSF7__tblArOpenInvoice__c, CommercientSF7__tblArShipTo__c, CommercientSF7__tblInItem__c, CommercientSF7__tblSoTransDetail__c, CommercientSF7__tblSoTransHeader__c, Invoice__c, Invoice_Detail__c, Order_Detail__c, Order_Header__c, User
• Object display names: Account, Child Account, Get Salesforce Product, Get Salesforce User, Invoice Detail, Invoice Header, Order Detail, Order Header, Product, TRAVERSEPROCESSPROGLOBAL ArHistDetail, TRAVERSEPROCESSPROGLOBAL ArHistHeader, TRAVERSEPROCESSPROGLOBAL ArOpenInvoice and 7 more
• Template groups: Account, Product, Invoice, Salesorder, Customer Multi Ship Addresses

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_TRAVERSEPROCESSPROGLOBAL_GetUser
• vw_TRAVERSEPROCESSPROGLOBAL_SoTransHeader
• vw_TRAVERSEPROCESSPROGLOBAL_SoTransDetail
• vw_TRAVERSEPROCESSPROGLOBAL_ArHistHeader
• vw_TRAVERSEPROCESSPROGLOBAL_ArHistDetail
• vw_TRAVERSEPROCESSPROGLOBAL_Account
• vw_TRAVERSEPROCESSPROGLOBAL_CustomerToAccountLooku
• vw_TRAVERSEPROCESSPROGLOBAL_Customer
• vw_TRAVERSEPROCESSPROGLOBAL_ShipTo
• vw_TRAVERSEPROCESSPROGLOBAL_ArOpenInvoice
• vw_TRAVERSEPROCESSPROGLOBAL_InvoiceHeader
• vw_TRAVERSEPROCESSPROGLOBAL_InvoiceDetail
• vw_TRAVERSEPROCESSPROGLOBAL_Product
• vw_TRAVERSEPROCESSPROGLOBAL_OrderHeader
• vw_TRAVERSEPROCESSPROGLOBAL_OrderDetail

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 Traverse Process PRO Global → 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.