CRMPro → Salesforce — ECi M1: what the shipped templates set up

CRMPro → Salesforce — ECi M1: 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/eci-m1.md, and that skill’s ERP table is what points at it. What follows is only what the shipped ECi M1 → 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, Child Account	SF_ERP_Salesforce_Clone_Organizations, SF_ERP_Salesforce_Clone_OrganizationLocations
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, existing ones updated, and records removed in the ERP are deleted.	Commercient37__ECIM1_ARinvoices__c, Commercient37__ECIM1_ARInvoiceLines__c	SF_ERP_Salesforce_Clone_ARinvoices, SF_ERP_Salesforce_Clone_ARInvoiceLines
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.	Commercient37__ECIM1_SalesOrders__c, Commercient37__ECIM1_SalesOrderLines__c	SF_ERP_Salesforce_Clone_SalesOrders, SF_ERP_Salesforce_Clone_SalesOrderLines

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_ECIM1_Account	vw_ECIM1_Account	'' / ''	1
Child Account	Child Account	CommercientSF__Commercient_ArCustomerCode__c	2	vw_ECIM1_ChildAccount	vw_ECIM1_ChildAccount	'' / ''	1
ECIM1 CustomerToAccountLookup	Account	CommercientSF__Commercient_ArCustomerCode__c	4	vw_ECIM1_CustomerToAccountLookup	vw_ECIM1_CustomerToAccountLookup	'' / ''	1
ECIM1 SalesOrderHeader	Commercient37__ECIM1_SalesOrders__c	Commercient37__ExternalKey__c	6	vw_ECIM1_SalesOrderHeader	vw_ECIM1_SalesOrderHeader	Commercient37__ / __c	1
ECIM1 SalesOrderDetail	Commercient37__ECIM1_SalesOrderLines__c	Commercient37__ExternalKey__c	7	vw_ECIM1_SalesOrderDetail	vw_ECIM1_SalesOrderDetail	Commercient37__ / __c	1
ECIM1 InvoiceHeader	Commercient37__ECIM1_ARinvoices__c	Commercient37__ExternalKey__c	8	vw_ECIM1_InvoiceHeader	vw_ECIM1_InvoiceHeader	Commercient37__ / __c	1
ECIM1 InvoiceDetail	Commercient37__ECIM1_ARInvoiceLines__c	Commercient37__ExternalKey__c	9	vw_ECIM1_InvoiceDetail	vw_ECIM1_InvoiceDetail	Commercient37__ / __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	Source tables
vw_ECIM1_Account	insert + update	vw_ECIM1_Account:	—	SF_ERP_Salesforce_Clone_Organizations, SF_ERP_Salesforce_Clone_OrganizationLocations
vw_ECIM1_ChildAccount	insert + update	vw_ECIM1_ChildAccount:	vw_ECIM1_Account:	SF_ERP_Salesforce_Clone_OrganizationLocations, SF_ERP_Salesforce_Clone_Organizations
vw_ECIM1_CustomerToAccountLookup	insert + update	vw_ECIM1_CustomerToAccountLookup:	vw_ECIM1_Customer:, vw_ECIM1_Account:	SF_ERP_Salesforce_Clone_Organizations
vw_ECIM1_SalesOrderHeader	insert + update	vw_ECIM1_SalesOrderHeader:	vw_ECIM1_Account:, vw_ECIM1_Customer:	SF_ERP_Salesforce_Clone_SalesOrders
vw_ECIM1_SalesOrderDetail	insert + update	vw_ECIM1_SalesOrderDetail:	vw_ECIM1_SalesOrderHeader:	SF_ERP_Salesforce_Clone_SalesOrderLines
vw_ECIM1_InvoiceHeader	insert + update	vw_ECIM1_InvoiceHeader:	vw_ECIM1_Account:, vw_ECIM1_Customer:	SF_ERP_Salesforce_Clone_ARinvoices
vw_ECIM1_InvoiceDetail	insert + update	vw_ECIM1_InvoiceDetail:	vw_ECIM1_InvoiceHeader:	SF_ERP_Salesforce_Clone_ARInvoiceLines

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

• 1 — Account
• 2 — Child Account
• 4 — ECIM1 CustomerToAccountLookup
• 6 — ECIM1 SalesOrderHeader
• 7 — ECIM1 SalesOrderDetail
• 8 — ECIM1 InvoiceHeader
• 9 — ECIM1 InvoiceDetail

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_ECIM1_ChildAccount reads vw_ECIM1_Account:
• vw_ECIM1_CustomerToAccountLookup reads vw_ECIM1_Customer:, vw_ECIM1_Account:; no template in this set writes vw_ECIM1_Customer:
• vw_ECIM1_InvoiceHeader reads vw_ECIM1_Account:, vw_ECIM1_Customer:; no template in this set writes vw_ECIM1_Customer:
• vw_ECIM1_InvoiceDetail reads vw_ECIM1_InvoiceHeader:
• vw_ECIM1_SalesOrderHeader reads vw_ECIM1_Account:, vw_ECIM1_Customer:; no template in this set writes vw_ECIM1_Customer:
• vw_ECIM1_SalesOrderDetail reads vw_ECIM1_SalesOrderHeader:

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	13	CommercientSFommercient_ArCustomerCode → CommercientSF__Commercient_ArCustomerCode__c, Phone → Phone, BillingStreet → BillingStreet, BillingCity → BillingCity, BillingCountry → BillingCountry
Child Account	Child Account	14	CommercientSFommercient_ArCustomerCode → CommercientSF__Commercient_ArCustomerCode__c, Phone → Phone, BillingStreet → BillingStreet, BillingCity → BillingCity, BillingCountry → BillingCountry
ECIM1 CustomerToAccountLookup	Account	2	CommercientSFommercient_ArCustomerCode → CommercientSF__Commercient_ArCustomerCode__c, Commercient37__ECI_M1_Customer → Commercient37__ECI_M1_Customer__c
ECIM1 SalesOrderHeader	Commercient37__ECIM1_SalesOrders__c	86	Account → Account, Organizations → Commercient37__Organizations__c, ompSalesOrderID → Commercient37__ompSalesOrderID__c, ompPlantID → Commercient37__ompPlantID__c, ompPlantDepartmentID → Commercient37__ompPlantDepartmentID__c
ECIM1 SalesOrderDetail	Commercient37__ECIM1_SalesOrderLines__c	67	SalesOrders → Commercient37__SalesOrders__c, omlSalesOrderID → Commercient37__omlSalesOrderID__c, omlSalesOrderLineID → Commercient37__omlSalesOrderLineID__c, omlPartID → Commercient37__omlPartID__c, omlOrgPartID → Commercient37__omlOrgPartID__c
ECIM1 InvoiceHeader	Commercient37__ECIM1_ARinvoices__c	93	Account → Account, Organizations → Commercient37__Organizations__c, arpARInvoiceID → arpARInvoiceID, arpInvoiceType → arpInvoiceType, arpCreditARInvoiceID → arpCreditARInvoiceID
ECIM1 InvoiceDetail	Commercient37__ECIM1_ARInvoiceLines__c	94	ARinvoices → ARinvoices, arlARInvoiceID → arlARInvoiceID, arlARInvoiceLineID → arlARInvoiceLineID, arlLineType → Commercient37__arlLineType__c, arlPartID → Commercient37__arlPartID__c

6. Community templates

The catalogue carries 27 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: 27
• Default operations: insert on 27, update on 27, delete on 27
• Marked circular-sync: 0
• Licence groups they span: 7
• Destination objects: Account, Child Account, Commercient37__ECIM1_ARInvoiceLines__c, Commercient37__ECIM1_OrganizationLocations__c, Commercient37__ECIM1_SalesOrderLines__c, Commercient37__ECIM1_SalesOrders__c, ACCOUNTMATCHING__c, Contact, CONTACTMATCHING__c, User and 2 custom objects
• Object display names: Child Account, Account, ECIM1 Customer, ECIM1 CustomerToAccountLookup, ECIM1 InvoiceDetail, ECIM1 InvoiceHeader, ECIM1 SalesOrderDetail, ECIM1 SalesOrderHeader, ECIM1 ShipToAddress, Contact, Get Users, SYNC ACCOUNTMATCHING and 1 more
• Template groups: Account, Invoice, Salesorder, Customer Multi Ship Addresses

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_ECIM1_Account
• vw_ECIM1_ChildAccount
• vw_ECIM1_CustomerToAccountLookup
• vw_ECIM1_InvoiceHeader
• vw_ECIM1_InvoiceDetail
• vw_ECIM1_SalesOrderHeader
• vw_ECIM1_SalesOrderDetail

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 ECi M1 → 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.