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

CRMPro → Salesforce — Epicor 10 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/epicor-10-cloud.md, and that skill’s ERP table is what points at it. What follows is only what the shipped Epicor 10 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
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, CommercientSF10__EPICOR10_Customer__c, CommercientSF10__EPICOR10_SalesRep__c	SF_ERP_Salesforce_Clone_Customer, SF_ERP_Salesforce_Clone_ShipTo, SF_ERP_Salesforce_Clone_CustCnt, SF_ERP_Salesforce_Clone_SalesRep
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.	CommercientSF10__EPICOR10_ShipTo__c	SF_ERP_Salesforce_Clone_ShipTo, SF_ERP_Salesforce_Clone_Customer
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.	CommercientSF10__EPICOR10_InvcHead__c, CommercientSF10__EPICOR10_InvcDtl__c	SF_ERP_Salesforce_Clone_InvcHead, SF_ERP_Salesforce_Clone_Customer, CommercientFlags, SF_ERP_Salesforce_Clone_InvcDtl
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.	CommercientSF10__EPICOR10_OrderHed__c, CommercientSF10__EPICOR10_OrderDtl__c	SF_ERP_Salesforce_Clone_OrderHed, SF_ERP_Salesforce_Clone_Customer, CommercientFlags, SF_ERP_Salesforce_Clone_OrderDtl

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
EPICOR10CLOUD SalesPerson	CommercientSF10__EPICOR10_SalesRep__c	CommercientSF10__ExternalKey__c	1	vw_EPICOR10CLOUD_SalesPerson	vw_EPICOR10CLOUD_SalesPerson	CommercientSF10__ / __c	1
Account	Account	CommercientSF__Commercient_ArCustomerCode__c	2	vw_EPICOR10CLOUD_Account	vw_EPICOR10CLOUD_Account	'' / ''	1
Contact	Contact	ExternalKey__c	3	vw_EPICOR10CLOUD_Contact	vw_EPICOR10CLOUD_Contact	'' / ''	1
EPICOR10CLOUD Customer	CommercientSF10__EPICOR10_Customer__c	CommercientSF10__ExternalKey__c	4	vw_EPICOR10CLOUD_Customer	vw_EPICOR10CLOUD_Customer	CommercientSF10__ / __c	1
EPICOR10CLOUD CustomerToAccountLookup	Account	CommercientSF__Commercient_ArCustomerCode__c	5	vw_EPICOR10CLOUD_CustomerToAccountLookup	vw_EPICOR10CLOUD_CustomerToAccountLookup	'' / ''	1
EPICOR10CLOUD ShipToAddress	CommercientSF10__EPICOR10_ShipTo__c	CommercientSF10__ExternalKey__c	6	vw_EPICOR10CLOUD_ShipToAddress	vw_EPICOR10CLOUD_ShipToAddress	CommercientSF10__ / __c	1
EPICOR10CLOUD SalesOrderHeader	CommercientSF10__EPICOR10_OrderHed__c	CommercientSF10__ExternalKey__c	7	vw_EPICOR10CLOUD_SalesOrderHeader	vw_EPICOR10CLOUD_SalesOrderHeader	CommercientSF10__ / __c	1
EPICOR10CLOUD SalesOrderDetail	CommercientSF10__EPICOR10_OrderDtl__c	CommercientSF10__ExternalKey__c	8	vw_EPICOR10CLOUD_SalesOrderDetail	vw_EPICOR10CLOUD_SalesOrderDetail	CommercientSF10__ / __c	1
EPICOR10CLOUD InvoiceHeader	CommercientSF10__EPICOR10_InvcHead__c	CommercientSF10__ExternalKey__c	9	vw_EPICOR10CLOUD_InvoiceHeader	vw_EPICOR10CLOUD_InvoiceHeader	CommercientSF10__ / __c	1
EPICOR10CLOUD InvoiceDetail	CommercientSF10__EPICOR10_InvcDtl__c	CommercientSF10__ExternalKey__c	10	vw_EPICOR10CLOUD_InvoiceDetail	vw_EPICOR10CLOUD_InvoiceDetail	CommercientSF10__ / __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_EPICOR10CLOUD_SalesPerson	insert + update	vw_EPICOR10CLOUD_SalesPerson:	—	EXTERNALKEY	SF_ERP_Salesforce_Clone_SalesRep
vw_EPICOR10CLOUD_Account	insert + update	vw_EPICOR10CLOUD_Account:	vw_EPICOR10CLOUD_SalesPerson:	—	SF_ERP_Salesforce_Clone_Customer, SF_ERP_Salesforce_Clone_ShipTo
vw_EPICOR10CLOUD_Contact	insert + update	vw_EPICOR10CLOUD_Contact:	vw_EPICOR10CLOUD_Account:	—	SF_ERP_Salesforce_Clone_CustCnt, SF_ERP_Salesforce_Clone_Customer
vw_EPICOR10CLOUD_Customer	insert + update	vw_EPICOR10CLOUD_Customer:	vw_EPICOR10CLOUD_Account:, vw_EPICOR10CLOUD_SalesPerson:	EXTERNALKEY	SF_ERP_Salesforce_Clone_Customer
vw_EPICOR10CLOUD_CustomerToAccountLookup	insert + update	vw_EPICOR10CLOUD_CustomerToAccountLookup:	vw_EPICOR10CLOUD_Customer:	—	SF_ERP_Salesforce_Clone_Customer
vw_EPICOR10CLOUD_ShipToAddress	insert + update	vw_EPICOR10CLOUD_ShipToAddress:	vw_EPICOR10CLOUD_Account:, vw_EPICOR10CLOUD_Customer:	ExternalKey	SF_ERP_Salesforce_Clone_ShipTo, SF_ERP_Salesforce_Clone_Customer
vw_EPICOR10CLOUD_SalesOrderHeader	insert + update	vw_EPICOR10CLOUD_SalesOrderHeader:	vw_EPICOR10CLOUD_Account:, vw_EPICOR10CLOUD_Customer:, vw_EPICOR10CLOUD_SalesPerson:	EXTERNALKEY	SF_ERP_Salesforce_Clone_OrderHed, SF_ERP_Salesforce_Clone_Customer, CommercientFlags
vw_EPICOR10CLOUD_SalesOrderDetail	insert + update	vw_EPICOR10CLOUD_SalesOrderDetail:	vw_EPICOR10CLOUD_SalesOrderHeader:	EXTERNALKEY	SF_ERP_Salesforce_Clone_OrderDtl
vw_EPICOR10CLOUD_InvoiceHeader	insert + update	vw_EPICOR10CLOUD_InvoiceHeader:	vw_EPICOR10CLOUD_Account:, vw_EPICOR10CLOUD_Customer:, vw_EPICOR10CLOUD_SalesPerson:	EXTERNALKEY	SF_ERP_Salesforce_Clone_InvcHead, SF_ERP_Salesforce_Clone_Customer, CommercientFlags
vw_EPICOR10CLOUD_InvoiceDetail	insert + update	vw_EPICOR10CLOUD_InvoiceDetail:	vw_EPICOR10CLOUD_InvoiceHeader:	EXTERNALKEY	SF_ERP_Salesforce_Clone_InvcDtl

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

• 1 — EPICOR10CLOUD SalesPerson
• 2 — Account
• 3 — Contact
• 4 — EPICOR10CLOUD Customer
• 5 — EPICOR10CLOUD CustomerToAccountLookup
• 6 — EPICOR10CLOUD ShipToAddress
• 7 — EPICOR10CLOUD SalesOrderHeader
• 8 — EPICOR10CLOUD SalesOrderDetail
• 9 — EPICOR10CLOUD InvoiceHeader
• 10 — EPICOR10CLOUD 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_EPICOR10CLOUD_Account reads vw_EPICOR10CLOUD_SalesPerson:
• vw_EPICOR10CLOUD_CustomerToAccountLookup reads vw_EPICOR10CLOUD_Customer:
• vw_EPICOR10CLOUD_Contact reads vw_EPICOR10CLOUD_Account:
• vw_EPICOR10CLOUD_Customer reads vw_EPICOR10CLOUD_Account:, vw_EPICOR10CLOUD_SalesPerson:
• vw_EPICOR10CLOUD_ShipToAddress reads vw_EPICOR10CLOUD_Account:, vw_EPICOR10CLOUD_Customer:
• vw_EPICOR10CLOUD_InvoiceHeader reads vw_EPICOR10CLOUD_Account:, vw_EPICOR10CLOUD_Customer:, vw_EPICOR10CLOUD_SalesPerson:
• vw_EPICOR10CLOUD_InvoiceDetail reads vw_EPICOR10CLOUD_InvoiceHeader:
• vw_EPICOR10CLOUD_SalesOrderHeader reads vw_EPICOR10CLOUD_Account:, vw_EPICOR10CLOUD_Customer:, vw_EPICOR10CLOUD_SalesPerson:
• vw_EPICOR10CLOUD_SalesOrderDetail reads vw_EPICOR10CLOUD_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
EPICOR10CLOUD SalesPerson	CommercientSF10__EPICOR10_SalesRep__c	49	Address1 → CommercientSF10__Address1__c, Address2 → CommercientSF10__Address2__c, Address3 → CommercientSF10__Address3__c, AlertFlag → CommercientSF10__AlertFlag__c, CellPhoneNum → CommercientSF10__CellPhoneNum__c
Account	Account	12	CommercientSFommercient_ArCustomerCode → CommercientSF__Commercient_ArCustomerCode__c, Phone → Phone, BillingStreet → BillingStreet, BillingCity → BillingCity, BillingCountry → BillingCountry
Contact	Contact	8	AccountID → AccountID, LastName → LastName, FirstName → FirstName, Suffix → Suffix, Email → Email
EPICOR10CLOUD Customer	CommercientSF10__EPICOR10_Customer__c	113	THBRANCHID → thbranchid__c, CUSTPRICINGSCHEMA → custpricingschema__c, PARAMCODE → paramcode__c, AGAFIPRESPONSIBILITYCODE → agafipresponsibilitycode__c, AGBILLTOPROVINCECODE → agbilltoprovincecode__c
EPICOR10CLOUD CustomerToAccountLookup	Account	2	CommercientSFommercient_ArCustomerCode → CommercientSF__Commercient_ArCustomerCode__c, CommercientSF10__EPICOR10_Customer_Master → CommercientSF10__EPICOR10_Customer_Master__c
EPICOR10CLOUD ShipToAddress	CommercientSF10__EPICOR10_ShipTo__c	92	AddlHdlgFlag → CommercientSF10__AddlHdlgFlag__c, Address1 → CommercientSF10__Address1__c, Address2 → CommercientSF10__Address2__c, Address3 → CommercientSF10__Address3__c, AddressVal → CommercientSF10__AddressVal__c
EPICOR10CLOUD SalesOrderHeader	CommercientSF10__EPICOR10_OrderHed__c	96	ApplyChrg → ApplyChrg, ARLOCID → ARLOCID, BTConNum → BTConNum, BTCustNum → BTCustNum, CancelAfterDate → CancelAfterDate
EPICOR10CLOUD SalesOrderDetail	CommercientSF10__EPICOR10_OrderDtl__c	92	AdvanceBillBal → AdvanceBillBal, BasePartNum → CommercientSF10__BasePartNum__c, BaseRevisionNum → CommercientSF10__BaseRevisionNum__c, BreakListCode → BreakListCode, ChangeDate → CommercientSF10__ChangeDate__c
EPICOR10CLOUD InvoiceHeader	CommercientSF10__EPICOR10_InvcHead__c	96	AGLegalNumber → CommercientSF10__AGLegalNumber__c, ApplyDate → CommercientSF10__ApplyDate__c, BillConNum → BillConNum, BillConNum1 → BillConNum1, BillingDate → CommercientSF10__BillingDate__c
EPICOR10CLOUD InvoiceDetail	CommercientSF10__EPICOR10_InvcDtl__c	90	ABTUID → CommercientSF10__ABTUID__c, AdvanceBillCredit → AdvanceBillCredit, AdvGainLoss → CommercientSF10__AdvGainLoss__c, AssetNum → CommercientSF10__AssetNum__c, BTCustNum → BTCustNum

6. Community templates

The catalogue carries 79 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: 79
• Default operations: insert on 79, update on 79, delete on 79
• Marked circular-sync: 0
• Licence groups they span: 12
• Destination objects: Account, CommercientSF10__EPICOR10_OrderHed__c, CommercientSF10__EPICOR10_InvcDtl__c, CommercientSF10__EPICOR10_InvcHead__c, CommercientSF10__EPICOR10_OrderDtl__c, CommercientSF10__EPICOR10_Customer__c, CommercientSF10__EPICOR10_QuoteHed__c, CommercientSF10__EPICOR10_SalesRep__c, CommercientSF10__EPICOR10_ShipTo__c, Opportunity, Product2, CommercientSF10__EPICOR10_ItemWarehouse__c, CommercientSF10__EPICOR10_QuoteDtl__c, Contact, CommercientSF10__EPICOR10_ItemMaster__c, PricebookEntry, PriceBookEntry, EPICOR10_PriceList__c, EPICOR10_SerialNo__c, EPICOR10_ShipDtl__c, 3 more and 2 custom objects
• Object display names: Account, Contacts, EPICOR10CLOUD ACCOUNT, EPICOR10CLOUD Customer, EPICOR10CLOUD CUSTOMER, EPICOR10CLOUD CustomerToAccountLookup, EPICOR10CLOUD CUSTOMERTOACCOUNTLOOKUP, EPICOR10CLOUD InvoiceDetail, EPICOR10CLOUD INVOICEDETAIL, EPICOR10CLOUD InvoiceHeader, EPICOR10CLOUD INVOICEHEADER, EPICOR10CLOUD ITEMMASTER, 35 more and 10 further templates
• Template groups: Account, Product, Invoice, Salesorder, Opportunity, 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_EPICOR10CLOUD_Account
• vw_EPICOR10CLOUD_CustomerToAccountLookup
• vw_EPICOR10CLOUD_Contact
• vw_EPICOR10CLOUD_Customer
• vw_EPICOR10CLOUD_ShipToAddress
• vw_EPICOR10CLOUD_InvoiceHeader
• vw_EPICOR10CLOUD_InvoiceDetail
• vw_EPICOR10CLOUD_SalesOrderHeader
• vw_EPICOR10CLOUD_SalesOrderDetail
• vw_EPICOR10CLOUD_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 Epicor 10 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.