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

CRMPro → Salesforce — QAD: 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/qad.md, and that skill’s ERP table is what points at it. What follows is only what the shipped QAD → 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 USER	The templates push users to Salesforce. New records are created, existing ones updated, and records removed in the ERP are deleted.	users	—
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__QAD_Customer__c, CommercientSF18__QAD_Salesperson__c	SF_ERP_Salesforce_Clone_cm_mstr, SF_ERP_Salesforce_Clone_ad_mstr, SF_ERP_Salesforce_Clone_Contact, SF_ERP_Salesforce_Clone_Address
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__QAD_ADDR__c	SF_ERP_Salesforce_Clone_ad_mstr, SF_ERP_Salesforce_Clone_cm_mstr
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__QAD_Invoice__c, CommercientSF18__QAD_InvoiceDetail__c	SF_ERP_Salesforce_Clone_ih_hist, CommercientFlags, SF_ERP_Salesforce_Clone_idh_hist
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__QAD_SalesOrder__c, CommercientSF18__QAD_SalesOrderDetail__c	SF_ERP_Salesforce_Clone_so_mstr, SF_ERP_Salesforce_Clone_ih_hist, SF_ERP_Salesforce_Clone_ad_mstr, CommercientFlags, SF_ERP_Salesforce_Clone_sod_det

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	users	—	0	vw_QADERP_User	1=0	'' / ''	1
QADERP Salesperson	CommercientSF18__QAD_Salesperson__c	CommercientSF18__ExternalKey__c	1	vw_QADERP_SalesPerson	vw_QADERP_SalesPerson	CommercientSF18__ / __c	1
Account	Account	CommercientSF__Commercient_ArCustomerCode__c	2	vw_QADERP_Account	vw_QADERP_Account	'' / ''	1
QADERP Customer	CommercientSF18__QAD_Customer__c	CommercientSF18__ExternalKey__c	4	vw_QADERP_Customer	vw_QADERP_Customer	CommercientSF18__ / __c	1
QADERP CustomerToAccountLookup	Account	CommercientSF__Commercient_ArCustomerCode__c	5	vw_QADERP_CustomerToAccountLookup	vw_QADERP_CustomerToAccountLookup	'' / ''	1
QADERP SalesOrder	CommercientSF18__QAD_SalesOrder__c	CommercientSF18__ExternalKey__c	6	vw_QADERP_SalesOrder	vw_QADERP_SalesOrder	CommercientSF18__ / __c	1
QADERP SalesOrderLine	CommercientSF18__QAD_SalesOrderDetail__c	CommercientSF18__ExternalKey__c	7	vw_QADERP_SalesOrderLine	vw_QADERP_SalesOrderLine	CommercientSF18__ / __c	1
QADERP Invoice	CommercientSF18__QAD_Invoice__c	CommercientSF18__ExternalKey__c	8	vw_QADERP_Invoice	vw_QADERP_Invoice	CommercientSF18__ / __c	1
QADERP InvoiceLine	CommercientSF18__QAD_InvoiceDetail__c	CommercientSF18__ExternalKey__c	9	vw_QADERP_InvoiceLine	vw_QADERP_InvoiceLine	CommercientSF18__ / __c	1
QADERP Address	CommercientSF18__QAD_ADDR__c	CommercientSF18__ExternalKey__c	10	vw_QADERP_Address	vw_QADERP_Address	CommercientSF18__ / __c	1
Contact	Contact	ExternalKey__c	11	vw_QADERP_Contact	vw_QADERP_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 USER, Account — 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_QADERP_SalesPerson	insert + update	vw_QADERP_SalesPerson:	—	ExternalKey	SF_ERP_Salesforce_Clone_ad_mstr
vw_QADERP_Account	insert-only	vw_QADERP_Account:	vw_QADERP_SalesPerson:, vw_QADERP_User:	—	SF_ERP_Salesforce_Clone_cm_mstr, SF_ERP_Salesforce_Clone_ad_mstr
vw_QADERP_Customer	insert + update	vw_QADERP_Customer:	vw_QADERP_SalesPerson:, vw_QADERP_Account:	—	SF_ERP_Salesforce_Clone_cm_mstr
vw_QADERP_CustomerToAccountLookup	insert + update	vw_QADERP_CustomerToAccountLookup:	vw_QADERP_Customer:	—	SF_ERP_Salesforce_Clone_cm_mstr
vw_QADERP_SalesOrder	insert + update	vw_QADERP_SalesOrder:	vw_QADERP_Account:, vw_QADERP_Customer:, vw_QADERP_Address:, vw_QADERP_SalesPerson:	—	SF_ERP_Salesforce_Clone_so_mstr, SF_ERP_Salesforce_Clone_ih_hist, SF_ERP_Salesforce_Clone_ad_mstr, CommercientFlags
vw_QADERP_SalesOrderLine	insert + update	vw_QADERP_SalesOrderLine:	vw_QADERP_SalesOrder:	—	SF_ERP_Salesforce_Clone_sod_det
vw_QADERP_Invoice	insert + update	vw_QADERP_Invoice:	vw_QADERP_Account:, vw_QADERP_Customer:	—	SF_ERP_Salesforce_Clone_ih_hist, CommercientFlags
vw_QADERP_InvoiceLine	insert + update	vw_QADERP_InvoiceLine:	vw_QADERP_Invoice:	—	SF_ERP_Salesforce_Clone_idh_hist
vw_QADERP_Address	insert + update	vw_QADERP_Address:	vw_QADERP_Account:, vw_QADERP_Customer:	—	SF_ERP_Salesforce_Clone_ad_mstr, SF_ERP_Salesforce_Clone_cm_mstr
vw_QADERP_Contact	insert + update	vw_QADERP_Contact:	vw_QADERP_Address:	ExternalKey__c	SF_ERP_Salesforce_Clone_Contact, SF_ERP_Salesforce_Clone_Address

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

• 0 — GET USER
• 1 — QADERP Salesperson
• 2 — Account
• 4 — QADERP Customer
• 5 — QADERP CustomerToAccountLookup
• 6 — QADERP SalesOrder
• 7 — QADERP SalesOrderLine
• 8 — QADERP Invoice
• 9 — QADERP InvoiceLine
• 10 — QADERP Address
• 11 — 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_QADERP_Account reads vw_QADERP_SalesPerson:, vw_QADERP_User:
• vw_QADERP_CustomerToAccountLookup reads vw_QADERP_Customer:
• vw_QADERP_Contact reads vw_QADERP_Address:
• vw_QADERP_Customer reads vw_QADERP_SalesPerson:, vw_QADERP_Account:
• vw_QADERP_Address reads vw_QADERP_Account:, vw_QADERP_Customer:
• vw_QADERP_Invoice reads vw_QADERP_Account:, vw_QADERP_Customer:
• vw_QADERP_InvoiceLine reads vw_QADERP_Invoice:
• vw_QADERP_SalesOrder reads vw_QADERP_Account:, vw_QADERP_Customer:, vw_QADERP_Address:, vw_QADERP_SalesPerson:
• vw_QADERP_SalesOrderLine reads vw_QADERP_SalesOrder:

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
QADERP Salesperson	CommercientSF18__QAD_Salesperson__c	6	sp_addr → CommercientSF18__sp_addr__c, sp_sort → CommercientSF18__sp_sort__c, sp_user1 → CommercientSF18__sp_user1__c, sp_user2 → CommercientSF18__sp_user2__c, sp_domain → CommercientSF18__sp_domain__c
Account	Account	12	CommercientSFommercient_ArCustomerCode → CommercientSF__Commercient_ArCustomerCode__c, Type → Type, QAD_Salesperson → QAD_Salesperson__c, Active → Active__c, QAD_Code → QAD_Code__c
QADERP Customer	CommercientSF18__QAD_Customer__c	98	Account → Account, Salesperson → CommercientSF18__Salesperson__c, cm_active → cm_active, cm_submit_prop → CommercientSF18__cm_submit_prop__c, cm_drft_apv → CommercientSF18__cm_drft_apv__c
QADERP CustomerToAccountLookup	Account	2	CommercientSFommercient_ArCustomerCode → CommercientSF__Commercient_ArCustomerCode__c, CommercientSF18ustomer → CommercientSF18__Customer__c
QADERP SalesOrder	CommercientSF18__QAD_SalesOrder__c	116	QAD_Salesperson → QAD_Salesperson__c, Account → Account, Customer → CommercientSF18__Customer__c, so_stat → CommercientSF18__so_stat__c, so_ar_acct → so_ar_acct
QADERP SalesOrderLine	CommercientSF18__QAD_SalesOrderDetail__c	97	Salesorder → CommercientSF18__Salesorder__c, oid_sod_det → CommercientSF18__oid_sod_det__c, sod_abnormal → CommercientSF18__sod_abnormal__c, sod_acct → sod_acct, sod_act_price → sod_act_price
QADERP Invoice	CommercientSF18__QAD_Invoice__c	100	Account → Account, QAD_Customer → QAD_Customer, ih_stat → CommercientSF18__ih_stat__c, ih_ar_acct → ih_ar_acct, ih_ar_sub → CommercientSF18__ih_ar_sub__c
QADERP InvoiceLine	CommercientSF18__QAD_InvoiceDetail__c	96	Invoice → Invoice, idh_act_price → idh_act_price, idh_bonus → CommercientSF18__idh_bonus__c, idh_calc_isb → idh_calc_isb, idh_car_load → idh_car_load
QADERP Address	CommercientSF18__QAD_ADDR__c	68	Account → Account__c, QAD_Customer → QAD_Customer__c, ad_addr → CommercientSF18__ad_addr__c, ad_asn_data → CommercientSF18__ad_asn_data__c, ad_attn → CommercientSF18__ad_attn__c
Contact	Contact	13	QAD_Address → QAD_Address__c, LastName → LastName, FirstName → FirstName, Email → Email, Phone → Phone

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, CommercientSF18__QAD_ADDR__c, CommercientSF18__QAD_Address__c, CommercientSF18__QAD_Customer__c, CommercientSF18__QAD_Invoice__c, CommercientSF18__QAD_InvoiceDetail__c, CommercientSF18__QAD_SalesOrder__c, CommercientSF18__QAD_SalesOrderDetail__c, CommercientSF18__QAD_Salesperson__c, Contact
• Object display names: QADERP Address, Account, Account Update, Contact, QADERP Customer, QADERP CustomerToAccountLookup, QADERP Invoice, QADERP InvoiceLine, QADERP SalesOrder, QADERP SalesOrderLine, QADERP Salesperson
• Template groups: Account, Customer Multi Ship Addresses, Invoice, Salesorder

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_QADERP_User
• vw_QADERP_Account
• vw_QADERP_CustomerToAccountLookup
• vw_QADERP_Contact
• vw_QADERP_Customer
• vw_QADERP_Address
• vw_QADERP_Invoice
• vw_QADERP_InvoiceLine
• vw_QADERP_SalesOrder
• vw_QADERP_SalesOrderLine
• vw_QADERP_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 QAD → 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.