CRMPro → Zoho CRM — Acumatica: what the shipped templates set up

CRMPro → Zoho CRM — Acumatica: 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-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/acumatica.md, and that skill’s ERP table is what points at it. What follows is only what the shipped Acumatica → 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	—
Accounts	The templates push Accounts to Zoho CRM. New records are created and existing ones updated; none are deleted.	Accounts	SF_ERP_Salesforce_Clone_SalesInvoice, SF_ERP_Salesforce_Clone_Customer, SF_ERP_Salesforce_Clone_BillingContact, SF_ERP_Salesforce_Clone_Salesrep, SF_ERP_Salesforce_Clone_CustomerBillingAddress, SF_ERP_Salesforce_Clone_CustomerShippingAddress
Contacts	The templates push Contacts to Zoho CRM. New records are created and existing ones updated; none are deleted.	Contacts	SF_ERP_Salesforce_Clone_Contacts, SF_ERP_Salesforce_Clone_CustomerMainAddress
ACUMATICA Customer	The templates push commercientacumatica__Acumatica_Customer to Zoho CRM. New records are created and existing ones updated; none are deleted.	commercientacumatica__Acumatica_Customer	SF_ERP_Salesforce_Clone_Customer
ACUMATICA Opportunity	The templates push ACUMATICA_Opportunity to Zoho CRM. New records are created and existing ones updated; none are deleted.	ACUMATICA_Opportunity	SF_ERP_Salesforce_Clone_Opportunity, SF_ERP_Salesforce_Clone_Salesrep
ACUMATICA Contacts	The templates push commercientacumatica__Acumatica_CustomerContact to Zoho CRM. New records are created and existing ones updated; none are deleted.	commercientacumatica__Acumatica_CustomerContact	SF_ERP_Salesforce_Clone_Contacts, SF_ERP_Salesforce_Clone_CustomerMainAddress
ACUMATICA SalesOrder	The templates push commercientacumatica__Acumatica_SOHeader to Zoho CRM. New records are created and existing ones updated; none are deleted.	commercientacumatica__Acumatica_SOHeader	SF_ERP_Salesforce_Clone_SalesOrder
ACUMATICA SalesOrderLine	The templates push commercientacumatica__Acumatica_SODetail to Zoho CRM. New records are created and existing ones updated; none are deleted.	commercientacumatica__Acumatica_SODetail	SF_ERP_Salesforce_Clone_SalesOrderDetail
ACUMATICA Invoice	The templates push commercientacumatica__Acumatica_InvoiceHeader to Zoho CRM. New records are created and existing ones updated; none are deleted.	commercientacumatica__Acumatica_InvoiceHeader	SF_ERP_Salesforce_Clone_SalesInvoice
ACUMATICA InvoiceLine	The templates push commercientacumatica__Acumatica_InvoiceDetail to Zoho CRM. New records are created and existing ones updated; none are deleted.	commercientacumatica__Acumatica_InvoiceDetail	SF_ERP_Salesforce_Clone_SalesInvoiceDetail

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	'' / ''
Accounts	Accounts	Commercient_ArCustomer_Code	1	vw_ACUMATICA_Account	vw_ACUMATICA_Account	'' / ''
Contacts	Contacts	Commercient_ExternalKey	3	vw_ACUMATICA_Contact:	vw_ACUMATICA_Contact	'' / ''
ACUMATICA Customer	commercientacumatica__Acumatica_Customer	Commercient_ExternalKey	4	vw_ACUMATICA_Customer:	vw_ACUMATICA_Customer	commercientacumatica__ / ''
ACUMATICA Opportunity	ACUMATICA_Opportunity	Commercient_ExternalKey	5	vw_ACUMATICA_Opportunity:	vw_ACUMATICA_Opportunity	'' / __c
ACUMATICA Contacts	commercientacumatica__Acumatica_CustomerContact	Commercient_ExternalKey	6	vw_ACUMATICA_TAB_Contact:	vw_ACUMATICA_TAB_Contact	commercientacumatica__ / __c
ACUMATICA SalesOrder	commercientacumatica__Acumatica_SOHeader	Commercient_ExternalKey	7	vw_ACUMATICA_SalesOrder:	vw_ACUMATICA_SalesOrder	commercientacumatica__ / __c
ACUMATICA SalesOrderLine	commercientacumatica__Acumatica_SODetail	Commercient_ExternalKey	8	vw_ACUMATICA_SalesOrderLine:	vw_ACUMATICA_SalesOrderLine	commercientacumatica__ / __c
ACUMATICA Invoice	commercientacumatica__Acumatica_InvoiceHeader	Commercient_ExternalKey	9	vw_ACUMATICA_Invoice:	vw_ACUMATICA_Invoice	commercientacumatica__ / __c
ACUMATICA InvoiceLine	commercientacumatica__Acumatica_InvoiceDetail	Commercient_ExternalKey	10	vw_ACUMATICA_InvoiceLine:	vw_ACUMATICA_InvoiceLine	commercientacumatica__ / __c

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 Accounts, Contacts — 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_ACUMATICA_Account	insert + update	vw_ACUMATICA_Account:	SalesRep:	Commercient_ArCustomer_Code	SF_ERP_Salesforce_Clone_SalesInvoice, SF_ERP_Salesforce_Clone_Customer, SF_ERP_Salesforce_Clone_BillingContact, SF_ERP_Salesforce_Clone_Salesrep, SF_ERP_Salesforce_Clone_CustomerBillingAddress
vw_ACUMATICA_Contact	insert-only	—	vw_ACUMATICA_Account:, vw_ACUMATICA_Contact:	Commercient_ExternalKey	SF_ERP_Salesforce_Clone_Contacts, SF_ERP_Salesforce_Clone_CustomerMainAddress
vw_ACUMATICA_Customer	insert-only	—	vw_ACUMATICA_Account:, vw_ACUMATICA_Customer:	Commercient_ExternalKey__c, Commercient_ExternalKey	SF_ERP_Salesforce_Clone_Customer
vw_ACUMATICA_Opportunity	insert-only	—	vw_ACUMATICA_Account:, vw_ACUMATICA_Customer:, SalesRep:, vw_ACUMATICA_Opportunity:	Commercient_ExternalKey	SF_ERP_Salesforce_Clone_Opportunity, SF_ERP_Salesforce_Clone_Salesrep
vw_ACUMATICA_TAB_Contact	insert-only	—	vw_ACUMATICA_Account:, vw_ACUMATICA_Customer:, vw_ACUMATICA_TAB_Contact:	—	SF_ERP_Salesforce_Clone_Contacts, SF_ERP_Salesforce_Clone_CustomerMainAddress
vw_ACUMATICA_SalesOrder	insert-only	—	vw_ACUMATICA_Account:, vw_ACUMATICA_Customer:, vw_ACUMATICA_SalesOrder:	Commercient_ExternalKey__c, Commercient_ExternalKey	SF_ERP_Salesforce_Clone_SalesOrder
vw_ACUMATICA_SalesOrderLine	insert-only	—	vw_ACUMATICA_SalesOrder:, vw_ACUMATICA_SalesOrderLine:	Commercient_ExternalKey__c, Commercient_ExternalKey	SF_ERP_Salesforce_Clone_SalesOrderDetail
vw_ACUMATICA_Invoice	insert-only	—	vw_ACUMATICA_Account:, vw_ACUMATICA_Customer:, vw_ACUMATICA_Invoice:	—	SF_ERP_Salesforce_Clone_SalesInvoice
vw_ACUMATICA_InvoiceLine	insert-only	—	vw_ACUMATICA_Invoice:, vw_ACUMATICA_InvoiceLine:	—	SF_ERP_Salesforce_Clone_SalesInvoiceDetail

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

• 0 — Users
• 1 — Accounts
• 3 — Contacts
• 4 — ACUMATICA Customer
• 5 — ACUMATICA Opportunity
• 6 — ACUMATICA Contacts
• 7 — ACUMATICA SalesOrder
• 8 — ACUMATICA SalesOrderLine
• 9 — ACUMATICA Invoice
• 10 — ACUMATICA InvoiceLine

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_ACUMATICA_Account reads SalesRep:; no template in this set writes SalesRep:
• vw_ACUMATICA_Contact reads vw_ACUMATICA_Account:, vw_ACUMATICA_Contact:; no template in this set writes vw_ACUMATICA_Contact:
• vw_ACUMATICA_Customer reads vw_ACUMATICA_Account:, vw_ACUMATICA_Customer:; no template in this set writes vw_ACUMATICA_Customer:
• vw_ACUMATICA_Opportunity reads vw_ACUMATICA_Account:, vw_ACUMATICA_Customer:, SalesRep:, vw_ACUMATICA_Opportunity:; no template in this set writes vw_ACUMATICA_Customer:, SalesRep:, vw_ACUMATICA_Opportunity:
• vw_ACUMATICA_TAB_Contact reads vw_ACUMATICA_Account:, vw_ACUMATICA_Customer:, vw_ACUMATICA_TAB_Contact:; no template in this set writes vw_ACUMATICA_Customer:, vw_ACUMATICA_TAB_Contact:
• vw_ACUMATICA_SalesOrder reads vw_ACUMATICA_Account:, vw_ACUMATICA_Customer:, vw_ACUMATICA_SalesOrder:; no template in this set writes vw_ACUMATICA_Customer:, vw_ACUMATICA_SalesOrder:
• vw_ACUMATICA_SalesOrderLine reads vw_ACUMATICA_SalesOrder:, vw_ACUMATICA_SalesOrderLine:; no template in this set writes vw_ACUMATICA_SalesOrder:, vw_ACUMATICA_SalesOrderLine:
• vw_ACUMATICA_Invoice reads vw_ACUMATICA_Account:, vw_ACUMATICA_Customer:, vw_ACUMATICA_Invoice:; no template in this set writes vw_ACUMATICA_Customer:, vw_ACUMATICA_Invoice:
• vw_ACUMATICA_InvoiceLine reads vw_ACUMATICA_Invoice:, vw_ACUMATICA_InvoiceLine:; no template in this set writes vw_ACUMATICA_Invoice:, vw_ACUMATICA_InvoiceLine:

5. 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_ACUMATICA_Account
• vw_ACUMATICA_Contact:
• vw_ACUMATICA_Customer:
• vw_ACUMATICA_Opportunity:
• vw_ACUMATICA_TAB_Contact:
• vw_ACUMATICA_SalesOrder:
• vw_ACUMATICA_SalesOrderLine:
• vw_ACUMATICA_Invoice:
• vw_ACUMATICA_InvoiceLine:

6. 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 Acumatica → 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.