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

CRMPro → Salesforce — GlobalShop: 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/globalshop.md, and that skill’s ERP table is what points at it. What follows is only what the shipped GlobalShop → 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 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, Commercient33__CUSTOMER_MASTER__c	SF_ERP_Salesforce_Clone_CUSTOMER_MASTER, SF_ERP_Salesforce_Clone_V_CUSTOMER_SALES, SF_ERP_Salesforce_Clone_V_OE_MULTI_SHIP
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.	Commercient33__CUSTOMER_SHIPTO__c	SF_ERP_Salesforce_Clone_V_OE_MULTI_SHIP
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.	Commercient33__ORDER_HIST_HEAD__c, Commercient33__ORDER_HIST_LINE__c, Commercient33__AR_OPEN_ITEMS__c	SF_ERP_Salesforce_Clone_ORDER_HIST_HEAD, SF_ERP_Salesforce_Clone_ORDER_HIST_LINE, SF_ERP_Salesforce_Clone_AR_OPEN_ITEMS
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.	Commercient33__ORDER_HEADER__c, Commercient33__ORDER_LINES__c	SF_ERP_Salesforce_Clone_ORDER_HEADER, SF_ERP_Salesforce_Clone_ORDER_LINES

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
Account	Account	CommercientSF__Commercient_ArCustomerCode__c	2	vw_Account	vw_GLOBALSHOP_Account	'' / ''	1
Customer Master	Commercient33__CUSTOMER_MASTER__c	Commercient33__ExternalKey__c	3	vw_Customer	vw_GLOBALSHOP_Customer	Commercient33__ / __c	1
Customer To Account Reverse Lookup	Account	CommercientSF__Commercient_ArCustomerCode__c	4	vw_CustomerToAccountLookup	vw_GLOBALSHOP_CustomerToAccountLookup	'' / ''	1
Sales Order Header	Commercient33__ORDER_HEADER__c	Commercient33__ExternalKey__c	9	vw_SalesOrderHeader	vw_GLOBALSHOP_SalesOrderHeader	Commercient33__ / __c	1
Sales Order Lines	Commercient33__ORDER_LINES__c	Commercient33__ExternalKey__c	10	vw_SalesOrderLines	vw_GLOBALSHOP_SalesOrderLines	Commercient33__ / __c	1
Invoice Header	Commercient33__ORDER_HIST_HEAD__c	Commercient33__ExternalKey__c	11	vw_InvoiceHeader	vw_GLOBALSHOP_InvoiceHeader	Commercient33__ / __c	1
Invoice Lines	Commercient33__ORDER_HIST_LINE__c	Commercient33__ExternalKey__c	12	vw_InvoiceLines	vw_GLOBALSHOP_InvoiceLine	Commercient33__ / __c	1
Invoice Payments	Commercient33__AR_OPEN_ITEMS__c	Commercient33__ExternalKey__c	13	vw_InvoicePayment	vw_GLOBALSHOP_InvoicePayment	Commercient33__ / __c	1
Ship To Address	Commercient33__CUSTOMER_SHIPTO__c	Commercient33__ExternalKey__c	14	vw_ShipToAddress	vw_GLOBALSHOP_ShipToAddress	Commercient33__ / __c	1
Get User	User	Id	17	vw_GLOBALSHOP_User	SELECT 1=0	'' / ''	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 User, Account — 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	Source tables
vw_GLOBALSHOP_Account	insert-only	vw_Account:	vw_GLOBALSHOP_User:	SF_ERP_Salesforce_Clone_CUSTOMER_MASTER, SF_ERP_Salesforce_Clone_V_CUSTOMER_SALES, SF_ERP_Salesforce_Clone_V_OE_MULTI_SHIP
vw_GLOBALSHOP_Customer	insert + update	vw_Customer:	vw_Account:	SF_ERP_Salesforce_Clone_CUSTOMER_MASTER, SF_ERP_Salesforce_Clone_V_CUSTOMER_SALES
vw_GLOBALSHOP_CustomerToAccountLookup	insert + update	vw_CustomerToAccountLookup:	vw_Customer:	SF_ERP_Salesforce_Clone_CUSTOMER_MASTER
vw_GLOBALSHOP_SalesOrderHeader	insert + update	vw_SalesOrderHeader:	vw_Account:, vw_Customer:	SF_ERP_Salesforce_Clone_ORDER_HEADER
vw_GLOBALSHOP_SalesOrderLines	insert + update	vw_SalesOrderLines:	vw_SalesOrderHeader:	SF_ERP_Salesforce_Clone_ORDER_LINES
vw_GLOBALSHOP_InvoiceHeader	insert + update	vw_InvoiceHeader:	vw_Account:, vw_Customer:	SF_ERP_Salesforce_Clone_ORDER_HIST_HEAD
vw_GLOBALSHOP_InvoiceLine	insert + update	vw_InvoiceLines:	vw_InvoiceHeader:	SF_ERP_Salesforce_Clone_ORDER_HIST_LINE
vw_GLOBALSHOP_InvoicePayment	insert + update	vw_InvoicePayment:	vw_Account:, vw_Customer:, vw_InvoiceHeader:	SF_ERP_Salesforce_Clone_AR_OPEN_ITEMS, SF_ERP_Salesforce_Clone_ORDER_HIST_HEAD
vw_GLOBALSHOP_ShipToAddress	insert + update	vw_ShipToAddress:	vw_Account:, vw_Customer:	SF_ERP_Salesforce_Clone_V_OE_MULTI_SHIP

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

• 2 — Account
• 3 — Customer Master
• 4 — Customer To Account Reverse Lookup
• 9 — Sales Order Header
• 10 — Sales Order Lines
• 11 — Invoice Header
• 12 — Invoice Lines
• 13 — Invoice Payments
• 14 — Ship To Address
• 17 — Get User

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_GLOBALSHOP_Account reads vw_GLOBALSHOP_User:
• vw_GLOBALSHOP_CustomerToAccountLookup reads vw_Customer:
• vw_GLOBALSHOP_Customer reads vw_Account:
• vw_GLOBALSHOP_ShipToAddress reads vw_Account:, vw_Customer:
• vw_GLOBALSHOP_InvoiceHeader reads vw_Account:, vw_Customer:
• vw_GLOBALSHOP_InvoiceLine reads vw_InvoiceHeader:
• vw_GLOBALSHOP_InvoicePayment reads vw_Account:, vw_Customer:, vw_InvoiceHeader:
• vw_GLOBALSHOP_SalesOrderHeader reads vw_Account:, vw_Customer:
• vw_GLOBALSHOP_SalesOrderLines 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	11	CommercientSFommercient_ArCustomerCode → CommercientSF__Commercient_ArCustomerCode__c, Phone → Phone, BillingStreet → BillingStreet, BillingCity → BillingCity, BillingCountry → BillingCountry
Customer Master	Commercient33__CUSTOMER_MASTER__c	35	Account → Account, CUSTOMER → Commercient33__CUSTOMER__c, REC → REC, NAME_CUSTOMER → NAME_CUSTOMER, ADDRESS1 → Commercient33__ADDRESS1__c
Customer To Account Reverse Lookup	Account	2	CommercientSFommercient_ArCustomerCode → CommercientSF__Commercient_ArCustomerCode__c, Commercient33__GlobalShop_Customer_Master → Commercient33__GlobalShop_Customer_Master__c
Sales Order Header	Commercient33__ORDER_HEADER__c	98	Account → Account, GlobalShop_Customer_Master → GlobalShop_Customer_Master, ORDER_NO → Commercient33__ORDER_NO__c, RECORD_NO → RECORD_NO, ORDER_SHIP_ID → Commercient33__ORDER_SHIP_ID__c
Sales Order Lines	Commercient33__ORDER_LINES__c	97	GlobalShop_Sales_Order_Header → Commercient33__GlobalShop_Sales_Order_Header__c, ORDER_NO → Commercient33__ORDER_NO__c, RECORD_NO → RECORD_NO, ORDER_SHIP_ID → Commercient33__ORDER_SHIP_ID__c, RECORD_TYPE → RECORD_TYPE
Invoice Header	Commercient33__ORDER_HIST_HEAD__c	98	Account → Account, GlobalShop_Customer_Master → GlobalShop_Customer_Master, INVOICE → INVOICE, ORDER_NO → Commercient33__ORDER_NO__c, ORDER_SUFFIX → Commercient33__ORDER_SUFFIX__c
Invoice Lines	Commercient33__ORDER_HIST_LINE__c	97	GlobalShop_Invoice_Header → GlobalShop_Invoice_Header, INVOICE → INVOICE, ORDER_NO → Commercient33__ORDER_NO__c, ORDER_SUFFIX → Commercient33__ORDER_SUFFIX__c, ORDER_LINE → Commercient33__ORDER_LINE__c
Invoice Payments	Commercient33__AR_OPEN_ITEMS__c	60	Account → Account, GlobalShop_Customer_Master → GlobalShop_Customer_Master, GlobalShop_Invoice_Header → GlobalShop_Invoice_Header, CUSTOMER → Commercient33__CUSTOMER__c, INVOICE → INVOICE
Ship To Address	Commercient33__CUSTOMER_SHIPTO__c	26	Account → Account, GlobalShop_Customer_Master → GlobalShop_Customer_Master, CUSTOMER → Commercient33__CUSTOMER__c, ship_seq → ship_seq__c, NAME_CUSTOMER_SHIP → NAME_CUSTOMER_SHIP

6. Community templates

The catalogue carries 265 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: 265
• Default operations: insert on 265, update on 265, delete on 265
• Marked circular-sync: 8
• Licence groups they span: 13
• Destination objects: Account, Product2, Commercient33__CUSTOMER_MASTER__c, Commercient33__CUSTOMER_SHIPTO__c, Commercient33__ORDER_HEADER__c, Commercient33__ORDER_HIST_HEAD__c, Commercient33__ORDER_HIST_LINE__c, Commercient33__ORDER_LINES__c, Commercient33__AR_OPEN_ITEMS__c, PriceBookEntry, Contact, Opportunity, QUOTE_HEADER__c, QUOTE_LINES__c, User, Pricebookentry, Commercient33__VWSAGEACCOUNTMATCHING__c, GlobalShop_Salesperson__c, PART_PRICE_CODE__c and 10 custom objects
• Object display names: Account, Product, Customer To Account Reverse Lookup, Invoice Header, Invoice Lines, Item Master, Item To Product Reverse Lookup, Sales Order Header, Sales Order Lines, Customer Master, Invoice Payments, Ship To Address, 51 more and 6 further templates
• Template groups: Account, Product, Invoice, Salesorder, Customer Multi Ship Addresses, Opportunity, CRM Opportunity and Line

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_GLOBALSHOP_User
• vw_Account
• vw_CustomerToAccountLookup
• vw_Customer
• vw_ShipToAddress
• vw_InvoiceHeader
• vw_InvoiceLines
• vw_InvoicePayment
• vw_SalesOrderHeader
• vw_SalesOrderLines

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