CRMPro → Salesforce — Exact Globe Next: what the shipped templates set up

CRMPro → Salesforce — Exact Globe Next: 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/exact-globe-next.md, and that skill’s ERP table is what points at it. What follows is only what the shipped Exact Globe Next → 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 USERS	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, Contact, CommercientSF19__MACOLAGLOBE_Customer__c, CommercientSF19__MACOLAGLOBE_SalesRep__c	CommercientFlags, SF_ERP_Salesforce_Clone_cicmpy, CompanyP, SF_ERP_Salesforce_Clone_land, SF_ERP_Salesforce_Clone_AddressStates, SF_ERP_Salesforce_Clone_cicntp
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.	CommercientSF19__MACOLAGLOBE_Addresses__c	CommercientFlags, SF_ERP_Salesforce_Clone_Addresses, CompanyP
Invoice History Headers	The Invoices from the ERP invoice module are synchronized to the Commercient Invoice Header (MCO) object in CRM. Customer service and sales people can visualize the status of the Invoice such as open, closed, as well as the balance remaining and the due date. New records are created, existing ones updated, and records removed in the ERP are deleted.	CommercientSF19__MACOLAGLOBE_InvoiceHeader__c, CommercientSF19__MACOLAGLOBE_InvoiceLines__c	CommercientFlags, SF_ERP_Salesforce_Clone_frhkrg, CompanyP, SF_ERP_Salesforce_Clone_cicmpy, SF_ERP_Salesforce_Clone_frhsrg
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.	CommercientSF19__MACOLAGLOBE_SalesOrderHeader__c, CommercientSF19__MACOLAGLOBE_SalesOrderLines__c	CommercientFlags, SF_ERP_Salesforce_Clone_orkrg, CompanyP, SF_ERP_Salesforce_Clone_cicmpy, SF_ERP_Salesforce_Clone_orsrg

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 USERS	User	—	0	vw_EXACTGLOBENEXT_User	1=0	'' / ''	1
SYNC ACCOUNT	Account	CommercientSF__Commercient_ArCustomerCode__c	1	vw_EXACTGLOBENEXT_Account	vw_EXACTGLOBENEXT_Account	'' / ''	1
SYNC SALESPERSON	CommercientSF19__MACOLAGLOBE_SalesRep__c	CommercientSF19__ExternalKey__c	1	vw_EXACTGLOBENEXT_Salesperson	vw_EXACTGLOBENEXT_Salesperson	CommercientSF19__ / __c	1
SYNC SHIPTOACCOUNT	Account	CommercientSF__Commercient_ArCustomerCode__c	2	vw_EXACTGLOBENEXT_ShipToAccount	vw_EXACTGLOBENEXT_ShipToAccount	'' / ''	1
SYNC CUSTOMER	CommercientSF19__MACOLAGLOBE_Customer__c	CommercientSF19__ExternalKey__c	3	vw_EXACTGLOBENEXT_Customer	vw_EXACTGLOBENEXT_Customer	CommercientSF19__ / __c	1
SYNC CUSTOMER TO ACCOUNT LOOKUP	Account	CommercientSF__Commercient_ArCustomerCode__c	4	vw_EXACTGLOBENEXT_CustomerToAccountLookup	vw_EXACTGLOBENEXT_CustomerToAccountLookup	'' / ''	1
SYNC ADDRESS	CommercientSF19__MACOLAGLOBE_Addresses__c	CommercientSF19__ExternalKey__c	5	vw_EXACTGLOBENEXT_Address	vw_EXACTGLOBENEXT_Address	CommercientSF19__ / __c	1
SYNC CONTACT	Contact	ExternalKey__c	6	vw_EXACTGLOBENEXT_Contact	vw_EXACTGLOBENEXT_Contact	'' / ''	1
SYNC SALES ORDER HEADER	CommercientSF19__MACOLAGLOBE_SalesOrderHeader__c	CommercientSF19__ExternalKey__c	16	vw_EXACTGLOBENEXT_SalesOrderHeader	vw_EXACTGLOBENEXT_SalesOrderHeader	CommercientSF19__ / __c	1
SYNC SALES ORDER DETAIL	CommercientSF19__MACOLAGLOBE_SalesOrderLines__c	CommercientSF19__ExternalKey__c	17	vw_EXACTGLOBENEXT_SalesOrderDetail	vw_EXACTGLOBENEXT_SalesOrderDetail	CommercientSF19__ / __c	1
SYNC INVOICE HISTORY HEADER	CommercientSF19__MACOLAGLOBE_InvoiceHeader__c	CommercientSF19__ExternalKey__c	18	vw_EXACTGLOBENEXT_InvoiceHistoryHeader	vw_EXACTGLOBENEXT_InvoiceHistoryHeader	CommercientSF19__ / __c	1
SYNC INVOICEHISTORYDETAIL	CommercientSF19__MACOLAGLOBE_InvoiceLines__c	CommercientSF19__ExternalKey__c	19	vw_EXACTGLOBENEXT_InvoiceHistoryDetail	vw_EXACTGLOBENEXT_InvoiceHistoryDetail	CommercientSF19__ / __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 USERS, SYNC ACCOUNT, SYNC SHIPTOACCOUNT — 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_EXACTGLOBENEXT_Account	insert + update	vw_EXACTGLOBENEXT_Account:	vw_EXACTGLOBENEXT_User:	CommercientSF__Commercient_ArCustomerCode__c	CommercientFlags, SF_ERP_Salesforce_Clone_cicmpy, CompanyP, SF_ERP_Salesforce_Clone_land, SF_ERP_Salesforce_Clone_AddressStates
vw_EXACTGLOBENEXT_Salesperson	insert + update	vw_EXACTGLOBENEXT_Salesperson:	—	ExternalKey	CommercientFlags, SF_ERP_Salesforce_Clone_humres, CompanyP
vw_EXACTGLOBENEXT_ShipToAccount	insert + update	vw_EXACTGLOBENEXT_ShipToAccount:	vw_EXACTGLOBENEXT_Account:, vw_EXACTGLOBENEXT_User:	CommercientSF__Commercient_ArCustomerCode__c	CommercientFlags, SF_ERP_Salesforce_Clone_cicmpy, CompanyP, SF_ERP_Salesforce_Clone_land, SF_ERP_Salesforce_Clone_AddressStates
vw_EXACTGLOBENEXT_Customer	insert + update	vw_EXACTGLOBENEXT_Customer:	vw_EXACTGLOBENEXT_Account:, vw_EXACTGLOBENEXT_ShipToAccount:	ExternalKey	CommercientFlags, SF_ERP_Salesforce_Clone_cicmpy, CompanyP
vw_EXACTGLOBENEXT_CustomerToAccountLookup	insert + update	vw_EXACTGLOBENEXT_CustomerToAccountLookup:	vw_EXACTGLOBENEXT_Account:, vw_EXACTGLOBENEXT_Customer:, vw_EXACTGLOBENEXT_ShipToAccount:	—	CommercientFlags, SF_ERP_Salesforce_Clone_cicmpy, CompanyP
vw_EXACTGLOBENEXT_Address	insert + update	vw_EXACTGLOBENEXT_Address:	vw_EXACTGLOBENEXT_Customer:	ExternalKey	CommercientFlags, SF_ERP_Salesforce_Clone_Addresses, CompanyP
vw_EXACTGLOBENEXT_Contact	insert + update	vw_EXACTGLOBENEXT_Contact:	vw_EXACTGLOBENEXT_Account:, vw_EXACTGLOBENEXT_Customer:, vw_EXACTGLOBENEXT_User:, vw_EXACTGLOBENEXT_ShipToAccount:	ExternalKey__c	CommercientFlags, SF_ERP_Salesforce_Clone_cicntp, CompanyP, SF_ERP_Salesforce_Clone_cicmpy
vw_EXACTGLOBENEXT_SalesOrderHeader	insert + update	vw_EXACTGLOBENEXT_SalesOrderHeader:	vw_EXACTGLOBENEXT_Account:, vw_EXACTGLOBENEXT_Customer:, vw_EXACTGLOBENEXT_User:, vw_EXACTGLOBENEXT_ShipToAccount:	ExternalKey	CommercientFlags, SF_ERP_Salesforce_Clone_orkrg, CompanyP, SF_ERP_Salesforce_Clone_cicmpy
vw_EXACTGLOBENEXT_SalesOrderDetail	insert + update	vw_EXACTGLOBENEXT_SalesOrderDetail:	vw_EXACTGLOBENEXT_SalesOrderHeader:, vw_EXACTGLOBENEXT_Account:, vw_EXACTGLOBENEXT_User:, vw_EXACTGLOBENEXT_Product:, vw_EXACTGLOBENEXT_Item:, vw_EXACTGLOBENEXT_ShipToAccount:	ExternalKey	CommercientFlags, SF_ERP_Salesforce_Clone_orsrg, CompanyP, SF_ERP_Salesforce_Clone_orkrg, SF_ERP_Salesforce_Clone_cicmpy
vw_EXACTGLOBENEXT_InvoiceHistoryHeader	insert + update	vw_EXACTGLOBENEXT_InvoiceHistoryHeader:	vw_EXACTGLOBENEXT_Account:, vw_EXACTGLOBENEXT_Customer:, vw_EXACTGLOBENEXT_User:, vw_EXACTGLOBENEXT_ShipToAccount:	ExternalKey	CommercientFlags, SF_ERP_Salesforce_Clone_frhkrg, CompanyP, SF_ERP_Salesforce_Clone_cicmpy
vw_EXACTGLOBENEXT_InvoiceHistoryDetail	insert + update	vw_EXACTGLOBENEXT_InvoiceHistoryDetail:	vw_EXACTGLOBENEXT_Account:, vw_EXACTGLOBENEXT_InvoiceHistoryHeader:, vw_EXACTGLOBENEXT_User:, vw_EXACTGLOBENEXT_Product:, vw_EXACTGLOBENEXT_Item:, vw_EXACTGLOBENEXT_ShipToAccount:	ExternalKey	CommercientFlags, SF_ERP_Salesforce_Clone_frhsrg, CompanyP, SF_ERP_Salesforce_Clone_frhkrg, SF_ERP_Salesforce_Clone_cicmpy

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

• 0 — GET USERS
• 1 — SYNC ACCOUNT, SYNC SALESPERSON
• 2 — SYNC SHIPTOACCOUNT
• 3 — SYNC CUSTOMER
• 4 — SYNC CUSTOMER TO ACCOUNT LOOKUP
• 5 — SYNC ADDRESS
• 6 — SYNC CONTACT
• 16 — SYNC SALES ORDER HEADER
• 17 — SYNC SALES ORDER DETAIL
• 18 — SYNC INVOICE HISTORY HEADER
• 19 — SYNC INVOICEHISTORYDETAIL

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_EXACTGLOBENEXT_Account reads vw_EXACTGLOBENEXT_User:
• vw_EXACTGLOBENEXT_ShipToAccount reads vw_EXACTGLOBENEXT_Account:, vw_EXACTGLOBENEXT_User:
• vw_EXACTGLOBENEXT_CustomerToAccountLookup reads vw_EXACTGLOBENEXT_Account:, vw_EXACTGLOBENEXT_Customer:, vw_EXACTGLOBENEXT_ShipToAccount:
• vw_EXACTGLOBENEXT_Contact reads vw_EXACTGLOBENEXT_Account:, vw_EXACTGLOBENEXT_Customer:, vw_EXACTGLOBENEXT_User:, vw_EXACTGLOBENEXT_ShipToAccount:
• vw_EXACTGLOBENEXT_Customer reads vw_EXACTGLOBENEXT_Account:, vw_EXACTGLOBENEXT_ShipToAccount:
• vw_EXACTGLOBENEXT_Address reads vw_EXACTGLOBENEXT_Customer:
• vw_EXACTGLOBENEXT_InvoiceHistoryHeader reads vw_EXACTGLOBENEXT_Account:, vw_EXACTGLOBENEXT_Customer:, vw_EXACTGLOBENEXT_User:, vw_EXACTGLOBENEXT_ShipToAccount:
• vw_EXACTGLOBENEXT_InvoiceHistoryDetail reads vw_EXACTGLOBENEXT_Account:, vw_EXACTGLOBENEXT_InvoiceHistoryHeader:, vw_EXACTGLOBENEXT_User:, vw_EXACTGLOBENEXT_Product:, vw_EXACTGLOBENEXT_Item:, vw_EXACTGLOBENEXT_ShipToAccount:; no template in this set writes vw_EXACTGLOBENEXT_Product:, vw_EXACTGLOBENEXT_Item:
• vw_EXACTGLOBENEXT_SalesOrderHeader reads vw_EXACTGLOBENEXT_Account:, vw_EXACTGLOBENEXT_Customer:, vw_EXACTGLOBENEXT_User:, vw_EXACTGLOBENEXT_ShipToAccount:
• vw_EXACTGLOBENEXT_SalesOrderDetail reads vw_EXACTGLOBENEXT_SalesOrderHeader:, vw_EXACTGLOBENEXT_Account:, vw_EXACTGLOBENEXT_User:, vw_EXACTGLOBENEXT_Product:, vw_EXACTGLOBENEXT_Item:, vw_EXACTGLOBENEXT_ShipToAccount:; no template in this set writes vw_EXACTGLOBENEXT_Product:, vw_EXACTGLOBENEXT_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 ACCOUNT	Account	14	CommercientSFommercient_ArCustomerCode → CommercientSF__Commercient_ArCustomerCode__c, BillingStreet → BillingStreet, BillingPostalCode → BillingPostalCode, BillingCity → BillingCity, BillingState → BillingState
SYNC SALESPERSON	CommercientSF19__MACOLAGLOBE_SalesRep__c	160	res_id → CommercientSF19__res_id__c, fullname → CommercientSF19__fullname__c, sur_name → CommercientSF19__sur_name__c, first_name → CommercientSF19__first_name__c, middle_name → CommercientSF19__middle_name__c
SYNC SHIPTOACCOUNT	Account	14	CommercientSFommercient_ArCustomerCode → CommercientSF__Commercient_ArCustomerCode__c, BillingStreet → BillingStreet, BillingPostalCode → BillingPostalCode, BillingCity → BillingCity, BillingState → BillingState
SYNC CUSTOMER	CommercientSF19__MACOLAGLOBE_Customer__c	342	cmp_wwn → CommercientSF19__cmp_wwn__c, cmp_code → cmp_code, cnt_id → CommercientSF19__cnt_id__c, cmp_parent → CommercientSF19__cmp_parent__c, cmp_name → CommercientSF19__cmp_name__c
SYNC CUSTOMER TO ACCOUNT LOOKUP	Account	2	CommercientSFommercient_ArCustomerCode → CommercientSF__Commercient_ArCustomerCode__c, CommercientSF19__MACOLAGLOBE_Customer → CommercientSF19__MACOLAGLOBE_Customer__c
SYNC ADDRESS	CommercientSF19__MACOLAGLOBE_Addresses__c	66	IDCol → IDCol, Type → CommercientSF19__Type__c, ContactPerson → ContactPerson, AddressLine1 → CommercientSF19__AddressLine1__c, AddressLine2 → CommercientSF19__AddressLine2__c
SYNC CONTACT	Contact	12	Salutation → Salutation, FirstName → FirstName, LastName → LastName, Fax → Fax, Phone → Phone
SYNC SALES ORDER HEADER	CommercientSF19__MACOLAGLOBE_SalesOrderHeader__c	168	ordernr → CommercientSF19__ordernr__c, fakdebnr → CommercientSF19__fakdebnr__c, verzdebnr → CommercientSF19__verzdebnr__c, naldebnr → CommercientSF19__naldebnr__c, einddebnr → einddebnr__c
SYNC SALES ORDER DETAIL	CommercientSF19__MACOLAGLOBE_SalesOrderLines__c	130	ordernr → CommercientSF19__ordernr__c, regel → regel__c, afldat → afldat__c, artcode → artcode, ar_soort → CommercientSF19__ar_soort__c
SYNC INVOICE HISTORY HEADER	CommercientSF19__MACOLAGLOBE_InvoiceHeader__c	143	faknr → faknr__c, fakdat → fakdat__c, dagbknr → dagbknr__c, debnr → debnr__c, fakdebnr → fakdebnr__c
SYNC INVOICEHISTORYDETAIL	CommercientSF19__MACOLAGLOBE_InvoiceLines__c	80	fakdat → fakdat__c, dagbknr → dagbknr__c, regel → regel__c, artcode → artcode, ar_soort → CommercientSF19__ar_soort__c

6. Community templates

The catalogue carries 138 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: 138
• Default operations: insert on 138, update on 138, delete on 138
• Marked circular-sync: 18
• Licence groups they span: 11
• Destination objects: Account, Product2, CommercientSF19__MACOLAGLOBE_Customer__c, PriceBookEntry, CommercientSF19__MACOLAGLOBE_InvoiceHeader__c, CommercientSF19__MACOLAGLOBE_Addresses__c, CommercientSF19__MACOLAGLOBE_InvoiceLines__c, CommercientSF19__MACOLAGLOBE_SalesOrderHeader__c, CommercientSF19__MACOLAGLOBE_SalesOrderLines__c, Contact, CommercientSF19__MACOLAGLOBE_Items__c, CommercientSF19__MACOLAGLOBE_SalesRep__c, User, CommercientSF19__ACCOUNTMATCHING__c, CommercientSF19__ADDRESS__c, CommercientSF19__CONTACT__c, CommercientSF19__INVOICEDETAIL__c, CommercientSF19__ITEM__c, CommercientSF19__ITEMTOPRODUCTLOOKUP__c, CommercientSF19__PRODUCT__c, 2 more and 5 custom objects
• Object display names: SYNC ACCOUNT, SYNC CUSTOMER, SYNC CUSTOMER TO ACCOUNT LOOKUP, SYNC ADDRESS, SYNC CONTACT, SYNC SHIPTOACCOUNT, SYNC INVOICE HISTORY HEADER, SYNC INVOICEHISTORYDETAIL, SYNC ITEM, SYNC ITEM TO PRODUCT LOOKUP, SYNC PRODUCT, SYNC SALES ORDER DETAIL, 14 more and 6 further templates
• Template groups: Account, Product, Invoice History Headers, Salesorder, Customer Multi Ship Addresses, Invoice

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_EXACTGLOBENEXT_User
• vw_EXACTGLOBENEXT_Account
• vw_EXACTGLOBENEXT_ShipToAccount
• vw_EXACTGLOBENEXT_CustomerToAccountLookup
• vw_EXACTGLOBENEXT_Contact
• vw_EXACTGLOBENEXT_Customer
• vw_EXACTGLOBENEXT_Address
• vw_EXACTGLOBENEXT_InvoiceHistoryHeader
• vw_EXACTGLOBENEXT_InvoiceHistoryDetail
• vw_EXACTGLOBENEXT_SalesOrderHeader
• vw_EXACTGLOBENEXT_SalesOrderDetail
• vw_EXACTGLOBENEXT_Salesperson

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 Exact Globe Next → 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.