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

CRMPro → Salesforce — GlobalShop 2020: 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-2020.md, and that skill’s ERP table is what points at it. What follows is only what the shipped GlobalShop 2020 → 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
SYNC SALES PEOPLE	ERP SALESPEOPLE data becomes Commercient33__SALESPEOPLE__c in Salesforce. New records are created, existing ones updated, and records removed in the ERP are deleted.	Commercient33__SALESPEOPLE__c	SF_ERP_Salesforce_Clone_SALESPEOPLE
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, Commercient33__CUSTOMER_MASTER__c	SF_ERP_Salesforce_Clone_CUSTOMER_MASTER, SF_ERP_Salesforce_Clone_CUSTOMER_SHIPTO, SF_ERP_Salesforce_Clone_SALESPEOPLE, SF_ERP_Salesforce_Clone_CONTACT
CRM Ownership	The templates push user to Salesforce. New records are created, existing ones updated, and records removed in the ERP are deleted.	user	—
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_CUSTOMER_SHIPTO
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	SF_ERP_Salesforce_Clone_ORDER_HIST_HEAD, SF_ERP_Salesforce_Clone_SALESPEOPLE, CommercientFlags, SF_ERP_Salesforce_Clone_ORDER_HIST_LINE, SF_ERP_Salesforce_Clone_INVENTORY_MST2
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_SALESPEOPLE, CommercientFlags, 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
GET USER	user	—	0	vw_User	1=0	'' / ''	1
SYNC SALES PEOPLE	Commercient33__SALESPEOPLE__c	Commercient33__ExternalKey__c	2	vw_GLOBALSHOP2020_SalesPeople	vw_GLOBALSHOP2020_SalesPeople	Commercient33__ / __c	1
SYNC ACCOUNT	Account	CommercientSF__Commercient_ArCustomerCode__c	3	vw_GLOBALSHOP2020_Account	vw_GLOBALSHOP2020_Account	'' / ''	1
SYNC CUSTOMER	Commercient33__CUSTOMER_MASTER__c	Commercient33__ExternalKey__c	4	vw_GLOBALSHOP2020_Customer	vw_GLOBALSHOP2020_Customer	Commercient33__ / __c	1
SYNC CUSTOMERTOACCOUNTLOOKUP	Account	CommercientSF__Commercient_ArCustomerCode__c	5	vw_GLOBALSHOP2020_CustomerToAccountLookup	vw_GLOBALSHOP2020_CustomerToAccountLookup	'' / ''	1
SYNC SHIPTOADDRESS	Commercient33__CUSTOMER_SHIPTO__c	Commercient33__ExternalKey__c	6	vw_GLOBALSHOP2020_ShipToAddress	vw_GLOBALSHOP2020_ShipToAddress	Commercient33__ / __c	1
SYNC CONTACT	Contact	ExternalKey__c	7	vw_GLOBALSHOP2020_Contact	vw_GLOBALSHOP2020_Contact	'' / ''	1
SYNC SALES ORDER HEADER	Commercient33__ORDER_HEADER__c	Commercient33__ExternalKey__c	17	vw_GLOBALSHOP2020_SalesOrderHeader	vw_GLOBALSHOP2020_SalesOrderHeader	Commercient33__ / __c	1
SYNC SALES ORDER DETAIL	Commercient33__ORDER_LINES__c	Commercient33__ExternalKey__c	18	vw_GLOBALSHOP2020_SalesOrderDetail	vw_GLOBALSHOP2020_SalesOrderDetail	Commercient33__ / __c	1
SYNC INVOICE HEADER	Commercient33__ORDER_HIST_HEAD__c	Commercient33__ExternalKey__c	19	vw_GLOBALSHOP2020_InvoiceHeader	vw_GLOBALSHOP2020_InvoiceHeader	Commercient33__ / __c	1
SYNC INVOICE DETAIL	Commercient33__ORDER_HIST_LINE__c	Commercient33__ExternalKey__c	20	vw_GLOBALSHOP2020_InvoiceDetail	vw_GLOBALSHOP2020_InvoiceDetail	Commercient33__ / __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 is set on SYNC CONTACT. Text columns a template does not use are inserted as '' rather than left NULL. Get_SOQL_Query carries a query on SYNC ACCOUNT, SYNC CONTACT, GET USER — 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_GLOBALSHOP2020_SalesPeople	insert + update	vw_GLOBALSHOP2020_SalesPeople:	—	SF_ERP_Salesforce_Clone_SALESPEOPLE
vw_GLOBALSHOP2020_Account	insert + update	vw_GLOBALSHOP2020_Account:	vw_User:, vw_GLOBALSHOP2020_SalesPeople:	SF_ERP_Salesforce_Clone_CUSTOMER_MASTER, SF_ERP_Salesforce_Clone_CUSTOMER_SHIPTO, SF_ERP_Salesforce_Clone_SALESPEOPLE
vw_GLOBALSHOP2020_Customer	insert + update	vw_GLOBALSHOP2020_Customer:	vw_GLOBALSHOP2020_Account:, vw_GLOBALSHOP2020_SalesPeople:	SF_ERP_Salesforce_Clone_CUSTOMER_MASTER, SF_ERP_Salesforce_Clone_SALESPEOPLE
vw_GLOBALSHOP2020_CustomerToAccountLookup	insert + update	vw_GLOBALSHOP2020_CustomerToAccountLookup:	vw_GLOBALSHOP2020_Customer:	SF_ERP_Salesforce_Clone_CUSTOMER_MASTER
vw_GLOBALSHOP2020_ShipToAddress	insert + update	vw_GLOBALSHOP2020_ShipToAddress:	vw_GLOBALSHOP2020_Account:, vw_GLOBALSHOP2020_Customer:	SF_ERP_Salesforce_Clone_CUSTOMER_SHIPTO
vw_GLOBALSHOP2020_Contact	insert + update	vw_GLOBALSHOP2020_Contact:	vw_GLOBALSHOP2020_Account:	SF_ERP_Salesforce_Clone_CONTACT
vw_GLOBALSHOP2020_SalesOrderHeader	insert + update	vw_GLOBALSHOP2020_SalesOrderHeader:	vw_GLOBALSHOP2020_Account:, vw_GLOBALSHOP2020_Customer:, vw_GLOBALSHOP2020_SalesPeople:	SF_ERP_Salesforce_Clone_ORDER_HEADER, SF_ERP_Salesforce_Clone_SALESPEOPLE, CommercientFlags
vw_GLOBALSHOP2020_SalesOrderDetail	insert + update	vw_GLOBALSHOP2020_SalesOrderDetail:	vw_GLOBALSHOP2020_SalesOrderHeader:, vw_GLOBALSHOP2020_Product:, vw_GLOBALSHOP2020_Item:	SF_ERP_Salesforce_Clone_ORDER_LINES
vw_GLOBALSHOP2020_InvoiceHeader	insert + update	vw_GLOBALSHOP2020_InvoiceHeader:	vw_GLOBALSHOP2020_Account:, vw_GLOBALSHOP2020_Customer:, vw_GLOBALSHOP2020_SalesPeople:	SF_ERP_Salesforce_Clone_ORDER_HIST_HEAD, SF_ERP_Salesforce_Clone_SALESPEOPLE, CommercientFlags
vw_GLOBALSHOP2020_InvoiceDetail	insert + update	vw_GLOBALSHOP2020_InvoiceDetail:	vw_GLOBALSHOP2020_InvoiceHeader:, vw_GLOBALSHOP2020_Product:, vw_GLOBALSHOP2020_Item:	SF_ERP_Salesforce_Clone_ORDER_HIST_LINE, SF_ERP_Salesforce_Clone_INVENTORY_MST2

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

• 0 — GET USER
• 2 — SYNC SALES PEOPLE
• 3 — SYNC ACCOUNT
• 4 — SYNC CUSTOMER
• 5 — SYNC CUSTOMERTOACCOUNTLOOKUP
• 6 — SYNC SHIPTOADDRESS
• 7 — SYNC CONTACT
• 17 — SYNC SALES ORDER HEADER
• 18 — SYNC SALES ORDER DETAIL
• 19 — SYNC INVOICE HEADER
• 20 — SYNC INVOICE DETAIL

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_GLOBALSHOP2020_Account reads vw_User:, vw_GLOBALSHOP2020_SalesPeople:
• vw_GLOBALSHOP2020_CustomerToAccountLookup reads vw_GLOBALSHOP2020_Customer:
• vw_GLOBALSHOP2020_Contact reads vw_GLOBALSHOP2020_Account:
• vw_GLOBALSHOP2020_Customer reads vw_GLOBALSHOP2020_Account:, vw_GLOBALSHOP2020_SalesPeople:
• vw_GLOBALSHOP2020_ShipToAddress reads vw_GLOBALSHOP2020_Account:, vw_GLOBALSHOP2020_Customer:
• vw_GLOBALSHOP2020_InvoiceHeader reads vw_GLOBALSHOP2020_Account:, vw_GLOBALSHOP2020_Customer:, vw_GLOBALSHOP2020_SalesPeople:
• vw_GLOBALSHOP2020_InvoiceDetail reads vw_GLOBALSHOP2020_InvoiceHeader:, vw_GLOBALSHOP2020_Product:, vw_GLOBALSHOP2020_Item:; no template in this set writes vw_GLOBALSHOP2020_Product:, vw_GLOBALSHOP2020_Item:
• vw_GLOBALSHOP2020_SalesOrderHeader reads vw_GLOBALSHOP2020_Account:, vw_GLOBALSHOP2020_Customer:, vw_GLOBALSHOP2020_SalesPeople:
• vw_GLOBALSHOP2020_SalesOrderDetail reads vw_GLOBALSHOP2020_SalesOrderHeader:, vw_GLOBALSHOP2020_Product:, vw_GLOBALSHOP2020_Item:; no template in this set writes vw_GLOBALSHOP2020_Product:, vw_GLOBALSHOP2020_Item:

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
SYNC SALES PEOPLE	Commercient33__SALESPEOPLE__c	7	KEY1 → Commercient33__KEY1__c, KEY2 → Commercient33__KEY2__c, SALESPERSON_CODE → SALESPERSON_CODE, FILLER → Commercient33__FILLER__c, SALESPERSON → Commercient33__SALESPERSON__c
SYNC ACCOUNT	Account	15	CommercientSFommercient_ArCustomerCode → CommercientSF__Commercient_ArCustomerCode__c, Phone → Phone, BillingStreet → BillingStreet, BillingCity → BillingCity, BillingCountry → BillingCountry
SYNC CUSTOMER	Commercient33__CUSTOMER_MASTER__c	29	Account → Account, GlobalShop_Salesperson → Commercient33__GlobalShop_Salesperson__c, CUSTOMER → Commercient33__CUSTOMER__c, REC → REC, NAME_CUSTOMER → NAME_CUSTOMER
SYNC CUSTOMERTOACCOUNTLOOKUP	Account	2	CommercientSFommercient_ArCustomerCode → CommercientSF__Commercient_ArCustomerCode__c, Commercient33__GlobalShop_Customer_Master → Commercient33__GlobalShop_Customer_Master__c
SYNC SHIPTOADDRESS	Commercient33__CUSTOMER_SHIPTO__c	28	CUSTOMER → Commercient33__CUSTOMER__c, REC → REC, NAME_CUSTOMER_SHIP → NAME_CUSTOMER_SHIP, ADDRESS1_SHIP → Commercient33__ADDRESS1_SHIP__c, ADDRESS2_SHIP → Commercient33__ADDRESS2_SHIP__c
SYNC CONTACT	Contact	13	Salutation → Salutation, FirstName → FirstName, LastName → LastName, Phone → Phone, MobilePhone → MobilePhone
SYNC SALES ORDER HEADER	Commercient33__ORDER_HEADER__c	99	Account → Account, GlobalShop_Customer_Master → GlobalShop_Customer_Master, GlobalShop_Salesperson → Commercient33__GlobalShop_Salesperson__c, ORDER_NO → Commercient33__ORDER_NO__c, RECORD_NO → RECORD_NO
SYNC SALES ORDER DETAIL	Commercient33__ORDER_LINES__c	99	GlobalShop_Sales_Order_Header → Commercient33__GlobalShop_Sales_Order_Header__c, Product → Product__c, GlobalShop_Inventory_Master → GlobalShop_Inventory_Master__c, ORDER_NO → Commercient33__ORDER_NO__c, RECORD_NO → RECORD_NO
SYNC INVOICE HEADER	Commercient33__ORDER_HIST_HEAD__c	99	Account → Account, GlobalShop_Customer_Master → GlobalShop_Customer_Master, GlobalShop_Salesperson → Commercient33__GlobalShop_Salesperson__c, INVOICE → INVOICE, ORDER_NO → Commercient33__ORDER_NO__c
SYNC INVOICE DETAIL	Commercient33__ORDER_HIST_LINE__c	100	GlobalShop_Invoice_Header → GlobalShop_Invoice_Header, Product → Commercient33__Product__c, GlobalShop_Inventory_Master → GlobalShop_Inventory_Master__c, INVOICE → INVOICE, ORDER_NO → Commercient33__ORDER_NO__c

6. Community templates

The catalogue carries 27 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: 27
• Default operations: insert on 27, update on 27, delete on 27
• Marked circular-sync: 0
• Licence groups they span: 13
• Destination objects: Account, Commercient33__ORDER_HIST_HEAD__c, Commercient33__QUOTE_HEADER__c, Commercient33__QUOTE_LINES__c, OpportunityLineItem, PriceBookEntry, Product2, Commercient33__CUSTOMER_MASTER__c, Commercient33__CUSTOMER_SHIPTO__c, Commercient33__ORDER_HEADER__c, Commercient33__ORDER_HIST_LINE__c, Commercient33__ORDER_LINES__c, Commercient33__SALESPEOPLE__c, Contact, Opportunity, user and 4 custom objects
• Object display names: SYNC QUOTE HEADER, GET USER, SYNC ACCOUNT, SYNC AR_TERMS, SYNC CONTACT, SYNC CUSTOMER, SYNC CUSTOMERTOACCOUNTLOOKUP, SYNC INVOICE DETAIL, SYNC INVOICE HEADER, SYNC ITEM, SYNC ITEMTOPRODUCTLOOKUP, SYNC PRODUCT, 9 more and 4 further templates
• Template groups: Product, Account, Opportunity, CRM Opportunity and Line, 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_GLOBALSHOP2020_SalesPeople
• vw_GLOBALSHOP2020_Account
• vw_GLOBALSHOP2020_CustomerToAccountLookup
• vw_GLOBALSHOP2020_Contact
• vw_User
• vw_GLOBALSHOP2020_Customer
• vw_GLOBALSHOP2020_ShipToAddress
• vw_GLOBALSHOP2020_InvoiceHeader
• vw_GLOBALSHOP2020_InvoiceDetail
• vw_GLOBALSHOP2020_SalesOrderHeader
• vw_GLOBALSHOP2020_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 GlobalShop 2020 → 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.