CRMPro → Salesforce — E-solver: what the shipped templates set up

CRMPro → Salesforce — E-solver: 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/e-solver.md, and that skill’s ERP table is what points at it. What follows is only what the shipped E-solver → 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, account, CommercientSF8_ESOLVER_CUSTOMER__c, CommercientSF8_ESOLVER_SalesPerson__c	SF_ERP_Salesforce_Clone_AnagrGenCliFor, SF_ERP_Salesforce_Clone_ClientiFornitori, SF_ERP_Salesforce_Clone_AnagrGenIndirizzi, SF_ERP_Salesforce_Clone_CliForCondizioniComm, SF_ERP_Salesforce_Clone_CampiUtenteTabValori, vw_ESOLVER_Account_View
CRM Ownership	The templates push User to Salesforce. New records are created, existing ones updated, and records removed in the ERP are deleted.	User	—
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.	CommercientSF8_ESOLVER_SHIPTOADDRESS__c	SF_ERP_Salesforce_Clone_AnagrGenIndirizzi, SF_ERP_Salesforce_Clone_ClientiFornitori, SF_ERP_Salesforce_Clone_CliForDatiIndirizzo
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.	CommercientSF8_ESOLVER_INVOICEHEADER__c, CommercientSF8_ESOLVER_INVOICEDETAIL__c	SF_ERP_Salesforce_Clone_DocElencoGen, SF_ERP_Salesforce_Clone_DocUniTestata, SF_ERP_Salesforce_Clone_DocUniPiede, CommercientFlags, SF_ERP_Salesforce_Clone_DocUniRigheFattVen
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.	CommercientSF8_ESOLVER_SALESORDERHEADER__c, CommercientSF8_ESOLVER_SALESORDERDETAIL__c	SF_ERP_Salesforce_Clone_DocElencoGen, SF_ERP_Salesforce_Clone_DocUniTestata, SF_ERP_Salesforce_Clone_DocUniPiede, SF_ERP_Salesforce_Clone_DocUniRigheOrdCli

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
Get User	User	—	0	vw_ESOLVER_User	1=0	'' / ''	1
ESOLVER_SalesPerson	CommercientSF8_ESOLVER_SalesPerson__c	ExternalKey__c	1	vw_ESOLVER_SalesPerson	vw_ESOLVER_SalesPerson	'' / __c	1
Account	Account	CommercientSF__Commercient_ArCustomerCode__c	2	vw_ESOLVER_Account	vw_ESOLVER_Account	'' / ''	1
CRM AccountChild	account	CommercientSF__Commercient_ArCustomerCode__c	3	vw_ESOLVER_Account_Child	vw_ESOLVER_Account_Child	'' / ''	1
ESOLVER_Customer	CommercientSF8_ESOLVER_CUSTOMER__c	ExternalKey__c	3	vw_ESOLVER_Customer	vw_ESOLVER_Customer	'' / __c	1
AccountCustomerLookup	Account	CommercientSF__Commercient_ArCustomerCode__c	4	vw_ESOLVER_CustomerToAccountLookup	vw_ESOLVER_CustomerToAccountLookup	'' / ''	1
ESOLVER_Address	CommercientSF8_ESOLVER_SHIPTOADDRESS__c	ExternalKey__c	5	vw_ESOLVER_MasterDataAddresses	vw_ESOLVER_MasterDataAddresses	'' / __c	1
ESOLVER_Sales Order	CommercientSF8_ESOLVER_SALESORDERHEADER__c	ExternalKey__c	6	vw_ESOLVER_SalesOrderHeader	vw_ESOLVER_SalesOrderHeader	'' / __c	1
ESOLVER_Sales OrderLine	CommercientSF8_ESOLVER_SALESORDERDETAIL__c	ExternalKey__c	7	vw_ESOLVER_SalesOrderDetail	vw_ESOLVER_SalesOrderDetail	'' / __c	1
ESOLVER_Invoice Header	CommercientSF8_ESOLVER_INVOICEHEADER__c	ExternalKey__c	8	vw_ESOLVER_InvoiceHeader	vw_ESOLVER_InvoiceHeader	'' / __c	1
ESOLVER_Invoice Details	CommercientSF8_ESOLVER_INVOICEDETAIL__c	ExternalKey__c	9	vw_ESOLVER_InvoiceDetail	vw_ESOLVER_InvoiceDetail	'' / __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. Get_SOQL_Query carries a query on Get User — 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_ESOLVER_SalesPerson	insert + update	vw_ESOLVER_SalesPerson:	—	ExternalKey	SF_ERP_Salesforce_Clone_ClientiFornitori, SF_ERP_Salesforce_Clone_AnagrGenCliFor, SF_ERP_Salesforce_Clone_AnagrGenIndirizzi
vw_ESOLVER_Account		vw_ESOLVER_Account:	vw_ESOLVER_SalesPerson:, vw_ESOLVER_User:	—	SF_ERP_Salesforce_Clone_AnagrGenCliFor, SF_ERP_Salesforce_Clone_ClientiFornitori, SF_ERP_Salesforce_Clone_AnagrGenIndirizzi, SF_ERP_Salesforce_Clone_CliForCondizioniComm, SF_ERP_Salesforce_Clone_CampiUtenteTabValori
vw_ESOLVER_Account_Child	insert + update	vw_ESOLVER_Account_Child:	vw_ESOLVER_Account:, vw_ESOLVER_SalesPerson:, vw_ESOLVER_User:	CommercientSF__Commercient_ArCustomerCode__c	vw_ESOLVER_Account_View
vw_ESOLVER_Customer	insert-only	vw_ESOLVER_Customer:	vw_ESOLVER_Account:	ExternalKey	SF_ERP_Salesforce_Clone_AnagrGenCliFor, SF_ERP_Salesforce_Clone_ClientiFornitori, SF_ERP_Salesforce_Clone_AnagrGenIndirizzi, SF_ERP_Salesforce_Clone_CliForCondizioniComm, SF_ERP_Salesforce_Clone_CampiUtenteTabValori
vw_ESOLVER_CustomerToAccountLookup	insert-only	vw_ESOLVER_CustomerToAccountLookup:	vw_ESOLVER_Customer:	CommercientSF__Commercient_ArCustomerCode__c	SF_ERP_Salesforce_Clone_AnagrGenCliFor, SF_ERP_Salesforce_Clone_ClientiFornitori, SF_ERP_Salesforce_Clone_AnagrGenIndirizzi, SF_ERP_Salesforce_Clone_CliForCondizioniComm, SF_ERP_Salesforce_Clone_CampiUtenteTabValori
vw_ESOLVER_MasterDataAddresses	insert-only	vw_ESOLVER_MasterDataAddresses:	vw_ESOLVER_Account:, vw_ESOLVER_Customer:	ExternalKey	SF_ERP_Salesforce_Clone_AnagrGenIndirizzi, SF_ERP_Salesforce_Clone_ClientiFornitori, SF_ERP_Salesforce_Clone_CliForDatiIndirizzo
vw_ESOLVER_SalesOrderHeader	insert + update	vw_ESOLVER_SalesOrderHeader:	vw_ESOLVER_Account:, vw_ESOLVER_Customer:	ExternalKey	SF_ERP_Salesforce_Clone_DocElencoGen, SF_ERP_Salesforce_Clone_DocUniTestata, SF_ERP_Salesforce_Clone_DocUniPiede
vw_ESOLVER_SalesOrderDetail	insert + update	vw_ESOLVER_SalesOrderDetail:	vw_ESOLVER_SalesOrderHeader:	ExternalKey	SF_ERP_Salesforce_Clone_DocElencoGen, SF_ERP_Salesforce_Clone_DocUniTestata, SF_ERP_Salesforce_Clone_DocUniPiede, SF_ERP_Salesforce_Clone_DocUniRigheOrdCli
vw_ESOLVER_InvoiceHeader	insert + update	vw_ESOLVER_InvoiceHeader:	vw_ESOLVER_Account:, vw_ESOLVER_Customer:	ExternalKey	SF_ERP_Salesforce_Clone_DocElencoGen, SF_ERP_Salesforce_Clone_DocUniTestata, SF_ERP_Salesforce_Clone_DocUniPiede, CommercientFlags
vw_ESOLVER_InvoiceDetail	insert + update	vw_ESOLVER_InvoiceDetail:	vw_ESOLVER_InvoiceHeader:	ExternalKey	SF_ERP_Salesforce_Clone_DocElencoGen, SF_ERP_Salesforce_Clone_DocUniTestata, SF_ERP_Salesforce_Clone_DocUniPiede, SF_ERP_Salesforce_Clone_DocUniRigheFattVen

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

• 0 — Get User
• 1 — ESOLVER_SalesPerson
• 2 — Account
• 3 — CRM AccountChild, ESOLVER_Customer
• 4 — AccountCustomerLookup
• 5 — ESOLVER_Address
• 6 — ESOLVER_Sales Order
• 7 — ESOLVER_Sales OrderLine
• 8 — ESOLVER_Invoice Header
• 9 — ESOLVER_Invoice Details

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_ESOLVER_Account reads vw_ESOLVER_SalesPerson:, vw_ESOLVER_User:
• vw_ESOLVER_Account_Child reads vw_ESOLVER_Account:, vw_ESOLVER_SalesPerson:, vw_ESOLVER_User:
• vw_ESOLVER_CustomerToAccountLookup reads vw_ESOLVER_Customer:
• vw_ESOLVER_Customer reads vw_ESOLVER_Account:
• vw_ESOLVER_MasterDataAddresses reads vw_ESOLVER_Account:, vw_ESOLVER_Customer:
• vw_ESOLVER_InvoiceHeader reads vw_ESOLVER_Account:, vw_ESOLVER_Customer:
• vw_ESOLVER_InvoiceDetail reads vw_ESOLVER_InvoiceHeader:
• vw_ESOLVER_SalesOrderHeader reads vw_ESOLVER_Account:, vw_ESOLVER_Customer:
• vw_ESOLVER_SalesOrderDetail reads vw_ESOLVER_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
ESOLVER_SalesPerson	CommercientSF8_ESOLVER_SalesPerson__c	16	DBGroup → dbgroup__c, MasterDataType → masterdatatype__c, CodCustSupplier → codcustsupplier__c, AnagAgente → anagagente__c, ProgressiveNumber → progressivenumber__c
Account	Account	30	CommercientSFommercient_ArCustomerCode → CommercientSF__Commercient_ArCustomerCode__c, AccountNumber → accountnumber__c, Sales_Agent → Sales_Agent__c, Active_in_Esolver → Active_in_Esolver__c, Email → Email__c
CRM AccountChild	account	19	CommercientSFommercient_ArCustomerCode → CommercientSF__Commercient_ArCustomerCode__c, ParentID → ParentID, Phone → Phone, BillingStreet → BillingStreet, BillingCity → BillingCity
ESOLVER_Customer	CommercientSF8_ESOLVER_CUSTOMER__c	18	LOOKUPTO_Account → account__c, DBGroup → dbgroup__c, ValField16 → valfield16__c, BillingName1 → billingname1__c, PhoneNO → phoneno__c
AccountCustomerLookup	Account	2	CommercientSFommercient_ArCustomerCode → CommercientSF__Commercient_ArCustomerCode__c, ESOLVER_Customer → ESOLVER_Customer__c
ESOLVER_Address	CommercientSF8_ESOLVER_SHIPTOADDRESS__c	44	IdMasterdatacustomer → idmasterdatacustomer__c, ProgressiveNumber → progressivenumber__c, LeadTimeTrasporto → leadtimetrasporto__c, Alternativecode → alternativecode__c, ReferenceGroup → referencegroup__c
ESOLVER_Sales Order	CommercientSF8_ESOLVER_SALESORDERHEADER__c	28	DocumentClass → documentclass__c, DocumentGroup → documentgroup__c, Reg_Code → reg_code__c, RegistrationDate → registrationdate__c, Registration_Num → registration_num__c
ESOLVER_Sales OrderLine	CommercientSF8_ESOLVER_SALESORDERDETAIL__c	42	DocumentGroup → documentgroup__c, RegistrationDate → registrationdate__c, RegistrationNum → registrationnum__c, CodCustSupplier → codcustsupplier__c, UdCTotDoc → udctotdoc__c
ESOLVER_Invoice Header	CommercientSF8_ESOLVER_INVOICEHEADER__c	28	DocumentClass → documentclass__c, DocumentGroup → documentgroup__c, Reg_Code → reg_code__c, RegistrationDate → registrationdate__c, Registration_Num → registration_num__c
ESOLVER_Invoice Details	CommercientSF8_ESOLVER_INVOICEDETAIL__c	44	DocumentClass → documentclass__c, Reg_Code → reg_code__c, DocumentGroup → documentgroup__c, RegistrationDate → registrationdate__c, RegistrationNum → registrationnum__c

6. Community templates

The catalogue carries 12 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: 12
• Default operations: insert on 12, update on 12, delete on 12
• Marked circular-sync: 0
• Licence groups they span: 7
• Destination objects: Account, account, CommercientSF8_ESOLVER_CUSTOMER__c, CommercientSF8_ESOLVER_INVOICEDETAIL__c, CommercientSF8_ESOLVER_INVOICEHEADER__c, CommercientSF8_ESOLVER_SALESORDERDETAIL__c, CommercientSF8_ESOLVER_SALESORDERHEADER__c, CommercientSF8_ESOLVER_SalesPerson__c, CommercientSF8_ESOLVER_SHIPTOADDRESS__c, RecordType and a custom object
• Object display names: Account, AccountCustomerLookup, CRM AccountChild, ESOLVER Invoice_CreditNote, ESOLVER_Address, ESOLVER_Customer, ESOLVER_Invoice Details, ESOLVER_Invoice Header, ESOLVER_Sales Order, ESOLVER_Sales OrderLine, ESOLVER_SalesPerson, Get Recordtype
• 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_ESOLVER_Account
• vw_ESOLVER_Account_Child
• vw_ESOLVER_CustomerToAccountLookup
• vw_ESOLVER_User
• vw_ESOLVER_Customer
• vw_ESOLVER_MasterDataAddresses
• vw_ESOLVER_InvoiceHeader
• vw_ESOLVER_InvoiceDetail
• vw_ESOLVER_SalesOrderHeader
• vw_ESOLVER_SalesOrderDetail
• vw_ESOLVER_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 E-solver → 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.