CRMPro → Salesforce — Infor10 Distribution Business: what the shipped templates set up

CRMPro → Salesforce — Infor10 Distribution Business: 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/infor10-distribution-business.md, and that skill’s ERP table is what points at it. What follows is only what the shipped Infor10 Distribution Business → 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 Users	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, CommercientSF18__arsc__c, CommercientSF18__smsn__c	SF_ERP_Salesforce_Clone_arsc, SF_ERP_Salesforce_Clone_arss, SF_ERP_Salesforce_Clone_ttccom1401000, SF_ERP_Salesforce_Clone_ttsctm3001001, SF_ERP_Salesforce_Clone_smsn
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.	CommercientSF18__aret_InvoiceHeader__c, CommercientSF18__oeel_InvoiceDetail__c	SF_ERP_Salesforce_Clone_aret, CommercientFlags, SF_ERP_Salesforce_Clone_oeel, SF_ERP_Salesforce_Clone_oeeh
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.	CommercientSF18__oeeh__c, CommercientSF18__oeel__c	SF_ERP_Salesforce_Clone_oeeh, SF_ERP_Salesforce_Clone_arsc, CommercientFlags, SF_ERP_Salesforce_Clone_oeel

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 Users	User	CommercientSF6__SalespersonCode__c	1	vw_INFORSXE_User	Select 1 = 0	'' / ''	1
SYNC SALESPERSON	CommercientSF18__smsn__c	CommercientSF18__ExternalKey__c	1	vw_INFORSXE_Salesperson	vw_INFORSXE_Salesperson	CommercientSF18__ / __c	1
SYNC ACCOUNT	Account	CommercientSF__Commercient_ArCustomerCode__c	2	vw_INFORSXE_Account	vw_INFORSXE_Account	'' / ''	1
SYNC CUSTOMER	CommercientSF18__arsc__c	CommercientSF18__ExternalKey__c	3	vw_INFORSXE_Customer	vw_INFORSXE_Customer	CommercientSF18__ / __c	1
SYNC CUSTOMERTOACCOUNTLOOKUP	Account	CommercientSF__Commercient_ArCustomerCode__c	4	vw_INFORSXE_CustomerToAccountLookup	vw_INFORSXE_CustomerToAccountLookup	'' / ''	1
SYNC STANDARD CONTACT	Contact	ExternalKey__c	5	vw_INFOR10DISTRIBUTIONBUSINESS_StandardContact	vw_INFOR10DISTRIBUTIONBUSINESS_StandardContact	'' / ''	1
Order Headers	CommercientSF18__oeeh__c	CommercientSF18__ExternalKey__c	10	vw_INFORSXE_SalesOrderHeader	vw_INFORSXE_SalesOrderHeader	CommercientSF18__ / __c	1
Order Details	CommercientSF18__oeel__c	CommercientSF18__ExternalKey__c	11	vw_INFORSXE_SalesOrderLine	vw_INFORSXE_SalesOrderLine	CommercientSF18__ / __c	1
SYNC INVOICEHEADER	CommercientSF18__aret_InvoiceHeader__c	CommercientSF18__ExternalKey__c	12	vw_INFORSXE_InvoiceHeader	vw_INFORSXE_InvoiceHeader	CommercientSF18__ / __c	1
SYNC INVOICELINEITEM	CommercientSF18__oeel_InvoiceDetail__c	CommercientSF18__ExternalKey__c	13	vw_INFORSXE_InvoiceLineItem	vw_INFORSXE_InvoiceLineItem	CommercientSF18__ / __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, Sync_Batch_Size 200. IsAccountMatching is set on SYNC ACCOUNT. Text columns a template does not use are inserted as '' rather than left NULL. Get_SOQL_Query carries a query on Get Users — 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_INFORSXE_Salesperson	insert + update	vw_INFORSXE_Salesperson:	—	—	SF_ERP_Salesforce_Clone_smsn
vw_INFORSXE_Account	insert + update	vw_INFORSXE_Account:	vw_INFORSXE_Salesperson:, vw_INFORSXE_User:	—	SF_ERP_Salesforce_Clone_arsc, SF_ERP_Salesforce_Clone_arss
vw_INFORSXE_Customer	insert + update	vw_INFORSXE_Customer:	vw_INFORSXE_Account:, vw_INFORSXE_Salesperson:	ExternalKey	SF_ERP_Salesforce_Clone_arsc
vw_INFORSXE_CustomerToAccountLookup	insert + update	vw_INFORSXE_CustomerToAccountLookup:	vw_INFORSXE_Customer:	—	SF_ERP_Salesforce_Clone_arsc
vw_INFOR10DISTRIBUTIONBUSINESS_StandardContact	insert + update	vw_INFOR10DISTRIBUTIONBUSINESS_StandardContact:	vw_INFOR10DISTRIBUTIONBUSINESS_Account:	ExternalKey__c	SF_ERP_Salesforce_Clone_ttccom1401000, SF_ERP_Salesforce_Clone_ttsctm3001001
vw_INFORSXE_SalesOrderHeader	insert + update	vw_INFORSXE_SalesOrderHeader:	vw_INFORSXE_Account:, vw_INFORSXE_Customer:, vw_INFORSXE_Salesperson:	ExternalKey	SF_ERP_Salesforce_Clone_oeeh, SF_ERP_Salesforce_Clone_arsc, CommercientFlags
vw_INFORSXE_SalesOrderLine	insert + update	vw_INFORSXE_SalesOrderLine:	vw_INFORSXE_SalesOrderHeader:, vw_INFORSXE_ItemMaster:	ExternalKey	SF_ERP_Salesforce_Clone_oeel, SF_ERP_Salesforce_Clone_oeeh
vw_INFORSXE_InvoiceHeader	insert + update	vw_INFORSXE_InvoiceHeader:	vw_INFORSXE_Account:, vw_INFORSXE_Customer:	ExternalKey	SF_ERP_Salesforce_Clone_aret, CommercientFlags
vw_INFORSXE_InvoiceLineItem	insert + update	vw_INFORSXE_InvoiceLineItem:	vw_INFORSXE_InvoiceHeader:, vw_INFORSXE_ItemMaster:, vw_INFORSXE_Product:	ExternalKey	SF_ERP_Salesforce_Clone_oeel, SF_ERP_Salesforce_Clone_oeeh, SF_ERP_Salesforce_Clone_aret

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

• 1 — Get Users, SYNC SALESPERSON
• 2 — SYNC ACCOUNT
• 3 — SYNC CUSTOMER
• 4 — SYNC CUSTOMERTOACCOUNTLOOKUP
• 5 — SYNC STANDARD CONTACT
• 10 — Order Headers
• 11 — Order Details
• 12 — SYNC INVOICEHEADER
• 13 — SYNC INVOICELINEITEM

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_INFORSXE_Account reads vw_INFORSXE_Salesperson:, vw_INFORSXE_User:
• vw_INFORSXE_CustomerToAccountLookup reads vw_INFORSXE_Customer:
• vw_INFOR10DISTRIBUTIONBUSINESS_StandardContact reads vw_INFOR10DISTRIBUTIONBUSINESS_Account:; no template in this set writes vw_INFOR10DISTRIBUTIONBUSINESS_Account:
• vw_INFORSXE_Customer reads vw_INFORSXE_Account:, vw_INFORSXE_Salesperson:
• vw_INFORSXE_InvoiceHeader reads vw_INFORSXE_Account:, vw_INFORSXE_Customer:
• vw_INFORSXE_InvoiceLineItem reads vw_INFORSXE_InvoiceHeader:, vw_INFORSXE_ItemMaster:, vw_INFORSXE_Product:; no template in this set writes vw_INFORSXE_ItemMaster:, vw_INFORSXE_Product:
• vw_INFORSXE_SalesOrderHeader reads vw_INFORSXE_Account:, vw_INFORSXE_Customer:, vw_INFORSXE_Salesperson:
• vw_INFORSXE_SalesOrderLine reads vw_INFORSXE_SalesOrderHeader:, vw_INFORSXE_ItemMaster:; no template in this set writes vw_INFORSXE_ItemMaster:

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
SYNC SALESPERSON	CommercientSF18__smsn__c	71	cono → CommercientSF18__cono__c, slsrep → CommercientSF18__slsrep__c, addr → CommercientSF18__addr__c, city → CommercientSF18__city__c, state → CommercientSF18__state__c
SYNC ACCOUNT	Account	19	CommercientSFommercient_ArCustomerCode → CommercientSF__Commercient_ArCustomerCode__c, CommercientSF18__INFORSXE_Salesperson → CommercientSF18__INFORSXE_Salesperson__c, OwnerID → OwnerID, Phone → Phone, BillingStreet → BillingStreet
SYNC CUSTOMER	CommercientSF18__arsc__c	294	cono → CommercientSF18__cono__c, custno → CommercientSF18__custno__c, addr → CommercientSF18__addr__c, city → CommercientSF18__city__c, state → CommercientSF18__state__c
SYNC CUSTOMERTOACCOUNTLOOKUP	Account	2	CommercientSFommercient_ArCustomerCode → CommercientSF__Commercient_ArCustomerCode__c, CommercientSF18__INFORSXE_Customer → CommercientSF18__INFORSXE_Customer__c
SYNC STANDARD CONTACT	Contact	7	Title → Title, FirstName → FirstName, LastName → LastName, Phone → Phone, Email → Email
Order Headers	CommercientSF18__oeeh__c	304	Account → Account, INFORSXE_Customer → CommercientSF18__INFORSXE_Customer__c, INFORSXE_Salesperson → CommercientSF18__INFORSXE_Salesperson__c, orderno → CommercientSF18__orderno__c, ordersuf → CommercientSF18__ordersuf__c
Order Details	CommercientSF18__oeel__c	245	INFORSXE_Sales_Order_Header → CommercientSF18__INFORSXE_Sales_Order_Header__c, INFORSXE_Item_Master → CommercientSF18__INFORSXE_Item_Master__c, Product → Product__c, Opportunity → Opportunity__c, orderno → CommercientSF18__orderno__c
SYNC INVOICEHEADER	CommercientSF18__aret_InvoiceHeader__c	79	cono → CommercientSF18__cono__c, custno → CommercientSF18__custno__c, statustype → CommercientSF18__statustype__c, invno → CommercientSF18__invno__c, invsuf → CommercientSF18__invsuf__c
SYNC INVOICELINEITEM	CommercientSF18__oeel_InvoiceDetail__c	200	INFORSXE_Invoice_Header → CommercientSF18__INFORSXE_Invoice_Header__c, INFORSXE_Item_Master → CommercientSF18__INFORSXE_Item_Master__c, Product → CommercientSF18__Product__c, advertisingcode → advertisingcode, altwhse → CommercientSF18__altwhse__c

6. Community templates

The catalogue carries 43 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: 43
• Default operations: insert on 43, update on 43, delete on 43
• Marked circular-sync: 0
• Licence groups they span: 12
• Destination objects: Account, Product2, Opportunity, CommercientSF18__oeeh__c, OpportunityLineItem, PricebookEntry, CommercientSF14__BAAN_CUSTOMER__c, CommercientSF14__BAAN_CUSTOMERADDRESS__c, CommercientSF14__BAAN_INVOICEDETAIL__c, CommercientSF14__BAAN_INVOICEHEADER__c, CommercientSF14__BAAN_ITEM__c, CommercientSF14__BAAN_SALESORDERDETAIL__c, CommercientSF14__BAAN_SALESORDERHEADER__c, CommercientSF18__aret_InvoiceHeader__c, CommercientSF18__arsc__c, CommercientSF18__oeel__c, CommercientSF18__oeel_InvoiceDetail__c, CommercientSF18__QUOTEHEADER__c, CommercientSF18__smsn__c, CommercientSF18_INFORSXE_Quote__c, 4 more and 8 custom objects
• Object display names: SYNC ACCOUNT, SYNC CUSTOMER, SYNC CUSTOMERTOACCOUNTLOOKUP, SYNC INVOICEHEADER, SYNC ITEM, SYNC ITEMTOPRODUCTLOOKUP, SYNC PRODUCT, Get Users, INFORSXE QuoteHeader, INFORSXE QuoteLine, Opportunity Header, Opportunity HeaderUpdate, 20 more and 4 further templates
• Template groups: Account, Product, CRM Opportunity and Line, Invoice, Salesorder, Opportunity, 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_INFORSXE_User
• vw_INFORSXE_Account
• vw_INFORSXE_CustomerToAccountLookup
• vw_INFOR10DISTRIBUTIONBUSINESS_StandardContact
• vw_INFORSXE_Customer
• vw_INFORSXE_InvoiceHeader
• vw_INFORSXE_InvoiceLineItem
• vw_INFORSXE_SalesOrderHeader
• vw_INFORSXE_SalesOrderLine
• vw_INFORSXE_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 Infor10 Distribution Business → 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.