CRMPro → Salesforce — IQMS: what the shipped templates set up

CRMPro → Salesforce — IQMS: 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/iqms.md, and that skill’s ERP table is what points at it. What follows is only what the shipped IQMS → 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, Commercient31__ARCUSTO__c, Commercient31__SALESPEOPLE__c	SF_ERP_Salesforce_Clone_ARCUSTO, SF_ERP_Salesforce_Clone_SHIP_TO, SF_ERP_Salesforce_Clone_CONTACT, SF_ERP_Salesforce_Clone_SALESPEOPLE
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.	Commercient31__SHIP_TO__c	SF_ERP_Salesforce_Clone_SHIP_TO
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.	Commercient31__ARINVOICE__c, Commercient31__ARINVOICE_DETAIL__c	SF_ERP_Salesforce_Clone_ARINVOICE, CommercientFlags, SF_ERP_Salesforce_Clone_ARINVOICE_DETAIL
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.	Commercient31__ORD_DETAIL__c, Commercient31__HIST_ORDERS__c, Commercient31__HIST_ORD_DETAIL__c	SF_ERP_Salesforce_Clone_ORD_DETAIL, SF_ERP_Salesforce_Clone_HIST_ORDERS, CommercientFlags, SF_ERP_Salesforce_Clone_HIST_ORD_DETAIL

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	—	0	vw_IQMS_User	1=0	'' / ''	1
IQMS SalesPerson	Commercient31__SALESPEOPLE__c	Commercient31__ExternalKey__c	2	vw_IQMS_SalesPerson	vw_IQMS_SalesPerson	Commercient31__ / __c	1
Account	Account	CommercientSF__Commercient_ArCustomerCode__c	4	vw_IQMS_Account	vw_IQMS_Account	'' / ''	1
IQMS Customer	Commercient31__ARCUSTO__c	Commercient31__ExternalKey__c	6	vw_IQMS_Customer	vw_IQMS_Customer	Commercient31__ / __c	1
IQMS CustomerToAccountLookup	Account	CommercientSF__Commercient_ArCustomerCode__c	7	vw_IQMS_CustomerToAccountLookup	vw_IQMS_CustomerToAccountLookup	'' / ''	1
IQMS ShipToAddress	Commercient31__SHIP_TO__c	Commercient31__ExternalKey__c	8	vw_IQMS_ShipToAddress	vw_IQMS_ShipToAddress	Commercient31__ / __c	1
IQMS SalesOrderDetail	Commercient31__ORD_DETAIL__c	Commercient31__ExternalKey__c	10	vw_IQMS_SalesOrderDetail	vw_IQMS_SalesOrderDetail	Commercient31__ / __c	1
IQMS SalesOrderHistoryHeader	Commercient31__HIST_ORDERS__c	Commercient31__ExternalKey__c	11	vw_IQMS_SalesOrderHistoryHeader	vw_IQMS_SalesOrderHistoryHeader	Commercient31__ / __c	1
IQMS SalesOrderHistoryDetail	Commercient31__HIST_ORD_DETAIL__c	Commercient31__ExternalKey__c	12	vw_IQMS_SalesOrderHistoryDetail	vw_IQMS_SalesOrderHistoryDetail	Commercient31__ / __c	1
IQMS InvoiceHeader	Commercient31__ARINVOICE__c	Commercient31__ExternalKey__c	13	vw_IQMS_InvoiceHeader	vw_IQMS_InvoiceHeader	Commercient31__ / __c	1
IQMS InvoiceDetail	Commercient31__ARINVOICE_DETAIL__c	Commercient31__ExternalKey__c	14	vw_IQMS_InvoiceDetail	vw_IQMS_InvoiceDetail	Commercient31__ / __c	1
Contact	Contact	ExternalKey__c	16	vw_IQMS_Contact	vw_IQMS_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 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_IQMS_SalesPerson	insert + update	vw_IQMS_SalesPerson:	—	ExternalKey	SF_ERP_Salesforce_Clone_SALESPEOPLE
vw_IQMS_Account	insert + update	vw_IQMS_Account:	vw_IQMS_Terms:, vw_IQMS_SalesPerson:, vw_IQMS_User:	—	SF_ERP_Salesforce_Clone_ARCUSTO, SF_ERP_Salesforce_Clone_SHIP_TO
vw_IQMS_Customer	insert + update	vw_IQMS_Customer:	vw_IQMS_Account:, vw_IQMS_SalesPerson:, vw_IQMS_Terms:	ExternalKey	SF_ERP_Salesforce_Clone_ARCUSTO
vw_IQMS_CustomerToAccountLookup	insert + update	vw_IQMS_CustomerToAccountLookup:	vw_IQMS_Customer:, vw_IQMS_Account:	—	SF_ERP_Salesforce_Clone_ARCUSTO
vw_IQMS_ShipToAddress	insert + update	vw_IQMS_ShipToAddress:	vw_IQMS_Account:, vw_IQMS_Customer:	ExternalKey	SF_ERP_Salesforce_Clone_SHIP_TO
vw_IQMS_SalesOrderDetail	insert + update	vw_IQMS_SalesOrderDetail:	vw_IQMS_SalesOrderHeader:	ExternalKey	SF_ERP_Salesforce_Clone_ORD_DETAIL
vw_IQMS_SalesOrderHistoryHeader	insert + update	vw_IQMS_SalesOrderHistoryHeader:	vw_IQMS_Account:, vw_IQMS_Customer:	ExternalKey	SF_ERP_Salesforce_Clone_HIST_ORDERS, CommercientFlags
vw_IQMS_SalesOrderHistoryDetail	insert + update	vw_IQMS_SalesOrderHistoryDetail:	vw_IQMS_SalesOrderHistoryHeader:	ExternalKey	SF_ERP_Salesforce_Clone_HIST_ORD_DETAIL
vw_IQMS_InvoiceHeader	insert + update	vw_IQMS_InvoiceHeader:	vw_IQMS_Account:, vw_IQMS_Customer:	ExternalKey	SF_ERP_Salesforce_Clone_ARINVOICE, CommercientFlags
vw_IQMS_InvoiceDetail	insert + update	vw_IQMS_InvoiceDetail:	vw_IQMS_InvoiceHeader:	ExternalKey	SF_ERP_Salesforce_Clone_ARINVOICE_DETAIL
vw_IQMS_Contact	insert + update	vw_IQMS_Contact:	vw_IQMS_Account:	ExternalKey__c	SF_ERP_Salesforce_Clone_CONTACT

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

• 0 — GET USERS
• 2 — IQMS SalesPerson
• 4 — Account
• 6 — IQMS Customer
• 7 — IQMS CustomerToAccountLookup
• 8 — IQMS ShipToAddress
• 10 — IQMS SalesOrderDetail
• 11 — IQMS SalesOrderHistoryHeader
• 12 — IQMS SalesOrderHistoryDetail
• 13 — IQMS InvoiceHeader
• 14 — IQMS InvoiceDetail
• 16 — 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_IQMS_Account reads vw_IQMS_Terms:, vw_IQMS_SalesPerson:, vw_IQMS_User:; no template in this set writes vw_IQMS_Terms:
• vw_IQMS_CustomerToAccountLookup reads vw_IQMS_Customer:, vw_IQMS_Account:
• vw_IQMS_Contact reads vw_IQMS_Account:
• vw_IQMS_Customer reads vw_IQMS_Account:, vw_IQMS_SalesPerson:, vw_IQMS_Terms:; no template in this set writes vw_IQMS_Terms:
• vw_IQMS_ShipToAddress reads vw_IQMS_Account:, vw_IQMS_Customer:
• vw_IQMS_InvoiceHeader reads vw_IQMS_Account:, vw_IQMS_Customer:
• vw_IQMS_InvoiceDetail reads vw_IQMS_InvoiceHeader:
• vw_IQMS_SalesOrderDetail reads vw_IQMS_SalesOrderHeader:; no template in this set writes vw_IQMS_SalesOrderHeader:
• vw_IQMS_SalesOrderHistoryHeader reads vw_IQMS_Account:, vw_IQMS_Customer:
• vw_IQMS_SalesOrderHistoryDetail reads vw_IQMS_SalesOrderHistoryHeader:

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
IQMS SalesPerson	Commercient31__SALESPEOPLE__c	16	ID → Commercient31__ID__c, EMPLOYEE_ID → Commercient31__EMPLOYEE_ID__c, SALES_CODE → SALES_CODE, FIRST_NAME → Commercient31__FIRST_NAME__c, LAST_NAME → Commercient31__LAST_NAME__c
Account	Account	16	CommercientSFommercient_ArCustomerCode → CommercientSF__Commercient_ArCustomerCode__c, Phone → Phone, BillingStreet → BillingStreet, BillingCity → BillingCity, BillingState → BillingState
IQMS Customer	Commercient31__ARCUSTO__c	178	Account → Account, IQMS_Salespeople → Commercient31__IQMS_Salespeople__c, IQMS_Term → Commercient31__IQMS_Term__c, ID → Commercient31__ID__c, TER_ID → Commercient31__TER_ID__c
IQMS CustomerToAccountLookup	Account	2	CommercientSFommercient_ArCustomerCode → CommercientSF__Commercient_ArCustomerCode__c, Commercient31__IQMS_AR_Customer → Commercient31__IQMS_AR_Customer__c
IQMS ShipToAddress	Commercient31__SHIP_TO__c	109	Account → Account, ARCusTo → ARCusTo, ID → Commercient31__ID__c, ARCUSTO_ID → ARCUSTO_ID, ATTN → Commercient31__ATTN__c
IQMS SalesOrderDetail	Commercient31__ORD_DETAIL__c	81	IQMS_Order_Header → Commercient31__IQMS_Order_Header__c, ID → Commercient31__ID__c, ORDERS_ID → Commercient31__ORDERS_ID__c, ARINVT_ID → Commercient31__ARINVT_ID__c, ORD_DET_SEQNO → Commercient31__ORD_DET_SEQNO__c
IQMS SalesOrderHistoryHeader	Commercient31__HIST_ORDERS__c	130	ID → Commercient31__ID__c, Account → Account, ARCusTo → ARCusTo, ORDERNO → Commercient31__ORDERNO__c, PONO → Commercient31__PONO__c
IQMS SalesOrderHistoryDetail	Commercient31__HIST_ORD_DETAIL__c	90	HIST_ORDERS → Commercient31__HIST_ORDERS__c, ID → Commercient31__ID__c, ORDERS_ID → Commercient31__ORDERS_ID__c, ARINVT_ID → Commercient31__ARINVT_ID__c, ORD_DET_SEQNO → Commercient31__ORD_DET_SEQNO__c
IQMS InvoiceHeader	Commercient31__ARINVOICE__c	92	Account → Account, ARCusTo → ARCusTo, ID → Commercient31__ID__c, GLACCT_ID_AR → GLACCT_ID_AR, ARCUSTO_ID → ARCUSTO_ID
IQMS InvoiceDetail	Commercient31__ARINVOICE_DETAIL__c	76	ARINVOICE → ARINVOICE, ID → Commercient31__ID__c, ARINVOICE_ID → ARINVOICE_ID, SHIPMENT_DTL_ID → Commercient31__SHIPMENT_DTL_ID__c, ORD_DETAIL_ID → Commercient31__ORD_DETAIL_ID__c
Contact	Contact	12	AccountID → AccountID, FirstName → FirstName, LastName → LastName, Email → Email, Phone → Phone

6. Community templates

The catalogue carries 47 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: 47
• Default operations: insert on 47, update on 47, delete on 47
• Marked circular-sync: 0
• Licence groups they span: 12
• Destination objects: Account, Commercient31__ARCUSTO__c, Commercient31__ARINVOICE__c, Commercient31__ARINVOICE_DETAIL__c, Commercient31__HIST_ORD_DETAIL__c, Commercient31__HIST_ORDERS__c, Commercient31__SHIP_TO__c, Contact, Commercient31__ORD_DETAIL__c, Commercient31__ORDERS__c, Commercient31__SALESPEOPLE__c, Commercient31__TERMS__c, Product2, IQMS_Inventory__c, IQMS_Order_Detail__c, IQMS_Quote_Detail__c, IQMS_Quote_Header__c and 3 custom objects
• Object display names: Account, IQMS Customer, IQMS CustomerToAccountLookup, SYNC ACCOUNT, SYNC CONTACT, SYNC CUSTOMER, SYNC CUSTOMERTOACCOUNTLOOKUP, SYNC INVOICEDETAIL, SYNC INVOICEHEADER, SYNC SALESORDERDETAIL, SYNC SALESORDERHEADER, SYNC SALESORDERHISTORYDETAIL, 19 more and 2 further templates
• Template groups: Account, Salesorder, Invoice, Product, Customer Multi Ship Addresses, Opportunity

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_IQMS_User
• vw_IQMS_Account
• vw_IQMS_CustomerToAccountLookup
• vw_IQMS_Contact
• vw_IQMS_Customer
• vw_IQMS_ShipToAddress
• vw_IQMS_InvoiceHeader
• vw_IQMS_InvoiceDetail
• vw_IQMS_SalesOrderDetail
• vw_IQMS_SalesOrderHistoryHeader
• vw_IQMS_SalesOrderHistoryDetail
• vw_IQMS_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 IQMS → 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.