CRMPro → Salesforce — Macola 10: what the shipped templates set up

CRMPro → Salesforce — Macola 10: 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/macola-10.md, and that skill’s ERP table is what points at it. What follows is only what the shipped Macola 10 → 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
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, CommercientSF19_MACOLA10_Customer__c	SF_ERP_Salesforce_Clone_CICMPY, SF_ERP_Salesforce_Clone_Addresses
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_MACOLA10_Address__c	SF_ERP_Salesforce_Clone_Addresses, SF_ERP_Salesforce_Clone_CICMPY
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_MACOLA10_SO_HEADER__c, CommercientSF19_MACOLA10_SO_DETAIL__c, CommercientSF19_MACOLA10_SO_HST_HEADER__c, CommercientSF19_MACOLA10_SO_HST_DETAIL__c	SF_ERP_Salesforce_Clone_oeordhdr_sql, SF_ERP_Salesforce_Clone_CICMPY, CommercientFlags, SF_ERP_Salesforce_Clone_Addresses, SF_ERP_Salesforce_Clone_oeordlin_sql, SF_ERP_Salesforce_Clone_oehdrhst_sql

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_MACOLA10_Account	vw_MACOLA10_Account	'' / ''	1
MACOLA10_Customer	CommercientSF19_MACOLA10_Customer__c	ExternalKey__c	2	vw_MACOLA10_Customer	vw_MACOLA10_Customer	'' / __c	1
MACOLA10_Address	CommercientSF19_MACOLA10_Address__c	ExternalKey__c	3	vw_MACOLA10_Addresses	vw_MACOLA10_Addresses	'' / __c	1
CustomerToAccountLookup	Account	CommercientSF__Commercient_ArCustomerCode__c	4	vw_MACOLA10_CustomerToAccountLookup	vw_MACOLA10_CustomerToAccountLookup	'' / ''	1
MACOLA10_SalesOrderHeader	CommercientSF19_MACOLA10_SO_HEADER__c	ExternalKey__c	12	vw_MACOLA10_SalesOrderHeader	vw_MACOLA10_SalesOrderHeader	'' / __c	1
MACOLA10_SalesOrderDetail	CommercientSF19_MACOLA10_SO_DETAIL__c	ExternalKey__c	13	vw_MACOLA10_SalesOrderDetail	vw_MACOLA10_SalesOrderDetail	'' / __c	1
MACOLA10_SalesOrderHistoryHeader	CommercientSF19_MACOLA10_SO_HST_HEADER__c	ExternalKey__c	15	vw_MACOLA10_SalesOrderHistoryHeader	vw_MACOLA10_SalesOrderHistoryHeader	'' / __c	1
MACOLA10_SalesOrderHistoryDetail	CommercientSF19_MACOLA10_SO_HST_DETAIL__c	ExternalKey__c	16	vw_MACOLA10_SalesOrderHistoryDetail	vw_MACOLA10_SalesOrderHistoryDetail	'' / __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.

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_MACOLA10_Account	insert + update	vw_MACOLA10_Account:	—	—	SF_ERP_Salesforce_Clone_CICMPY, SF_ERP_Salesforce_Clone_Addresses
vw_MACOLA10_Customer	insert + update	vw_MACOLA10_Customer:	vw_MACOLA10_Account:	ExternalKey__c	SF_ERP_Salesforce_Clone_CICMPY, SF_ERP_Salesforce_Clone_Addresses
vw_MACOLA10_Addresses	insert-only	vw_MACOLA10_Addresses:	vw_MACOLA10_Account:, vw_MACOLA10_Customer:	ExternalKey__c	SF_ERP_Salesforce_Clone_Addresses, SF_ERP_Salesforce_Clone_CICMPY
vw_MACOLA10_CustomerToAccountLookup	insert + update	vw_MACOLA10_CustomerToAccountLookup:	vw_MACOLA10_Customer:	—	SF_ERP_Salesforce_Clone_CICMPY
vw_MACOLA10_SalesOrderHeader	insert + update	vw_MACOLA10_SalesOrderHeader:	vw_MACOLA10_Account:, vw_MACOLA10_Customer:, vw_MACOLA10_Addresses:	ExternalKey__c	SF_ERP_Salesforce_Clone_oeordhdr_sql, SF_ERP_Salesforce_Clone_CICMPY, CommercientFlags, SF_ERP_Salesforce_Clone_Addresses
vw_MACOLA10_SalesOrderDetail	insert + update	vw_MACOLA10_SalesOrderDetail:	vw_MACOLA10_SalesOrderHeader:	ExternalKey__c	SF_ERP_Salesforce_Clone_oeordlin_sql, SF_ERP_Salesforce_Clone_oeordhdr_sql
vw_MACOLA10_SalesOrderHistoryHeader	insert + update	vw_MACOLA10_SalesOrderHistoryHeader:	vw_MACOLA10_Account:, vw_MACOLA10_Customer:, vw_MACOLA10_Addresses:	ExternalKey__c	SF_ERP_Salesforce_Clone_oehdrhst_sql, SF_ERP_Salesforce_Clone_CICMPY, CommercientFlags, SF_ERP_Salesforce_Clone_Addresses
vw_MACOLA10_SalesOrderHistoryDetail	insert + update	vw_MACOLA10_SalesOrderHistoryDetail:	vw_MACOLA10_SalesOrderHistoryHeader:	—	SF_ERP_Salesforce_Clone_oelinhst_sql, SF_ERP_Salesforce_Clone_oehdrhst_sql

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 to 1, 2, 3, 4, 12, 13, 15, 16. A run processes active rows in ascending Sync_Order, which is the order the templates put them in:

• 1 — Account
• 2 — MACOLA10_Customer
• 3 — MACOLA10_Address
• 4 — CustomerToAccountLookup
• 12 — MACOLA10_SalesOrderHeader
• 13 — MACOLA10_SalesOrderDetail
• 15 — MACOLA10_SalesOrderHistoryHeader
• 16 — MACOLA10_SalesOrderHistoryDetail

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_MACOLA10_CustomerToAccountLookup reads vw_MACOLA10_Customer:
• vw_MACOLA10_Customer reads vw_MACOLA10_Account:
• vw_MACOLA10_Addresses reads vw_MACOLA10_Account:, vw_MACOLA10_Customer:
• vw_MACOLA10_SalesOrderHeader reads vw_MACOLA10_Account:, vw_MACOLA10_Customer:, vw_MACOLA10_Addresses:
• vw_MACOLA10_SalesOrderDetail reads vw_MACOLA10_SalesOrderHeader:
• vw_MACOLA10_SalesOrderHistoryHeader reads vw_MACOLA10_Account:, vw_MACOLA10_Customer:, vw_MACOLA10_Addresses:
• vw_MACOLA10_SalesOrderHistoryDetail reads vw_MACOLA10_SalesOrderHistoryHeader:

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	15	CommercientSFommercient_ArCustomerCode → CommercientSF__Commercient_ArCustomerCode__c, Region → Region__c, ParentID → ParentID, Phone → Phone, BillingStreet → BillingStreet
MACOLA10_Customer	CommercientSF19_MACOLA10_Customer__c	92	LOOKUPTO_Account → lookupto_account__c, AccountEmployeeId → accountemployeeid__c, AccountRating → accountrating__c, AccountTypeCode → accounttypecode__c, Acknowledge → acknowledge__c
MACOLA10_Address	CommercientSF19_MACOLA10_Address__c	62	LOOKUPTO_Account → lookupto_account__c, MACOLA10_Customer → MACOLA10_Customer__c, Main → main__c, Type → type__c, CustomerReq → customerreq__c
CustomerToAccountLookup	Account	2	CommercientSFommercient_ArCustomerCode → CommercientSF__Commercient_ArCustomerCode__c, MACOLA10_Customer → MACOLA10_Customer__c
MACOLA10_SalesOrderHeader	CommercientSF19_MACOLA10_SO_HEADER__c	89	ord_type → ord_type__c, ord_no → ord_no__c, status → status__c, entered_dt → entered_dt__c, ord_dt → ord_dt__c
MACOLA10_SalesOrderDetail	CommercientSF19_MACOLA10_SO_DETAIL__c	68	ord_type → ord_type__c, ord_no → ord_no__c, line_seq_no → line_seq_no__c, item_no → item_no__c, loc → loc__c
MACOLA10_SalesOrderHistoryHeader	CommercientSF19_MACOLA10_SO_HST_HEADER__c	96	ord_type → ord_type__c, ship_to_name → ship_to_name__c, ord_no → ord_no__c, status → status__c, entered_dt → entered_dt__c
MACOLA10_SalesOrderHistoryDetail	CommercientSF19_MACOLA10_SO_HST_DETAIL__c	81	erp_id → erp_id__c, ord_type → ord_type__c, ord_no → ord_no__c, line_seq_no → line_seq_no__c, item_no → item_no__c

6. Community templates

The catalogue carries 110 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: 110
• Default operations: insert on 110, update on 110, delete on 110
• Marked circular-sync: 0
• Licence groups they span: 10
• Destination objects: ContentDocument, Account, MACOLA10_Quote_Detail__c, MACOLA10_Quote_Header__c, MACOLA10_Sales_Order_Detail__c, MACOLA10_Sales_Order_Header__c, MACOLA10_Sales_Order_History_Detail__c, MACOLA10_Sales_Order_History_Header__c, MACOLA10_Transaction__c, Opportunity, CommercientSF19_MACOLA10_SO_DETAIL__c, CommercientSF19_MACOLA10_Address__c, CommercientSF19_MACOLA10_Item__c, CommercientSF19_MACOLA10_SO_HEADER__c, CommercientSF19__MACOLA10_Addresses__c, CommercientSF19__MACOLA10_Customer__c, CommercientSF19__MACOLA10_InvoiceHeader__c, CommercientSF19__MACOLA10_InvoiceLines__c, CommercientSF19__MACOLA10_salesOrderHeader__c, CommercientSF19__MACOLA10_SalesOrderLines__c, 8 more and 6 custom objects
• Object display names: DOCUMENT SYNC - MACOLA10 QUOTE, DOCUMENT SYNC - MACOLA10 SALES ORDER, DOCUMENT SYNC - MACOLA10 SALES ORDER HISTORY, GET ACCOUNT, SYNC MACOLA10 QUOTE DETAIL, SYNC MACOLA10 QUOTE HEADER, SYNC MACOLA10 SALES ORDER DETAIL, SYNC MACOLA10 SALES ORDER HEADER, SYNC MACOLA10 SALES ORDER HISTORY DETAIL, SYNC MACOLA10 SALES ORDER HISTORY HEADER, SYNC MACOLA10 TRANSACTIONS, SYNC OPPORTUNITY, 18 more and 5 further templates
• Template groups: Salesorder, Account, Opportunity, CRM Opportunity and Line, Invoice, Customer Multi Ship Addresses, Product

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_MACOLA10_Account
• vw_MACOLA10_CustomerToAccountLookup
• vw_MACOLA10_Customer
• vw_MACOLA10_Addresses
• vw_MACOLA10_SalesOrderHeader
• vw_MACOLA10_SalesOrderDetail
• vw_MACOLA10_SalesOrderHistoryHeader
• vw_MACOLA10_SalesOrderHistoryDetail

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 Macola 10 → 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.