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

CRMPro → Salesforce — Infor M3 QM: 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-qm.md, and that skill’s ERP table is what points at it. What follows is only what the shipped Infor M3 QM → 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, CommercientSF18__custsf__c, CommercientSF18__rep__c	SF_ERP_Salesforce_Clone_cust, SF_ERP_Salesforce_Clone_cust_address, SF_ERP_Salesforce_Clone_ship, SF_ERP_Salesforce_Clone_so, SF_ERP_Salesforce_Clone_shipsf_ship_to_address, SF_ERP_Salesforce_Clone_cust_rep
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.	CommercientSF18__shipsf__c	SF_ERP_Salesforce_Clone_ship, SF_ERP_Salesforce_Clone_so
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__arsf__c, CommercientSF18__arsf_li__c	SF_ERP_Salesforce_Clone_ar, CommercientFlags, SF_ERP_Salesforce_Clone_ar_li
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__sosf__c, CommercientSF18__sosf_lis__c	SF_ERP_Salesforce_Clone_so, CommercientFlags, SF_ERP_Salesforce_Clone_so_lis

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 Salesforce Users	User	CommercientSF6__SalespersonCode__c	0	vw_INFORM3QM_GetSalesforceUser	1=0	'' / ''	1
INFORM3QM Salesperson	CommercientSF18__rep__c	CommercientSF18__ExternalKey__c	1	vw_INFORM3QM_Salesperson	vw_INFORM3QM_Salesperson	CommercientSF18__ / __c	1
Account	Account	CommercientSF__Commercient_ArCustomerCode__c	2	vw_INFORM3QM_Account	vw_INFORM3QM_Account	'' / ''	1
INFORM3QM Customer	CommercientSF18__custsf__c	CommercientSF18__ExternalKey__c	3	vw_INFORM3QM_Customer	vw_INFORM3QM_Customer	CommercientSF18__ / __c	1
INFORM3QM CustomerToAccountLookup	Account	CommercientSF__Commercient_ArCustomerCode__c	4	vw_INFORM3QM_CustomerToAccountLookup	vw_INFORM3QM_CustomerToAccountLookup	'' / ''	1
INFORM3QM ShipTo	CommercientSF18__shipsf__c	CommercientSF18__ExternalKey__c	5	vw_INFORM3QM_ShipTo	vw_INFORM3QM_ShipTo	CommercientSF18__ / __c	1
INFORM3QM SalesOrderHeader	CommercientSF18__sosf__c	CommercientSF18__ExternalKey__c	6	vw_INFORM3QM_SalesOrderHeader	vw_INFORM3QM_SalesOrderHeader	CommercientSF18__ / __c	1
INFORM3QM SalesOrderLine	CommercientSF18__sosf_lis__c	CommercientSF18__ExternalKey__c	7	vw_INFORM3QM_SalesOrderLine	vw_INFORM3QM_SalesOrderLine	CommercientSF18__ / __c	1
INFORM3QM InvoiceHeader	CommercientSF18__arsf__c	CommercientSF18__ExternalKey__c	8	vw_INFORM3QM_InvoiceHeader	vw_INFORM3QM_InvoiceHeader	CommercientSF18__ / __c	1
INFORM3QM InvoiceLine	CommercientSF18__arsf_li__c	CommercientSF18__ExternalKey__c	9	vw_INFORM3QM_InvoiceLine	vw_INFORM3QM_InvoiceLine	CommercientSF18__ / __c	1
Contact	Contact	ExternalKey__c	10	vw_INFORM3QM_Contact	vw_INFORM3QM_Contact	'' / ''	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 Account, Get Salesforce 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_INFORM3QM_Salesperson	insert + update	vw_INFORM3QM_Salesperson:	—	ExternalKey	SF_ERP_Salesforce_Clone_rep
vw_INFORM3QM_Account	insert + update	vw_INFORM3QM_Account:	vw_INFORM3QM_Salesperson:, vw_EPICORP21_GetSalesforceUser:	—	SF_ERP_Salesforce_Clone_cust, SF_ERP_Salesforce_Clone_cust_address, SF_ERP_Salesforce_Clone_ship, SF_ERP_Salesforce_Clone_so, SF_ERP_Salesforce_Clone_shipsf_ship_to_address
vw_INFORM3QM_Customer	insert + update	vw_INFORM3QM_Customer:	vw_INFORM3QM_Account:	ExternalKey	SF_ERP_Salesforce_Clone_cust
vw_INFORM3QM_CustomerToAccountLookup	insert + update	vw_INFORM3QM_CustomerToAccountLookup:	vw_INFORM3QM_Account:, vw_INFORM3QM_Customer:	—	SF_ERP_Salesforce_Clone_cust
vw_INFORM3QM_ShipTo	insert + update	vw_INFORM3QM_ShipTo:	vw_INFORM3QM_Account:, vw_INFORM3QM_Customer:	ExternalKey	SF_ERP_Salesforce_Clone_ship, SF_ERP_Salesforce_Clone_so
vw_INFORM3QM_SalesOrderHeader	insert + update	vw_INFORM3QM_SalesOrderHeader:	vw_INFORM3QM_Account:, vw_INFORM3QM_Customer:	ExternalKey	SF_ERP_Salesforce_Clone_so, CommercientFlags
vw_INFORM3QM_SalesOrderLine	insert + update	vw_INFORM3QM_SalesOrderLine:	vw_INFORM3QM_SalesOrderHeader:	ExternalKey	SF_ERP_Salesforce_Clone_so_lis
vw_INFORM3QM_InvoiceHeader	insert + update	vw_INFORM3QM_InvoiceHeader:	vw_INFORM3QM_Account:, vw_INFORM3QM_Customer:	ExternalKey	SF_ERP_Salesforce_Clone_ar, CommercientFlags
vw_INFORM3QM_InvoiceLine	insert + update	vw_INFORM3QM_InvoiceLine:	vw_INFORM3QM_InvoiceHeader:	ExternalKey	SF_ERP_Salesforce_Clone_ar_li
vw_INFORM3QM_Contact	insert + update	vw_INFORM3QM_Contact:	vw_INFORM3QM_Account:	ExternalKey__c	SF_ERP_Salesforce_Clone_contact, SF_ERP_Salesforce_Clone_contact_address, SF_ERP_Salesforce_Clone_cust_contact_id

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

• 0 — Get Salesforce Users
• 1 — INFORM3QM Salesperson
• 2 — Account
• 3 — INFORM3QM Customer
• 4 — INFORM3QM CustomerToAccountLookup
• 5 — INFORM3QM ShipTo
• 6 — INFORM3QM SalesOrderHeader
• 7 — INFORM3QM SalesOrderLine
• 8 — INFORM3QM InvoiceHeader
• 9 — INFORM3QM InvoiceLine
• 10 — Contact

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_INFORM3QM_Account reads vw_INFORM3QM_Salesperson:, vw_EPICORP21_GetSalesforceUser:; no template in this set writes vw_EPICORP21_GetSalesforceUser:
• vw_INFORM3QM_CustomerToAccountLookup reads vw_INFORM3QM_Account:, vw_INFORM3QM_Customer:
• vw_INFORM3QM_Contact reads vw_INFORM3QM_Account:
• vw_INFORM3QM_Customer reads vw_INFORM3QM_Account:
• vw_INFORM3QM_ShipTo reads vw_INFORM3QM_Account:, vw_INFORM3QM_Customer:
• vw_INFORM3QM_InvoiceHeader reads vw_INFORM3QM_Account:, vw_INFORM3QM_Customer:
• vw_INFORM3QM_InvoiceLine reads vw_INFORM3QM_InvoiceHeader:
• vw_INFORM3QM_SalesOrderHeader reads vw_INFORM3QM_Account:, vw_INFORM3QM_Customer:
• vw_INFORM3QM_SalesOrderLine reads vw_INFORM3QM_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
INFORM3QM Salesperson	CommercientSF18__rep__c	17	rep_id → CommercientSF18__rep_id__c, address → CommercientSF18__address__c, phone → CommercientSF18__phone__c, terr → CommercientSF18__terr__c, comm → CommercientSF18__comm__c
Account	Account	10	CommercientSFommercient_ArCustomerCode → CommercientSF__Commercient_ArCustomerCode__c, Phone → Phone, BillingStreet → BillingStreet, BillingCity → BillingCity, BillingState → BillingState
INFORM3QM Customer	CommercientSF18__custsf__c	41	Account → Account, cust_id → CommercientSF18__cust_id__c, phone → CommercientSF18__phone__c, bill_to → CommercientSF18__bill_to__c, ship_via → CommercientSF18__ship_via__c
INFORM3QM CustomerToAccountLookup	Account	2	CommercientSFommercient_ArCustomerCode → CommercientSF__Commercient_ArCustomerCode__c, CommercientSF18__Infor_M3_QM_Customer → CommercientSF18__Infor_M3_QM_Customer__c
INFORM3QM ShipTo	CommercientSF18__shipsf__c	46	Account → Account, custsf → CommercientSF18__custsf__c, date → CommercientSF18__date__c, type → CommercientSF18__type__c, via → CommercientSF18__via__c
INFORM3QM SalesOrderHeader	CommercientSF18__sosf__c	71	Account → Account, custsf → CommercientSF18__custsf__c, date → CommercientSF18__date__c, sold_to → CommercientSF18__sold_to__c, book_date → CommercientSF18__book_date__c
INFORM3QM SalesOrderLine	CommercientSF18__sosf_lis__c	41	sosf → CommercientSF18__sosf__c, parent_key → CommercientSF18__parent_key__c, so_id → CommercientSF18__so_id__c, item_val → CommercientSF18__item_val__c, lis → CommercientSF18__lis__c
INFORM3QM InvoiceHeader	CommercientSF18__arsf__c	47	Account → Account, custsf → CommercientSF18__custsf__c, cust → CommercientSF18__cust__c, po → CommercientSF18__po__c, source_doc → source_doc
INFORM3QM InvoiceLine	CommercientSF18__arsf_li__c	18	arsf → CommercientSF18__arsf__c, parent_key → CommercientSF18__parent_key__c, ar_id → CommercientSF18__ar_id__c, item_val → CommercientSF18__item_val__c, li → CommercientSF18__li__c
Contact	Contact	10	AccountID → AccountID, FirstName → FirstName, LastName → LastName, Title → Title, Fax → Fax

6. Community templates

The catalogue carries 11 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: 11
• Default operations: insert on 11, update on 11, delete on 11
• Marked circular-sync: 0
• Licence groups they span: 8
• Destination objects: Account, CommercientSF18__arsf__c, CommercientSF18__arsf_li__c, CommercientSF18__custsf__c, CommercientSF18__rep__c, CommercientSF18__shipsf__c, CommercientSF18__sosf__c, CommercientSF18__sosf_lis__c, Contact, User
• Object display names: Account, Contact, Get Salesforce Users, INFORM3QM Customer, INFORM3QM CustomerToAccountLookup, INFORM3QM InvoiceHeader, INFORM3QM InvoiceLine, INFORM3QM SalesOrderHeader, INFORM3QM SalesOrderLine, INFORM3QM Salesperson, INFORM3QM ShipTo
• 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_INFORM3QM_Account
• vw_INFORM3QM_CustomerToAccountLookup
• vw_INFORM3QM_Contact
• vw_INFORM3QM_GetSalesforceUser
• vw_INFORM3QM_Customer
• vw_INFORM3QM_ShipTo
• vw_INFORM3QM_InvoiceHeader
• vw_INFORM3QM_InvoiceLine
• vw_INFORM3QM_SalesOrderHeader
• vw_INFORM3QM_SalesOrderLine
• vw_INFORM3QM_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 QM → 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.