CRMPro → Salesforce — Infor M3: what the shipped templates set up

CRMPro → Salesforce — Infor M3: 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/infor-m3.md, and that skill’s ERP table is what points at it. What follows is only what the shipped Infor M3 → 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
INFORM3 ShipToAddress	The templates push CommercientSF18_OCUSAD_ShipAdd__c to Salesforce. New records are created and existing ones updated; none are deleted.	CommercientSF18_OCUSAD_ShipAdd__c	SF_ERP_Salesforce_Clone_OCUSAD
Product	The templates push Product2 to Salesforce. New records are created and existing ones updated; none are deleted.	Product2	SF_ERP_Salesforce_Clone_MITMAS
INFORM3 ItemMaster	The templates push CommercientSF18__MITMAS__c to Salesforce. New records are created and existing ones updated; none are deleted.	CommercientSF18__MITMAS__c	SF_ERP_Salesforce_Clone_MITMAS
INFORM3 ItemWarehouse	The templates push CommercientSF18__MITBAL__c to Salesforce. New records are created and existing ones updated; none are deleted.	CommercientSF18__MITBAL__c	SF_ERP_Salesforce_Clone_MITBAL
Product to Item Master Reverse Lookup	The templates push Product2 to Salesforce. New records are created and existing ones updated; none are deleted.	Product2	SF_ERP_Salesforce_Clone_MITMAS
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 and existing ones updated; none are deleted.	Account, Contact, CommercientSF18__OCUSMA__c, CommercientSF18_CSYTAB__c	SF_ERP_Salesforce_Clone_OCUSMA, SF_ERP_Salesforce_Clone_CSYTAB
CRM Ownership	The templates push user to Salesforce. New records are created and existing ones updated; none are deleted.	user	—
Invoice History Headers	The Invoices from the ERP invoice module are synchronized to the Commercient Invoice Header (MCO) object in CRM. Customer service and sales people can visualize the status of the Invoice such as open, closed, as well as the balance remaining and the due date. New records are created and existing ones updated; none are deleted.	CommercientSF18__OINVOH__c	SF_ERP_Salesforce_Clone_OINVOH, CommercientFlags
Open AR Invoice Header	The detail lines on open invoices are visible too so that you are aware of what items you are awaiting payment on from your customer. New records are created and existing ones updated; none are deleted.	CommercientSF18__OINVOL__c	SF_ERP_Salesforce_Clone_OINVOL, SF_ERP_Salesforce_Clone_OINVOH
Salesorder	The templates push CommercientSF18__OOLINE__c, CommercientSF18__OOHEAD__c to Salesforce. New records are created and existing ones updated; none are deleted.	CommercientSF18__OOLINE__c, CommercientSF18__OOHEAD__c	SF_ERP_Salesforce_Clone_OOLINE, SF_ERP_Salesforce_Clone_OOHEAD, CommercientFlags

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
INFORM3 Salesperson	CommercientSF18_CSYTAB__c	ExternalKey__c	1	vw_INFORM3_Salesperson	vw_INFORM3_Salesperson	'' / __c	1
Account	Account	CommercientSF__Commercient_ArCustomerCode__c	2	vw_INFORM3_Account	vw_INFORM3_Account	'' / ''	1
INFORM3 Customer	CommercientSF18__OCUSMA__c	CommercientSF18__ExternalKey__c	3	vw_INFORM3_Customer	vw_INFORM3_Customer	CommercientSF18__ / __c	1
INFORM3 CustomerToAccountLookup	Account	CommercientSF__Commercient_ArCustomerCode__c	4	vw_INFORM3_CustomerToAccountLookup	vw_INFORM3_CustomerToAccountLookup	'' / ''	1
INFORM3 ShipToAddress	CommercientSF18_OCUSAD_ShipAdd__c	ExternalKey__c	5	vw_INFORM3_Ship_Address	vw_INFORM3_Ship_Address	'' / __c	1
INFORM3 SalesOrderHeader	CommercientSF18__OOHEAD__c	CommercientSF18__ExternalKey__c	6	vw_INFORM3_SalesOrderHeader	vw_INFORM3_SalesOrderHeader	CommercientSF18__ / __c	1
INFORM3 SalesOrderLine	CommercientSF18__OOLINE__c	CommercientSF18__ExternalKey__c	7	vw_INFORM3_SalesOrderDetail	vw_INFORM3_SalesOrderDetail	CommercientSF18__ / __c	1
INFORM3 InvoiceHeader	CommercientSF18__OINVOH__c	CommercientSF18__ExternalKey__c	8	vw_INFORM3_InvoiceHeader	vw_INFORM3_InvoiceHeader	CommercientSF18__ / __c	1
INFORM3 InvoiceLine	CommercientSF18__OINVOL__c	CommercientSF18__ExternalKey__c	9	vw_INFORM3_InvoiceDetail	vw_INFORM3_InvoiceDetail	CommercientSF18__ / __c	1
Contact	Contact	ExternalKey__c	10	vw_INFORM3_Contact	vw_INFORM3_Contact	'' / ''	1
Product	Product2	CommercientSF__ExternalKey__c	11	vw_INFORM3_Product	vw_INFORM3_Product	'' / ''	1
INFORM3 ItemMaster	CommercientSF18__MITMAS__c	CommercientSF18__ExternalKey__c	12	vw_INFORM3_ItemMaster	vw_INFORM3_ItemMaster	CommercientSF18__ / __c	1
INFORM3 ItemWarehouse	CommercientSF18__MITBAL__c	CommercientSF18__ExternalKey__c	13	vw_INFORM3_ItemWareHouse	vw_INFORM3_ItemWareHouse	CommercientSF18__ / __c	1
Product to Item Master Reverse Lookup	Product2	CommercientSF__ExternalKey__c	17	vw_INFORM3_ProductToItemReverseLookup	vw_INFORM3_ProductToItemReverseLookup	'' / ''	1
Get Users	user	AU_Sales_Rep_No__c	20	vw_INFORM3_User	Select 1 = 0	'' / ''	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 '', 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 Product, Account, Contact, 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_INFORM3_Salesperson	insert + update	vw_INFORM3_Salesperson:	—	ExternalKey	SF_ERP_Salesforce_Clone_CSYTAB
vw_INFORM3_Account	insert + update	vw_INFORM3_Account:	vw_INFORM3_Salesperson:, vw_INFORM3_User:	—	SF_ERP_Salesforce_Clone_OCUSMA
vw_INFORM3_Customer	insert + update	vw_INFORM3_Customer:	vw_INFORM3_Account:, vw_INFORM3_Salesperson:	—	SF_ERP_Salesforce_Clone_OCUSMA
vw_INFORM3_CustomerToAccountLookup	insert + update	vw_INFORM3_CustomerToAccountLookup:	vw_INFORM3_Customer:	—	SF_ERP_Salesforce_Clone_OCUSMA
vw_INFORM3_Ship_Address	insert + update	vw_INFORM3_Ship_Address:	vw_INFORM3_Account:, vw_INFORM3_Customer:	ExternalKey	SF_ERP_Salesforce_Clone_OCUSAD
vw_INFORM3_SalesOrderHeader	insert + update	vw_INFORM3_SalesOrderHeader:	vw_INFORM3_Account:, vw_INFORM3_Customer:, vw_INFORM3_Salesperson:	ExternalKey	SF_ERP_Salesforce_Clone_OOHEAD, CommercientFlags
vw_INFORM3_SalesOrderDetail	insert + update	vw_INFORM3_SalesOrderDetail:	vw_INFORM3_SalesOrderHeader:	ExternalKey	SF_ERP_Salesforce_Clone_OOLINE
vw_INFORM3_InvoiceHeader	insert + update	vw_INFORM3_InvoiceHeader:	vw_INFORM3_Account:, vw_INFORM3_Customer:	ExternalKey	SF_ERP_Salesforce_Clone_OINVOH, CommercientFlags
vw_INFORM3_InvoiceDetail	insert + update	vw_INFORM3_InvoiceDetail:	vw_INFORM3_InvoiceHeader:	ExternalKey	SF_ERP_Salesforce_Clone_OINVOL, SF_ERP_Salesforce_Clone_OINVOH
vw_INFORM3_Product	insert + update	vw_INFORM3_Product:	—	—	SF_ERP_Salesforce_Clone_MITMAS
vw_INFORM3_ItemMaster	insert + update	vw_INFORM3_ItemMaster:	vw_INFORM3_Product:	—	SF_ERP_Salesforce_Clone_MITMAS
vw_INFORM3_ItemWareHouse	insert-only	vw_INFORM3_ItemWareHouse:	vw_INFORM3_Product:, vw_INFORM3_ItemMaster:	ExternalKey	SF_ERP_Salesforce_Clone_MITBAL
vw_INFORM3_ProductToItemReverseLookup	insert + update	vw_INFORM3_ProductToItemReverseLookup:	vw_INFORM3_ItemMaster:	—	SF_ERP_Salesforce_Clone_MITMAS

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

• 1 — INFORM3 Salesperson
• 2 — Account
• 3 — INFORM3 Customer
• 4 — INFORM3 CustomerToAccountLookup
• 5 — INFORM3 ShipToAddress
• 6 — INFORM3 SalesOrderHeader
• 7 — INFORM3 SalesOrderLine
• 8 — INFORM3 InvoiceHeader
• 9 — INFORM3 InvoiceLine
• 10 — Contact
• 11 — Product
• 12 — INFORM3 ItemMaster
• 13 — INFORM3 ItemWarehouse
• 17 — Product to Item Master Reverse Lookup
• 20 — Get Users

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_INFORM3_Ship_Address reads vw_INFORM3_Account:, vw_INFORM3_Customer:
• vw_INFORM3_ItemMaster reads vw_INFORM3_Product:
• vw_INFORM3_ItemWareHouse reads vw_INFORM3_Product:, vw_INFORM3_ItemMaster:
• vw_INFORM3_ProductToItemReverseLookup reads vw_INFORM3_ItemMaster:
• vw_INFORM3_Account reads vw_INFORM3_Salesperson:, vw_INFORM3_User:
• vw_INFORM3_CustomerToAccountLookup reads vw_INFORM3_Customer:
• vw_INFORM3_Customer reads vw_INFORM3_Account:, vw_INFORM3_Salesperson:
• vw_INFORM3_InvoiceHeader reads vw_INFORM3_Account:, vw_INFORM3_Customer:
• vw_INFORM3_InvoiceDetail reads vw_INFORM3_InvoiceHeader:
• vw_INFORM3_SalesOrderDetail reads vw_INFORM3_SalesOrderHeader:
• vw_INFORM3_SalesOrderHeader reads vw_INFORM3_Account:, vw_INFORM3_Customer:, vw_INFORM3_Salesperson:

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
INFORM3 Salesperson	CommercientSF18_CSYTAB__c	16	CTCONO, CTSTCO, CTSTKY → ExternalKey__c, CTTX40 → Name, CTCONO → CTCONO__c, CTDIVI → CTDIVI__c, CTSTCO → CTSTCO__c
Account	Account	15	OKCONO, OKCUNO → CommercientSF__Commercient_ArCustomerCode__c, OKCUNM → Name, OKPHNO → Phone, OKCUA1, OKCUA2, OKCUA3 → BillingStreet, OKTOWN → BillingCity
INFORM3 Customer	CommercientSF18__OCUSMA__c	110	OKCONO, OKCUNO → CommercientSF18__ExternalKey__c, OKCUNM → Name, SFDCID → Account, OKCUA1 → OKCUA1, OKCUA2 → OKCUA2
INFORM3 CustomerToAccountLookup	Account	2	OKCONO, OKCUNO → CommercientSF__Commercient_ArCustomerCode__c, SFDCID → CommercientSF18__INFORM3_Customer__c
INFORM3 ShipToAddress	CommercientSF18_OCUSAD_ShipAdd__c	63	OPCONO, OPCUNO, OPADRT, OPADID → ExternalKey__c, OPCONO, OPCUNO, OPADRT, OPADID → Name, OPCONO, OPCUNO → Account, OPCONO, OPCUNO → INFORM3_Customer__c, OPLMDT → OPLMDT
INFORM3 SalesOrderHeader	CommercientSF18__OOHEAD__c	97	OACONO, OAORNO → CommercientSF18__ExternalKey__c, OACONO, OAORNO → CommercientSF18__Name__c, OACONO, OACUNO → Account, OACONO, OACUNO → INFORM3_Customer, OALMDT → CommercientSF18__OALMDT_Date__c
INFORM3 SalesOrderLine	CommercientSF18__OOLINE__c	33	OBCONO, OBORNO, OBPONR, OBPOSX → CommercientSF18__ExternalKey__c, OBCONO, OBORNO, OBPONR, OBPOSX → Name, SFDCID → CommercientSF18__Sales_Order_Header__c, OBLMDT → OBLMDT, OBCODT → OBCODT
INFORM3 InvoiceHeader	CommercientSF18__OINVOH__c	53	UHCONO, UHDIVI, UHIVNO, UHYEA4 → CommercientSF18__ExternalKey__c, UHCONO, UHDIVI, UHIVNO, UHYEA4 → Name, UHCONO, UHPYNO → CommercientSF18__Account__c, UHCONO, UHPYNO → CommercientSF18__INFORM3_Customer__c, UHRGDT → CommercientSF18__UHRGDT_Date__c
INFORM3 InvoiceLine	CommercientSF18__OINVOL__c	41	SFDCID → CommercientSF18__INFORM3_Sales_Invoice_Header__c, ONLMDT → CommercientSF18__ONLMDT_Date__c, ONRGDT → CommercientSF18__ONRGDT_Date__c, ONRGTM → CommercientSF18__Entry_Time__c, ONLMDT → CommercientSF18__ONLMDT__c
Contact	Contact	1	ExternalKey__c → ExternalKey__c
Product	Product2	5	MMCONO, MMITNO → CommercientSF__ExternalKey__c, IsActive → IsActive, MMITDS → Name, MMITNO → ProductCode, MMFUDS → Description
INFORM3 ItemMaster	CommercientSF18__MITMAS__c	208	MMCONO, MMITNO → CommercientSF18__ExternalKey__c, MMITDS → Name, MMCONO → CommercientSF18__MMCONO__c, MMSTAT → CommercientSF18__MMSTAT__c, MMITNO → CommercientSF18__MMITNO__c
INFORM3 ItemWarehouse	CommercientSF18__MITBAL__c	152	MBCONO, MBITNO, MBWHLO → CommercientSF18__ExternalKey__c, MBCONO, MBITNO, MBWHLO → Name, MBCONO → MBCONO, MBWHLO → MBWHLO, MBITNO → MBITNO
Product to Item Master Reverse Lookup	Product2	2	MMCONO, MMITNO → CommercientSF__ExternalKey__c, SFDCID → CommercientSF18__INFORM3_Item_Master__c
Get Users	user	1	—

6. Community templates

The catalogue carries 18 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: 18
• Default operations: insert on 18, update on 18, delete on 18
• Marked circular-sync: 0
• Licence groups they span: 11
• Destination objects: Account, Product2, user, CommercientSF18__MITBAL__c, CommercientSF18__MITMAS__c, CommercientSF18__OCUSMA__c, CommercientSF18__OINVOH__c, CommercientSF18__OINVOL__c, CommercientSF18__OOHEAD__c, CommercientSF18__OOLINE__c, CommercientSF18_CSYTAB__c, CommercientSF18_OCUSAD_ShipAdd__c, Contact, Location, ProductItem
• Object display names: Get Users, Account, Contact, Get Location, INFORM3 Customer, INFORM3 CustomerToAccountLookup, INFORM3 InvoiceHeader, INFORM3 InvoiceLine, INFORM3 ItemMaster, INFORM3 ItemWarehouse, INFORM3 SalesOrderHeader, INFORM3 SalesOrderLine and 5 more
• Template groups: Account, Product, Invoice, Salesorder, CRM Ownership, 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_INFORM3_Ship_Address
• vw_INFORM3_Product
• vw_INFORM3_ItemMaster
• vw_INFORM3_ItemWareHouse
• vw_INFORM3_ProductToItemReverseLookup
• vw_INFORM3_Account
• vw_INFORM3_CustomerToAccountLookup
• vw_INFORM3_Contact
• vw_INFORM3_User
• vw_INFORM3_Customer
• vw_INFORM3_InvoiceHeader
• vw_INFORM3_InvoiceDetail
• vw_INFORM3_SalesOrderDetail
• vw_INFORM3_SalesOrderHeader
• vw_INFORM3_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 Infor M3 → 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.