CRMPro → Salesforce — Acumatica Cloud: what the shipped templates set up

CRMPro → Salesforce — Acumatica Cloud: 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/acumatica-cloud.md, and that skill’s ERP table is what points at it. What follows is only what the shipped Acumatica Cloud → 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, Contact, CommercientSF24__ACUMATICA_Customer__c, CommercientSF24__ACUMATICA_Employee__c	SF_ERP_Salesforce_Clone_Salesrep, SF_ERP_Salesforce_Clone_SalesPerson, SF_ERP_Salesforce_Clone_Customer, SF_ERP_Salesforce_Clone_CustomerLocation, SF_ERP_Salesforce_Clone_CustomerContact, SF_ERP_Salesforce_Clone_Contacts
AR Invoice Payments	Commercient Syncs the payment details that are held in the receivables file and held against an invoice in the ERP. The amount received from a customer, the date of payment, the method of payment, whether partial or full payment, etc New records are created and existing ones updated; none are deleted.	CommercientSF24__ACUMATICA_Payment__c, CommercientSF24__ACUMATICA_PaymentDetail__c	SF_ERP_Salesforce_Clone_Payment, SF_ERP_Salesforce_Clone_PaymentDetail
CRM Opportunity and Line	ERP SALESORDER, SALESORDERDETAIL data becomes Opportunity, OpportunityLineItem in Salesforce. New records are created and existing ones updated; none are deleted.	Opportunity, OpportunityLineItem	SF_ERP_Salesforce_Clone_SalesOrder, SF_ERP_Salesforce_Clone_SalesOrderDetail
CRM Quote and Line	ERP SALESORDER, SALESORDERDETAIL data becomes Quote, QuoteLineItem in Salesforce. New records are created and existing ones updated; none are deleted.	Quote, QuoteLineItem	SF_ERP_Salesforce_Clone_SalesOrder, SF_ERP_Salesforce_Clone_SalesOrderDetail
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 and existing ones updated; none are deleted.	CommercientSF24__ACUMATICA_Contact__c	SF_ERP_Salesforce_Clone_Contacts, SF_ERP_Salesforce_Clone_CustomerContact
Product	ERP STOCKITEM data becomes CommercientSF24__StockItem__c, Product2 in Salesforce. New records are created and existing ones updated; none are deleted.	CommercientSF24__StockItem__c, Product2	SF_ERP_Salesforce_Clone_StockItem
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 and existing ones updated; none are deleted.	CommercientSF24__ACUMATICA_SalesInvoice__c, CommercientSF24__ACUMATICA_SalesInvoiceDetail__c	SF_ERP_Salesforce_Clone_SalesInvoice, SF_ERP_Salesforce_Clone_SalesInvoiceDetail
Pricebook	ERP STOCKITEM data becomes PricebookEntry in Salesforce. New records are created and existing ones updated; none are deleted.	PricebookEntry	SF_ERP_Salesforce_Clone_StockItem
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 and existing ones updated; none are deleted.	CommercientSF24__ACUMATICA_SalesOrder__c, CommercientSF24__ACUMATICA_SalesOrderDetails__c	SF_ERP_Salesforce_Clone_SalesOrder, SF_ERP_Salesforce_Clone_SalesOrderDetail

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	1	vw_ACUMATICACLOUD_Account	vw_ACUMATICACLOUD_Account	'' / ''	1
Acumatica SalesPerson	CommercientSF24__ACUMATICA_Employee__c	CommercientSF24__ExternalKey__c	1	vw_ACUMATICACLOUD_Salesperson	vw_ACUMATICACLOUD_Salesperson	CommercientSF24__ / __c	1
ACUMATICACLOUD Customer	CommercientSF24__ACUMATICA_Customer__c	CommercientSF24__ExternalKey__c	2	vw_ACUMATICACLOUD_Customer	vw_ACUMATICACLOUD_Customer	CommercientSF24__ / __c	1
ACUMATICACLOUD Address	CommercientSF24__ACUMATICA_Contact__c	CommercientSF24__ExternalKey__c	3	vw_ACUMATICACLOUD_Address	vw_ACUMATICACLOUD_Address	CommercientSF24__ / __c	1
Product	Product2	CommercientSF__ExternalKey__c	4	vw_ACUMATICACLOUD_Product	vw_ACUMATICACLOUD_Product	'' / ''	1
ACUMATICACLOUD Item Master	CommercientSF24__StockItem__c	CommercientSF24__ExternalKey__c	5	vw_ACUMATICACLOUD_LineItem	vw_ACUMATICACLOUD_LineItem	CommercientSF24__ / __c	1
ACUMATICACLOUD SalesOrder	CommercientSF24__ACUMATICA_SalesOrder__c	CommercientSF24__ExternalKey__c	6	vw_ACUMATICACLOUD_SalesOrderHeader	vw_ACUMATICACLOUD_SalesOrderHeader	CommercientSF24__ / __c	1
ACUMATICACLOUD SalesOrderDetail	CommercientSF24__ACUMATICA_SalesOrderDetails__c	CommercientSF24__ExternalKey__c	7	vw_ACUMATICACLOUD_SalesOrderDetail	vw_ACUMATICACLOUD_SalesOrderDetail	CommercientSF24__ / __c	1
ACUMATICACLOUD InvoiceHeader	CommercientSF24__ACUMATICA_SalesInvoice__c	CommercientSF24__ExternalKey__c	8	vw_ACUMATICACLOUD_InvoiceHeader	vw_ACUMATICACLOUD_InvoiceHeader	CommercientSF24__ / __c	1
ACUMATICACLOUD InvoiceDetail	CommercientSF24__ACUMATICA_SalesInvoiceDetail__c	CommercientSF24__ExternalKey__c	9	vw_ACUMATICACLOUD_InvoiceDetail	vw_ACUMATICACLOUD_InvoiceDetail	CommercientSF24__ / __c	1
ACUMATICACLOUD Payment	CommercientSF24__ACUMATICA_Payment__c	CommercientSF24__ExternalKey__c	10	vw_ACUMATICACLOUD_Payment	vw_ACUMATICACLOUD_Payment	CommercientSF24__ / __c	1
ACUMATICACLOUD PaymentDetail	CommercientSF24__ACUMATICA_PaymentDetail__c	CommercientSF24__ExternalKey__c	11	vw_ACUMATICACLOUD_PaymentDetail	vw_ACUMATICACLOUD_PaymentDetail	CommercientSF24__ / __c	1
Create Standard PriceBook	PricebookEntry	ExternalKey__c	12	vw_ProductPriceBook	vw_ACUMATICACLOUD_StandardPriceBook	'' / ''	1
Update Standard Pricebook	PricebookEntry	ExternalKey__c	13	vw_ProductPriceBook	vw_ACUMATICACLOUD_StandardPriceBookUpdate	'' / ''	1
Opportunity	Opportunity	ExternalKey__c	14	vw_ACUMATICACLOUD_Opportunity	vw_ACUMATICACLOUD_Opportunity	'' / ''	1
Contact	Contact	Commercient_ExternalKey__c	15	vw_ACUMATICACLOUD_Contact	vw_ACUMATICACLOUD_Contact	'' / ''	1
OpportunityLineitem	OpportunityLineItem	ExternalKey__c	15	vw_ACUMATICACLOUD_OpportunityLineItem	vw_ACUMATICACLOUD_OpportunityLineItem	'' / ''	1
Get User	User	Id	17	vw_ACUMATICACLOUD_User	SELECT 1=0	'' / ''	1
Quote	Quote	ExternalKey__c	22	vwSFQuote	vw_ACUMATICACLOUD_Quote	'' / ''	1
Quote Line	QuoteLineItem	ExternalKey__c	23	vwSFQuoteLine	vw_ACUMATICACLOUD_QuoteLineItem	'' / ''	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, 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, OpportunityLineitem — 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_ACUMATICACLOUD_Account	insert + update	vw_ACUMATICACLOUD_Account:	vw_ACUMATICACLOUD_Salesperson:, vw_ACUMATICACLOUD_User:	—	SF_ERP_Salesforce_Clone_Salesrep, SF_ERP_Salesforce_Clone_SalesPerson, SF_ERP_Salesforce_Clone_Customer, SF_ERP_Salesforce_Clone_CustomerLocation, SF_ERP_Salesforce_Clone_CustomerContact
vw_ACUMATICACLOUD_Salesperson	insert + update	vw_ACUMATICACLOUD_Salesperson:	—	Externalkey	SF_ERP_Salesforce_Clone_Salesrep, SF_ERP_Salesforce_Clone_SalesPerson
vw_ACUMATICACLOUD_Customer	insert + update	vw_ACUMATICACLOUD_Customer:	vw_ACUMATICACLOUD_Account:	ExternalKey	SF_ERP_Salesforce_Clone_Customer
vw_ACUMATICACLOUD_Address	insert + update	vw_ACUMATICACLOUD_Address:	vw_ACUMATICACLOUD_Account:, vw_ACUMATICACLOUD_Customer:	ExternalKey	SF_ERP_Salesforce_Clone_Contacts, SF_ERP_Salesforce_Clone_CustomerContact
vw_ACUMATICACLOUD_Product	insert + update	vw_ACUMATICACLOUD_Product:	—	CommercientSF__ExternalKey__c	SF_ERP_Salesforce_Clone_StockItem
vw_ACUMATICACLOUD_LineItem	insert + update	vw_ACUMATICACLOUD_LineItem:	vw_ACUMATICACLOUD_Product:	ExternalKey	SF_ERP_Salesforce_Clone_StockItem
vw_ACUMATICACLOUD_SalesOrderHeader	insert + update	vw_ACUMATICACLOUD_SalesOrderHeader:	vw_ACUMATICACLOUD_Account:, vw_ACUMATICACLOUD_Customer:	ExternalKey	SF_ERP_Salesforce_Clone_SalesOrder
vw_ACUMATICACLOUD_SalesOrderDetail	insert + update	vw_ACUMATICACLOUD_SalesOrderDetail:	vw_ACUMATICACLOUD_SalesOrderHeader:, vw_ACUMATICACLOUD_LineItem:	ExternalKey	SF_ERP_Salesforce_Clone_SalesOrderDetail
vw_ACUMATICACLOUD_InvoiceHeader	insert + update	vw_ACUMATICACLOUD_InvoiceHeader:	vw_ACUMATICACLOUD_Account:, vw_ACUMATICACLOUD_Customer:	ExternalKey	SF_ERP_Salesforce_Clone_SalesInvoice
vw_ACUMATICACLOUD_InvoiceDetail	insert + update	vw_ACUMATICACLOUD_InvoiceDetail:	vw_ACUMATICACLOUD_InvoiceHeader:, vw_ACUMATICACLOUD_LineItem:	ExternalKey	SF_ERP_Salesforce_Clone_SalesInvoiceDetail
vw_ACUMATICACLOUD_Payment	insert + update	vw_ACUMATICACLOUD_Payment:	vw_ACUMATICACLOUD_Account:, vw_ACUMATICACLOUD_Customer:	ExternalKey	SF_ERP_Salesforce_Clone_Payment
vw_ACUMATICACLOUD_PaymentDetail	insert + update	vw_ACUMATICACLOUD_PaymentDetail:	vw_ACUMATICACLOUD_Payment:	ExternalKey	SF_ERP_Salesforce_Clone_PaymentDetail
vw_ACUMATICACLOUD_StandardPriceBook	insert + update	—	vw_ACUMATICACLOUD_Product:, StandardPriceBook:	—	SF_ERP_Salesforce_Clone_StockItem
vw_ACUMATICACLOUD_StandardPriceBookUpdate	insert + update	—	vw_ACUMATICACLOUD_Product:, StandardPriceBook:	—	SF_ERP_Salesforce_Clone_StockItem
vw_ACUMATICACLOUD_Opportunity	insert-only	vw_ACUMATICACLOUD_Opportunity:	vw_ACUMATICACLOUD_Account:	ExternalKey__c	SF_ERP_Salesforce_Clone_SalesOrder
vw_ACUMATICACLOUD_Contact	insert + update	vw_ACUMATICACLOUD_Contact:	vw_ACUMATICACLOUD_Account:	Commercient_ExternalKey__c	SF_ERP_Salesforce_Clone_Contacts, SF_ERP_Salesforce_Clone_CustomerContact, SF_ERP_Salesforce_Clone_Salesrep
vw_ACUMATICACLOUD_OpportunityLineItem	insert + update	vw_ACUMATICACLOUD_OpportunityLineItem:	vw_ACUMATICACLOUD_Product:, vw_ACUMATICACLOUD_Opportunity:	ExternalKey__c	SF_ERP_Salesforce_Clone_SalesOrderDetail
vw_ACUMATICACLOUD_Quote	insert + update	vwSFQuote:	vw_ACUMATICACLOUD_Account:, vw_ACUMATICACLOUD_Opportunity:	ExternalKey	SF_ERP_Salesforce_Clone_SalesOrder
vw_ACUMATICACLOUD_QuoteLineItem	insert + update	vwSFQuoteLine:	vwSFQuote:, vw_ACUMATICACLOUD_Product:	ExternalKey__c	SF_ERP_Salesforce_Clone_SalesOrderDetail

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

• 1 — Account, Acumatica SalesPerson
• 2 — ACUMATICACLOUD Customer
• 3 — ACUMATICACLOUD Address
• 4 — Product
• 5 — ACUMATICACLOUD Item Master
• 6 — ACUMATICACLOUD SalesOrder
• 7 — ACUMATICACLOUD SalesOrderDetail
• 8 — ACUMATICACLOUD InvoiceHeader
• 9 — ACUMATICACLOUD InvoiceDetail
• 10 — ACUMATICACLOUD Payment
• 11 — ACUMATICACLOUD PaymentDetail
• 12 — Create Standard PriceBook
• 13 — Update Standard Pricebook
• 14 — Opportunity
• 15 — Contact, OpportunityLineitem
• 17 — Get User
• 22 — Quote
• 23 — Quote Line

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_ACUMATICACLOUD_Account reads vw_ACUMATICACLOUD_Salesperson:, vw_ACUMATICACLOUD_User:
• vw_ACUMATICACLOUD_Payment reads vw_ACUMATICACLOUD_Account:, vw_ACUMATICACLOUD_Customer:
• vw_ACUMATICACLOUD_PaymentDetail reads vw_ACUMATICACLOUD_Payment:
• vw_ACUMATICACLOUD_Contact reads vw_ACUMATICACLOUD_Account:
• vw_ACUMATICACLOUD_Opportunity reads vw_ACUMATICACLOUD_Account:
• vw_ACUMATICACLOUD_OpportunityLineItem reads vw_ACUMATICACLOUD_Product:, vw_ACUMATICACLOUD_Opportunity:
• vw_ACUMATICACLOUD_Quote reads vw_ACUMATICACLOUD_Account:, vw_ACUMATICACLOUD_Opportunity:
• vw_ACUMATICACLOUD_QuoteLineItem reads vwSFQuote:, vw_ACUMATICACLOUD_Product:
• vw_ACUMATICACLOUD_Customer reads vw_ACUMATICACLOUD_Account:
• vw_ACUMATICACLOUD_Address reads vw_ACUMATICACLOUD_Account:, vw_ACUMATICACLOUD_Customer:
• vw_ACUMATICACLOUD_LineItem reads vw_ACUMATICACLOUD_Product:
• vw_ACUMATICACLOUD_InvoiceHeader reads vw_ACUMATICACLOUD_Account:, vw_ACUMATICACLOUD_Customer:
• vw_ACUMATICACLOUD_InvoiceDetail reads vw_ACUMATICACLOUD_InvoiceHeader:, vw_ACUMATICACLOUD_LineItem:
• vw_ACUMATICACLOUD_StandardPriceBook reads vw_ACUMATICACLOUD_Product:, StandardPriceBook:; no template in this set writes StandardPriceBook:
• vw_ACUMATICACLOUD_StandardPriceBookUpdate reads vw_ACUMATICACLOUD_Product:, StandardPriceBook:; no template in this set writes StandardPriceBook:
• vw_ACUMATICACLOUD_SalesOrderHeader reads vw_ACUMATICACLOUD_Account:, vw_ACUMATICACLOUD_Customer:
• vw_ACUMATICACLOUD_SalesOrderDetail reads vw_ACUMATICACLOUD_SalesOrderHeader:, vw_ACUMATICACLOUD_LineItem:

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	24	CustomerID → CommercientSF__Commercient_ArCustomerCode__c, CustomerName → Name, CustomerID → ERP_UID__c, DisplayName → DBA_Name__c, Email → Account_Emails__c
Acumatica SalesPerson	CommercientSF24__ACUMATICA_Employee__c	5	Commission → commission__c, EmployeeID → CommercientSF24__employeeid__c, LocationID → locationid__c, IsActive → isactive__c, LocationName → locationname__c
ACUMATICACLOUD Customer	CommercientSF24__ACUMATICA_Customer__c	49	CustomerID → CommercientSF24__ExternalKey__c, CustomerName → Name, AccountRef → AccountRef, ApplyOverdueCharges → ApplyOverdueCharges, AutoApplyPayments → AutoApplyPayments
ACUMATICACLOUD Address	CommercientSF24__ACUMATICA_Contact__c	67	ContactID, Type → CommercientSF24__ExternalKey__c, CustomerID → Account, CustomerID → ACUMATICA_Customer, DisplayName, ContactID, Type → Name, Active → Active__c
Product	Product2	6	InventoryID → CommercientSF__ExternalKey__c, Description → Name, InventoryID → ProductCode, Description → Description, ItemStatus → IsActive
ACUMATICACLOUD Item Master	CommercientSF24__StockItem__c	74	InventoryID → CommercientSF24__ExternalKey__c, SFDCID → CommercientSF24__Product__c, InventoryID → CommercientSF24__Name__c, ABCCode → CommercientSF24__ABCCode__c, AutoIncrementalValue → CommercientSF24__AutoIncrementalValue__c
ACUMATICACLOUD SalesOrder	CommercientSF24__ACUMATICA_SalesOrder__c	64	OrderNbr → CommercientSF24__ExternalKey__c, CustomerID → Account, CustomerID → ACUMATICA_Customer, OrderNbr → Name, Approved → Approved__c
ACUMATICACLOUD SalesOrderDetail	CommercientSF24__ACUMATICA_SalesOrderDetails__c	46	OrderNbr, lineNbr → CommercientSF24__ExternalKey__c, SFDCID → CommercientSF24__ACUMATICA_Sales_Order__c, SFDCID → CommercientSF24__ACUMATICA_Item_Master__c, OrderNbr → OrderNbr, account → account
ACUMATICACLOUD InvoiceHeader	CommercientSF24__ACUMATICA_SalesInvoice__c	17	ReferenceNbr → CommercientSF24__ExternalKey__c, CustomerID → CommercientSF24__AccountID__c, CustomerID → CommercientSF24__ACUMATICA_Customer__c, ReferenceNbr → Name, Amount → Amount
ACUMATICACLOUD InvoiceDetail	CommercientSF24__ACUMATICA_SalesInvoiceDetail__c	16	SalesInvoiceNumber,LineNbr → CommercientSF24__ExternalKey__c, SalesInvoiceNumber,LineNbr → CommercientSF24__Name__c, SFDCID → CommercientSF24__ACUMATICA_Sales_Invoice__c, SFDCID → CommercientSF24__ACUMATICA_Item_Master__c, ReferenceNbr → CommercientSF24__ReferenceNbr__c
ACUMATICACLOUD Payment	CommercientSF24__ACUMATICA_Payment__c	21	ReferenceNbr → CommercientSF24__ExternalKey__c, CustomerID → Account__c, CustomerID → ACUMATICA_Customer__c, ReferenceNbr → Name, ApplicationDate → ApplicationDate
ACUMATICACLOUD PaymentDetail	CommercientSF24__ACUMATICA_PaymentDetail__c	10	paymentHeaderRefNumber,referenceNbr → CommercientSF24__ExternalKey__c, SFDCID → ACUMATICA_Payment__c, paymentHeaderRefNumber,referenceNbr → Name, amountPaid → AmountPaid, balanceWriteOff → BalanceWriteOff
Create Standard PriceBook	PricebookEntry	5	InventoryID → ExternalKey__c, Pricebook2Id → Pricebook2Id, SFDCID → Product2Id, IsActive → IsActive, CurrentStdCost → UnitPrice
Update Standard Pricebook	PricebookEntry	3	InventoryID → ExternalKey__c, IsActive → IsActive, CurrentStdCost → UnitPrice
Opportunity	Opportunity	8	OrderNbr → ExternalKey__c, CustomerID → AccountID, Description → Name, EffectiveDate → CloseDate, FOBPoint → FOB__c
Contact	Contact	20	Commercient_ExternalKey → Commercient_ExternalKey__c, AccountID → AccountID, LastName → LastName, FirstName → FirstName, Suffix → Suffix
OpportunityLineitem	OpportunityLineItem	5	OrderNbr, lineNbr, lineType → ExternalKey__c, SFDCID → PricebookEntryId, SFDCID → OpportunityId, unitPrice → UnitPrice, orderQty → Quantity
Quote	Quote	17	OrderNbr → ExternalKey__c, OrderNbr → Name, SFDCID → OpportunityID, SFDCID → AccountId, SFDCID → Pricebook2Id
Quote Line	QuoteLineItem	6	OrderNbr, lineNbr, lineType → ExternalKey__c, inventoryID → Product2ID, PricebookEntryId → PricebookEntryId, OrderNbr → QuoteID, orderQty → Quantity

6. Community templates

The catalogue carries 170 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: 170
• Default operations: insert on 170, update on 170, delete on 170
• Marked circular-sync: 0
• Licence groups they span: 12
• Destination objects: Account, Product2, PricebookEntry, CommercientSF24__ACUMATICA_Customer__c, CommercientSF24__ACUMATICA_SalesInvoice__c, CommercientSF24__ACUMATICA_SalesInvoiceDetail__c, CommercientSF24__ACUMATICA_SalesOrder__c, CommercientSF24__ACUMATICA_SalesOrderDetails__c, CommercientSF24__StockItem__c, CommercientSF24__ACUMATICA_Contact__c, CommercientSF24__ACUMATICA_Employee__c, Contact, ACUMATICA_ItemWarehouse__c, CommercientSF24__ACCOUNTMATCHING__c, Quote, CommercientSF24__ACUMATICA_PaymentDetail__c, CommercientSF24__CONTACTMATCHING__c, Opportunity, ACUMATICA_CustomerCreditCard__c, CommercientSF24__ACUMATICA_Payment__c and 16 more
• Object display names: Account, ACUMATICACLOUD InvoiceDetail, ACUMATICACLOUD InvoiceHeader, ACUMATICACLOUD Customer, ACUMATICACLOUD Item Master, Product, ACUMATICACLOUD SalesOrder, ACUMATICACLOUD SalesOrderDetail, Update Standard Pricebook, ACUMATICACLOUD Address, Create Standard PriceBook, SYNC ITEMTOPRODUCTLOOKUP, 48 more and 2 further templates
• Template groups: Account, Product, Invoice, Salesorder, CRM Quote and Line, Customer Multi Ship Addresses, 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_ACUMATICACLOUD_User
• vw_ACUMATICACLOUD_Account
• vw_ACUMATICACLOUD_Payment
• vw_ACUMATICACLOUD_PaymentDetail
• vw_ACUMATICACLOUD_Contact
• vw_ACUMATICACLOUD_Opportunity
• vw_ACUMATICACLOUD_OpportunityLineItem
• vwSFQuote
• vwSFQuoteLine
• vw_ACUMATICACLOUD_Customer
• vw_ACUMATICACLOUD_Address
• vw_ACUMATICACLOUD_LineItem
• vw_ACUMATICACLOUD_InvoiceHeader
• vw_ACUMATICACLOUD_InvoiceDetail
• vw_ProductPriceBook
• vw_ACUMATICACLOUD_Product
• vw_ACUMATICACLOUD_SalesOrderHeader
• vw_ACUMATICACLOUD_SalesOrderDetail
• vw_ACUMATICACLOUD_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 Acumatica Cloud → 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.