Source ERP · 6 of 27
CRMPro → Zoho CRM — GlobalShop: what the shipped templates set up
Read it in the terminal with "dlake skills show dlake-crmpro-zohocrm/erps/globalshop". It extends the dlake-crmpro-zohocrm skill, which holds what is true whatever the source ERP.
CRMPro → Zoho CRM — GlobalShop: what the shipped templates set up
Keep this skill current.
dlakeships updates often and this text is embedded in the CLI you have installed. Before relying on it, comparedlake --versionwithnpm view @commercient/dlake version; if they differ, runnpm install -g @commercient/dlake@latestand thendlake 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-zohocrm is the destination skill this page is a child of, and the authority for the
Zoho CRM 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-zohocrm/erps/globalshop.md, and that
skill’s ERP table is what points at it. What follows is only what the shipped GlobalShop → Zoho
CRM 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 |
|---|---|---|---|
| Users | The templates push users to Zoho CRM. New records are created and existing ones updated; none are deleted. | users | — |
| Globalshop Term | The templates push commercientglobalshop__GlobalShop_Terms to Zoho CRM. New records are created and existing ones updated; none are deleted. | commercientglobalshop__GlobalShop_Terms | SF_ERP_Salesforce_Clone_AR_TERMS |
| Globalshop SalesPerson | The templates push commercientglobalshop__GlobalShop_Salespersons to Zoho CRM. New records are created and existing ones updated; none are deleted. | commercientglobalshop__GlobalShop_Salespersons | SF_ERP_Salesforce_Clone_SALESPEOPLE |
| Account | The templates push Accounts to Zoho CRM. New records are created and existing ones updated; none are deleted. | Accounts | SF_ERP_Salesforce_Clone_CUSTOMER_MASTER, SF_ERP_Salesforce_Clone_V_OE_MULTI_SHIP |
| Globalshop Customer | The templates push commercientglobalshop__GlobalShop_Customer to Zoho CRM. New records are created and existing ones updated; none are deleted. | commercientglobalshop__GlobalShop_Customer | SF_ERP_Salesforce_Clone_CUSTOMER_MASTER |
| Contacts | The templates push Contacts to Zoho CRM. New records are created and existing ones updated; none are deleted. | Contacts | SF_ERP_Salesforce_Clone_CONTACT |
| Globalshop ShipTo | The templates push commercientglobalshop__GlobalShop_ShipToAddress to Zoho CRM. New records are created and existing ones updated; none are deleted. | commercientglobalshop__GlobalShop_ShipToAddress | SF_ERP_Salesforce_Clone_V_OE_MULTI_SHIP |
| Products | The templates push Products to Zoho CRM. New records are created and existing ones updated; none are deleted. | Products | SF_ERP_Salesforce_Clone_INVENTORY_MSTR |
| Globalshop Item | The templates push commercientglobalshop__GlobalShop_Item_Master to Zoho CRM. New records are created and existing ones updated; none are deleted. | commercientglobalshop__GlobalShop_Item_Master | SF_ERP_Salesforce_Clone_INVENTORY_MSTR |
| Globalshop SalesOrder | The templates push commercientglobalshop__GlobalShop_SO_Header to Zoho CRM. New records are created and existing ones updated; none are deleted. | commercientglobalshop__GlobalShop_SO_Header | SF_ERP_Salesforce_Clone_ORDER_HEADER |
| GLOBALSHOP ItemList | The templates push commercientglobalshop__GlobalShop_Item_List to Zoho CRM. New records are created and existing ones updated; none are deleted. | commercientglobalshop__GlobalShop_Item_List | SF_ERP_Salesforce_Clone_ITEM_MASTER |
| Globalshop SalesOrderLine | The templates push commercientglobalshop__GlobalShop_SO_Line to Zoho CRM. New records are created and existing ones updated; none are deleted. | commercientglobalshop__GlobalShop_SO_Line | SF_ERP_Salesforce_Clone_ORDER_LINES |
| Globalshop Invoice | The templates push commercientglobalshop__GlobalShop_Invoice_Header to Zoho CRM. New records are created and existing ones updated; none are deleted. | commercientglobalshop__GlobalShop_Invoice_Header | SF_ERP_Salesforce_Clone_ORDER_HIST_HEAD |
| Globalshop InvoiceLine | The templates push commercientglobalshop__GlobalShop_Invoice_Line to Zoho CRM. New records are created and existing ones updated; none are deleted. | commercientglobalshop__GlobalShop_Invoice_Line | SF_ERP_Salesforce_Clone_ORDER_HIST_LINE |
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 |
|---|---|---|---|---|---|---|
| Users | users | Commercient_ExternalKey | 0 | SalesRep: | SELECT 1 | '' / '' |
| Globalshop Term | commercientglobalshop__GlobalShop_Terms | commercientglobalshop__Commercient_ExternalKey | 1 | vw_GLOBALSHOP_Term: | vw_GLOBALSHOP_Term | commercientglobalshop__ / __c |
| Globalshop SalesPerson | commercientglobalshop__GlobalShop_Salespersons | commercientglobalshop__Commercient_ExternalKey | 2 | vw_GLOBALSHOP_SalesPerspon: | vw_GLOBALSHOP_SalesPerspon | commercientglobalshop__ / __c |
| Account | Accounts | Commercient_ExternalKey | 3 | vw_GLOBALSHOP_Account: | vw_GLOBALSHOP_Account | '' / '' |
| Globalshop Customer | commercientglobalshop__GlobalShop_Customer | commercientglobalshop__Commercient_ExternalKey | 4 | vw_GLOBALSHOP_Customer: | vw_GLOBALSHOP_Customer | commercientglobalshop__ / __c |
| Contacts | Contacts | Commercient_ExternalKey | 4 | vw_GLOBALSHOP_Contact: | vw_GLOBALSHOP_Contact | '' / '' |
| Globalshop ShipTo | commercientglobalshop__GlobalShop_ShipToAddress | commercientglobalshop__Commercient_ExternalKey | 5 | vw_GLOBALSHOP_ShipTo: | vw_GLOBALSHOP_ShipTo | commercientglobalshop__ / __c |
| Products | Products | Commercient_ExternalKey | 6 | vw_GLOBALSHOP_Product: | vw_GLOBALSHOP_Product | '' / '' |
| Globalshop Item | commercientglobalshop__GlobalShop_Item_Master | commercientglobalshop__Commercient_ExternalKey | 7 | vw_GLOBALSHOP_Item: | vw_GLOBALSHOP_Item | commercientglobalshop__ / '' |
| Globalshop SalesOrder | commercientglobalshop__GlobalShop_SO_Header | commercientglobalshop__Commercient_ExternalKey | 8 | vw_GLOBALSHOP_SalesOrder: | vw_GLOBALSHOP_SalesOrder | commercientglobalshop__ / '' |
| GLOBALSHOP ItemList | commercientglobalshop__GlobalShop_Item_List | commercientglobalshop__Commercient_ExternalKey | 8 | vw_GLOBALSHOP_ItemList: | vw_GLOBALSHOP_ItemList | commercientglobalshop__ / __c |
| Globalshop SalesOrderLine | commercientglobalshop__GlobalShop_SO_Line | commercientglobalshop__Commercient_ExternalKey | 9 | vw_GLOBALSHOP_SalesOrderLine: | vw_GLOBALSHOP_SalesOrderLine | commercientglobalshop__ / '' |
| Globalshop Invoice | commercientglobalshop__GlobalShop_Invoice_Header | commercientglobalshop__Commercient_ExternalKey | 10 | vw_GLOBALSHOP_Invoice: | vw_GLOBALSHOP_Invoice | commercientglobalshop__ / '' |
| Globalshop InvoiceLine | commercientglobalshop__GlobalShop_Invoice_Line | commercientglobalshop__Commercient_ExternalKey | 11 | vw_GLOBALSHOP_InvoiceLine: | vw_GLOBALSHOP_InvoiceLine | commercientglobalshop__ / '' |
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. Get_SOQL_Query carries a query on Products — those rows
read records back from Zoho CRM 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_GLOBALSHOP_Term | insert-only | — | vw_GLOBALSHOP_Term: | Commercient_ExternalKey | SF_ERP_Salesforce_Clone_AR_TERMS |
vw_GLOBALSHOP_SalesPerspon | insert-only | — | vw_GLOBALSHOP_SalesPerspon: | Commercient_ExternalKey | SF_ERP_Salesforce_Clone_SALESPEOPLE |
vw_GLOBALSHOP_Account | insert-only | — | vw_GLOBALSHOP_Account: | — | SF_ERP_Salesforce_Clone_CUSTOMER_MASTER, SF_ERP_Salesforce_Clone_V_OE_MULTI_SHIP |
vw_GLOBALSHOP_Customer | insert + update | — | vw_GLOBALSHOP_Account:, vw_GLOBALSHOP_Customer: | — | SF_ERP_Salesforce_Clone_CUSTOMER_MASTER |
vw_GLOBALSHOP_Contact | insert-only | — | vw_GLOBALSHOP_Account:, vw_GLOBALSHOP_Contact: | Commercient_ExternalKey | SF_ERP_Salesforce_Clone_CONTACT |
vw_GLOBALSHOP_ShipTo | insert + update | — | vw_GLOBALSHOP_Account:, vw_GLOBALSHOP_Customer:, vw_GLOBALSHOP_ShipTo: | Commercient_ExternalKey | SF_ERP_Salesforce_Clone_V_OE_MULTI_SHIP |
vw_GLOBALSHOP_Product | insert + update | — | vw_GLOBALSHOP_Item:, vw_GLOBALSHOP_Product: | Commercient_ExternalKey__c, Commercient_ExternalKey | SF_ERP_Salesforce_Clone_INVENTORY_MSTR |
vw_GLOBALSHOP_Item | insert + update | — | vw_GLOBALSHOP_Product:, vw_GLOBALSHOP_Item: | Commercient_ExternalKey | SF_ERP_Salesforce_Clone_INVENTORY_MSTR |
vw_GLOBALSHOP_SalesOrder | insert + update | — | vw_GLOBALSHOP_Account:, vw_GLOBALSHOP_Customer:, vw_GLOBALSHOP_SalesOrder: | Commercient_ExternalKey | SF_ERP_Salesforce_Clone_ORDER_HEADER |
vw_GLOBALSHOP_ItemList | insert + update | — | vw_GLOBALSHOP_Product:, vw_GLOBALSHOP_Item:, vw_GLOBALSHOP_ItemList: | Commercient_ExternalKey | SF_ERP_Salesforce_Clone_ITEM_MASTER |
vw_GLOBALSHOP_SalesOrderLine | insert + update | — | vw_GLOBALSHOP_SalesOrder:, vw_GLOBALSHOP_Product:, vw_GLOBALSHOP_Item:, vw_GLOBALSHOP_SalesOrderLine: | Commercient_ExternalKey | SF_ERP_Salesforce_Clone_ORDER_LINES |
vw_GLOBALSHOP_Invoice | insert + update | — | vw_GLOBALSHOP_Account:, vw_GLOBALSHOP_Customer:, vw_GLOBALSHOP_Invoice: | Commercient_ExternalKey | SF_ERP_Salesforce_Clone_ORDER_HIST_HEAD |
vw_GLOBALSHOP_InvoiceLine | insert + update | — | vw_GLOBALSHOP_Invoice:, vw_GLOBALSHOP_Product:, vw_GLOBALSHOP_Item:, vw_GLOBALSHOP_InvoiceLine: | Commercient_ExternalKey | SF_ERP_Salesforce_Clone_ORDER_HIST_LINE |
4. Order of work
The templates set Sync_Order from 0 to 11. A run processes active rows in ascending
Sync_Order, which is the order the templates put them in:
0— Users1— Globalshop Term2— Globalshop SalesPerson3— Account4— Globalshop Customer, Contacts5— Globalshop ShipTo6— Products7— Globalshop Item8— Globalshop SalesOrder, GLOBALSHOP ItemList9— Globalshop SalesOrderLine10— Globalshop Invoice11— Globalshop InvoiceLine
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_GLOBALSHOP_Termreadsvw_GLOBALSHOP_Term:; no template in this set writesvw_GLOBALSHOP_Term:vw_GLOBALSHOP_SalesPersponreadsvw_GLOBALSHOP_SalesPerspon:; no template in this set writesvw_GLOBALSHOP_SalesPerspon:vw_GLOBALSHOP_Accountreadsvw_GLOBALSHOP_Account:; no template in this set writesvw_GLOBALSHOP_Account:vw_GLOBALSHOP_Customerreadsvw_GLOBALSHOP_Account:,vw_GLOBALSHOP_Customer:; no template in this set writesvw_GLOBALSHOP_Account:,vw_GLOBALSHOP_Customer:vw_GLOBALSHOP_Contactreadsvw_GLOBALSHOP_Account:,vw_GLOBALSHOP_Contact:; no template in this set writesvw_GLOBALSHOP_Account:,vw_GLOBALSHOP_Contact:vw_GLOBALSHOP_ShipToreadsvw_GLOBALSHOP_Account:,vw_GLOBALSHOP_Customer:,vw_GLOBALSHOP_ShipTo:; no template in this set writesvw_GLOBALSHOP_Account:,vw_GLOBALSHOP_Customer:,vw_GLOBALSHOP_ShipTo:vw_GLOBALSHOP_Productreadsvw_GLOBALSHOP_Item:,vw_GLOBALSHOP_Product:; no template in this set writesvw_GLOBALSHOP_Item:,vw_GLOBALSHOP_Product:vw_GLOBALSHOP_Itemreadsvw_GLOBALSHOP_Product:,vw_GLOBALSHOP_Item:; no template in this set writesvw_GLOBALSHOP_Product:,vw_GLOBALSHOP_Item:vw_GLOBALSHOP_SalesOrderreadsvw_GLOBALSHOP_Account:,vw_GLOBALSHOP_Customer:,vw_GLOBALSHOP_SalesOrder:; no template in this set writesvw_GLOBALSHOP_Account:,vw_GLOBALSHOP_Customer:,vw_GLOBALSHOP_SalesOrder:vw_GLOBALSHOP_ItemListreadsvw_GLOBALSHOP_Product:,vw_GLOBALSHOP_Item:,vw_GLOBALSHOP_ItemList:; no template in this set writesvw_GLOBALSHOP_Product:,vw_GLOBALSHOP_Item:,vw_GLOBALSHOP_ItemList:vw_GLOBALSHOP_SalesOrderLinereadsvw_GLOBALSHOP_SalesOrder:,vw_GLOBALSHOP_Product:,vw_GLOBALSHOP_Item:,vw_GLOBALSHOP_SalesOrderLine:; no template in this set writesvw_GLOBALSHOP_SalesOrder:,vw_GLOBALSHOP_Product:,vw_GLOBALSHOP_Item:,vw_GLOBALSHOP_SalesOrderLine:vw_GLOBALSHOP_Invoicereadsvw_GLOBALSHOP_Account:,vw_GLOBALSHOP_Customer:,vw_GLOBALSHOP_Invoice:; no template in this set writesvw_GLOBALSHOP_Account:,vw_GLOBALSHOP_Customer:,vw_GLOBALSHOP_Invoice:vw_GLOBALSHOP_InvoiceLinereadsvw_GLOBALSHOP_Invoice:,vw_GLOBALSHOP_Product:,vw_GLOBALSHOP_Item:,vw_GLOBALSHOP_InvoiceLine:; no template in this set writesvw_GLOBALSHOP_Invoice:,vw_GLOBALSHOP_Product:,vw_GLOBALSHOP_Item:,vw_GLOBALSHOP_InvoiceLine:
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 → Zoho CRM pairs |
|---|---|---|---|
| Globalshop Term | commercientglobalshop__GlobalShop_Terms | 14 | ASS_SYS, ASS_SUB_SYS, TERMS_CODE, ASS_SUB_ITEM → Commercient_ExternalKey, TERMS_CODE, ASS_SYS, ASS_SUB_SYS, ASS_SUB_ITEM → Name, TERMS_CODE → Terms_Code, TERMS_DISC_DAYS → Terms_Disc_Days, TERMS_DISC_PCT → Terms_Disc_Pct |
| Globalshop SalesPerson | commercientglobalshop__GlobalShop_Salespersons | 9 | KEY1,KEY2,SALESPERSON_CODE,FILLER → Commercient_ExternalKey, BUYER_SHIPTO → Buyer_Shipto, FILLER → Filler, FILLER3 → Filler3, SALESPERSON → Name |
| Account | Accounts | 13 | CUSTOMER → Commercient_ExternalKey, NAME_CUSTOMER → Account_Name, TELEPHONE → Phone, ADDRESS1, ADDRESS2 → Billing_Street, CITY → Billing_City |
| Globalshop Customer | commercientglobalshop__GlobalShop_Customer | 30 | CUSTOMER → Commercient_ExternalKey, NAME_CUSTOMER → Name, ADDRESS1 → Address1, ADDRESS2 → Address2, ASSGN_USR_GRP → Assign_User_Group |
| Contacts | Contacts | 11 | CUST,TYPE,ID → Commercient_ExternalKey, CUST → Account_Name, TITLE → Title, NAME_LAST,NAME,CUST,TYPE,ID → Last_Name, NAME_FIRST → First_Name |
| Globalshop ShipTo | commercientglobalshop__GlobalShop_ShipToAddress | 74 | CUSTOMER,SHIP_SEQ → Commercient_ExternalKey, CUSTOMER_NAME,SHIP_SEQ → Name, COMM_IV_INT_SHP → COMM_IV_INT_SHP, CUSTOMER → Customer, CUSTOMER_NAME → Customer_Name |
| Products | Products | 10 | PART, LOCATION → Commercient_ExternalKey__c, PART → Product_Name, PART → Product_Code, SFDCID → GlobalShop_Inventory, QTY_ONHAND → Qty_in_Stock |
| Globalshop Item | commercientglobalshop__GlobalShop_Item_Master | 78 | PART, LOCATION → Commercient_ExternalKey, PART → Name, CODE_ABC → ABC_Code, AMT_ALT_COST → Alternate_Cost_Amount, CTR_BACK_ORDER → Back_Order_Counter |
| Globalshop SalesOrder | commercientglobalshop__GlobalShop_SO_Header | 97 | ORDER_NO → Commercient_ExternalKey, ORDER_NO → Name, CUSTOMER → Account, FLAG_ALWAYS_DISCOUNT → Always_Use_Discount_Indicator, AREA → Area |
| GLOBALSHOP ItemList | commercientglobalshop__GlobalShop_Item_List | 50 | ALLOC_TYPE → Alloc_Type, ALLOCATED → Allocated, BIN → Bin, CERT_CODE → Cart_Code, CERT_DATE → CertDate |
| Globalshop SalesOrderLine | commercientglobalshop__GlobalShop_SO_Line | 100 | ORDER_NO,RECORD_NO → Commercient_ExternalKey, ORDER_NO,RECORD_NO → Name, ORDER_NO → GlobalShop_SO_Header, PART,LOCATION → Product, PART,LOCATION → GlobalShop_Item_Master |
| Globalshop Invoice | commercientglobalshop__GlobalShop_Invoice_Header | 99 | INVOICE, ORDER_NO, ORDER_SUFFIX → Commercient_ExternalKey, INVOICE, ORDER_NO, ORDER_SUFFIX → Name, CUSTOMER → Account, CUSTOMER → GlobalShop_Customer, ADDRESS1 → Address_Line_1 |
| Globalshop InvoiceLine | commercientglobalshop__GlobalShop_Invoice_Line | 70 | INVOICE, ORDER_NO, ORDER_SUFFIX, ORDER_LINE → Commercient_ExternalKey, INVOICE → GlobalShop_Invoice_Header, PART, LOCATION → Product, PART, LOCATION → GlobalShop_Item_Master, COUNTRY_SHIP → Ship_To_Country |
6. 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:
SalesRep:vw_GLOBALSHOP_Term:vw_GLOBALSHOP_SalesPerspon:vw_GLOBALSHOP_Account:vw_GLOBALSHOP_Customer:vw_GLOBALSHOP_Contact:vw_GLOBALSHOP_ShipTo:vw_GLOBALSHOP_Product:vw_GLOBALSHOP_Item:vw_GLOBALSHOP_SalesOrder:vw_GLOBALSHOP_ItemList:vw_GLOBALSHOP_SalesOrderLine:vw_GLOBALSHOP_Invoice:vw_GLOBALSHOP_InvoiceLine:
7. 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 → Zoho CRM templates set up. dlake-crmpro-zohocrm is the
destination skill this page sits under: its own text is the authority for the Zoho CRM 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.