CRMPro → Salesforce — Sage MAS 90: what the shipped templates set up

CRMPro → Salesforce — Sage MAS 90: 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/sage-mas-90.md, and that skill’s ERP table is what points at it. What follows is only what the shipped Sage MAS 90 → 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, CommercientSF8__AR_CUSTOMER__c, CommercientSF8__SAGE100_SalesPerson__c	SF_ERP_Salesforce_Clone_AR_CUSTOMER, SF_ERP_Salesforce_Clone_AR_SALESPERSON
AR Invoice Payments	Commercient Syncs the payment details that are held in the receivables file and held against an invoice in the ERP. The amount received from a customer, the date of payment, the method of payment, whether partial or full payment, etc New records are created and existing ones updated; none are deleted.	CommercientSF8__AR_TRANSACTIONPAYMENTHISTORY__c	SF_ERP_Salesforce_Clone_AR_TRANSACTIONPAYMENTHISTORY, SF_ERP_Salesforce_Clone_AR_INVOICEHISTORYHEADER, CommercientFlags
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 and existing ones updated; none are deleted.	CommercientSF8__SO_SHIPTOADDRESS__c	SF_ERP_Salesforce_Clone_SO_SHIPTOADDRESS
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 and existing ones updated; none are deleted.	CommercientSF8__AR_INVOICEHISTORYHEADER__c, CommercientSF8__AR_INVOICEHISTORYDETAIL__c	SF_ERP_Salesforce_Clone_AR_INVOICEHISTORYHEADER, CommercientFlags, SF_ERP_Salesforce_Clone_AR_OPENINVOICE, SF_ERP_Salesforce_Clone_AR_SALESPERSON, SF_ERP_Salesforce_Clone_AR_INVOICEHISTORYDETAIL
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 and existing ones updated; none are deleted.	CommercientSF8__SO_SALESORDERHEADER__c, CommercientSF8__SO_SALESORDERDETAIL__c	SF_ERP_Salesforce_Clone_SO_SALESORDERHEADER, CommercientFlags, SF_ERP_Salesforce_Clone_SO_SALESORDERDETAIL

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_SAGEMASS90_User	1=0	'' / ''	1
SYNC SALESPERSON	CommercientSF8__SAGE100_SalesPerson__c	CommercientSF8__ExternalKey__c	1	vw_SAGEMASS90_SALESPERSON	vw_SAGEMASS90_SALESPERSON	CommercientSF8__ / __c	1
CRM Account	account	CommercientSF__Commercient_ArCustomerCode__c	2	vw_SAGEMASS90_CRM_ACCOUNT	vw_SAGEMASS90_CRM_ACCOUNT	'' / ''	—
Sage Customer	CommercientSF8__AR_CUSTOMER__c	CommercientSF8__ExternalKey__c	3	vw_SAGEMASS90_CUSTOMER	vw_SAGEMASS90_CUSTOMER	CommercientSF8__ / __c	—
Sage Ship To Address	CommercientSF8__SO_SHIPTOADDRESS__c	CommercientSF8__ExternalKey__c	5	vw_SAGEMASS90_SHIPTOADDRESS	vw_SAGEMASS90_SHIPTOADDRESS	CommercientSF8__ / __c	—
Sage SalesOrder Header	CommercientSF8__SO_SALESORDERHEADER__c	CommercientSF8__SALESORDERNO__c	12	vw_SAGEMASS90_SALESORDERHEADER	vw_SAGEMASS90_SALESORDERHEADER	CommercientSF8__ / __c	—
Sage SalesOrder Detail	CommercientSF8__SO_SALESORDERDETAIL__c	CommercientSF8__ExternalKey__c	13	vw_SAGEMASS90_SALESORDERDETAIL	vw_SAGEMASS90_SALESORDERDETAIL	CommercientSF8__ / __c	—
Sage Invoice History Header	CommercientSF8__AR_INVOICEHISTORYHEADER__c	CommercientSF8__ExternalKey__c	14	vw_SAGEMASS90_INVOICEHISTORYHEADER	vw_SAGEMASS90_INVOICEHISTORYHEADER	CommercientSF8__ / __c	—
Sage Invoice History Detail	CommercientSF8__AR_INVOICEHISTORYDETAIL__c	CommercientSF8__ExternalKey__c	15	vw_SAGEMASS90_INVOICEHISTORYDETAIL	vw_SAGEMASS90_INVOICEHISTORYDETAIL	CommercientSF8__ / __c	—
Sage Transaction Payment History	CommercientSF8__AR_TRANSACTIONPAYMENTHISTORY__c	CommercientSF8__ExternalKey__c	16	vw_SAGEMASS90_TRANSACTIONPAYMENTHISTORY	vw_SAGEMASS90_TRANSACTIONPAYMENTHISTORY	CommercientSF8__ / __c	—

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 CRM Account. Text columns a template does not use are inserted as '' rather than left NULL. Get_SOQL_Query carries a query on GET USER — 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_SAGEMASS90_SALESPERSON	insert + update	vw_SAGEMASS90_SALESPERSON:	—	—	SF_ERP_Salesforce_Clone_AR_SALESPERSON
vw_SAGEMASS90_CRM_ACCOUNT	insert + update	vw_SAGEMASS90_CRM_ACCOUNT:	—	—	SF_ERP_Salesforce_Clone_AR_CUSTOMER
vw_SAGEMASS90_CUSTOMER	insert + update	vw_SAGEMASS90_CUSTOMER:	vw_SAGEMASS90_CRM_ACCOUNT:	ExternalKey	SF_ERP_Salesforce_Clone_AR_CUSTOMER
vw_SAGEMASS90_SHIPTOADDRESS	insert + update	vw_SAGEMASS90_SHIPTOADDRESS:	vw_SAGEMASS90_CRM_ACCOUNT:, vw_SAGEMASS90_CUSTOMER:	ExternalKey	SF_ERP_Salesforce_Clone_SO_SHIPTOADDRESS
vw_SAGEMASS90_SALESORDERHEADER	insert + update	vw_SAGEMASS90_SALESORDERHEADER:	vw_SAGEMASS90_CRM_ACCOUNT:, vw_SAGEMASS90_CUSTOMER:	—	SF_ERP_Salesforce_Clone_SO_SALESORDERHEADER, CommercientFlags
vw_SAGEMASS90_SALESORDERDETAIL	insert + update	vw_SAGEMASS90_SALESORDERDETAIL:	vw_SAGEMASS90_SALESORDERHEADER:	ExternalKey	SF_ERP_Salesforce_Clone_SO_SALESORDERDETAIL
vw_SAGEMASS90_INVOICEHISTORYHEADER	insert + update	vw_SAGEMASS90_INVOICEHISTORYHEADER:	vw_SAGEMASS90_CRM_ACCOUNT:, vw_SAGEMASS90_CUSTOMER:	ExternalKey	SF_ERP_Salesforce_Clone_AR_INVOICEHISTORYHEADER, CommercientFlags, SF_ERP_Salesforce_Clone_AR_OPENINVOICE, SF_ERP_Salesforce_Clone_AR_SALESPERSON
vw_SAGEMASS90_INVOICEHISTORYDETAIL	insert + update	vw_SAGEMASS90_INVOICEHISTORYDETAIL:	vw_SAGEMASS90_INVOICEHISTORYHEADER:	ExternalKey	SF_ERP_Salesforce_Clone_AR_INVOICEHISTORYDETAIL
vw_SAGEMASS90_TRANSACTIONPAYMENTHISTORY	insert + update	vw_SAGEMASS90_TRANSACTIONPAYMENTHISTORY:	vw_SAGEMASS90_CRM_ACCOUNT:, vw_SAGEMASS90_CUSTOMER:, vw_SAGEMASS90_INVOICEHISTORYHEADER:	ExternalKey	SF_ERP_Salesforce_Clone_AR_TRANSACTIONPAYMENTHISTORY, SF_ERP_Salesforce_Clone_AR_INVOICEHISTORYHEADER, CommercientFlags

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 USER
• 1 — SYNC SALESPERSON
• 2 — CRM Account
• 3 — Sage Customer
• 5 — Sage Ship To Address
• 12 — Sage SalesOrder Header
• 13 — Sage SalesOrder Detail
• 14 — Sage Invoice History Header
• 15 — Sage Invoice History Detail
• 16 — Sage Transaction Payment History

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_SAGEMASS90_TRANSACTIONPAYMENTHISTORY reads vw_SAGEMASS90_CRM_ACCOUNT:, vw_SAGEMASS90_CUSTOMER:, vw_SAGEMASS90_INVOICEHISTORYHEADER:
• vw_SAGEMASS90_CUSTOMER reads vw_SAGEMASS90_CRM_ACCOUNT:
• vw_SAGEMASS90_SHIPTOADDRESS reads vw_SAGEMASS90_CRM_ACCOUNT:, vw_SAGEMASS90_CUSTOMER:
• vw_SAGEMASS90_INVOICEHISTORYHEADER reads vw_SAGEMASS90_CRM_ACCOUNT:, vw_SAGEMASS90_CUSTOMER:
• vw_SAGEMASS90_INVOICEHISTORYDETAIL reads vw_SAGEMASS90_INVOICEHISTORYHEADER:
• vw_SAGEMASS90_SALESORDERHEADER reads vw_SAGEMASS90_CRM_ACCOUNT:, vw_SAGEMASS90_CUSTOMER:
• vw_SAGEMASS90_SALESORDERDETAIL reads vw_SAGEMASS90_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
SYNC SALESPERSON	CommercientSF8__SAGE100_SalesPerson__c	26	Sales_Manager → CommercientSF8__Sales_Manager__c, SALESPERSONDIVISIONNO → CommercientSF8__SALESPERSONDIVISIONNO__c, SALESPERSONNO → CommercientSF8__SALESPERSONNO__c, SALESPERSONNAME → CommercientSF8__SALESPERSONNAME__c, ADDRESSLINE1 → CommercientSF8__ADDRESSLINE1__c
CRM Account	account	12	ARDIVISIONNO, CUSTOMERNO → CommercientSF__Commercient_ArCustomerCode__c, CUSTOMERNAME, CUSTOMERNO → Name, ADDRESSLINE1, ADDRESSLINE2, ADDRESSLINE3 → BillingStreet, CITY → BillingCity, STATE → BillingState
Sage Customer	CommercientSF8__AR_CUSTOMER__c	75	ARDIVISIONNO,CUSTOMERNO → CommercientSF8__ExternalKey__c, CUSTOMERNAME → CommercientSF8__Name__c, ARDIVISIONNO → CommercientSF8__ARDIVISIONNO__c, CUSTOMERNO → CommercientSF8__CUSTOMERNO__c, ADDRESSLINE1 → CommercientSF8__ADDRESSLINE1__c
Sage Ship To Address	CommercientSF8__SO_SHIPTOADDRESS__c	33	ARDIVISIONNO, CUSTOMERNO, SHIPTOCODE → CommercientSF8__ExternalKey__c, ARDIVISIONNO → CommercientSF8__ARDIVISIONNO__c, CUSTOMERNO → CommercientSF8__CUSTOMERNO__c, SHIPTOCODE → CommercientSF8__SHIPTOCODE__c, SHIPTONAME → CommercientSF8__SHIPTONAME__c
Sage SalesOrder Header	CommercientSF8__SO_SALESORDERHEADER__c	132	SALESORDERNO → CommercientSF8__SALESORDERNO__c, ORDERDATE → CommercientSF8__ORDERDATE__c, ORDERTYPE → CommercientSF8__ORDERTYPE__c, ORDERSTATUS → CommercientSF8__ORDERSTATUS__c, MASTERREPEATINGORDERNO → CommercientSF8__MASTERREPEATINGORDERNO__c
Sage SalesOrder Detail	CommercientSF8__SO_SALESORDERDETAIL__c	64	SALESORDERNO, LINEKEY → CommercientSF8__ExternalKey__c, SALESORDERNO → CommercientSF8__SALESORDERNO__c, LINEKEY → CommercientSF8__LINEKEY__c, LINESEQNO → CommercientSF8__LINESEQNO__c, ITEMCODE → CommercientSF8__ITEMCODE__c
Sage Invoice History Header	CommercientSF8__AR_INVOICEHISTORYHEADER__c	119	INVOICENO, HEADERSEQNO → CommercientSF8__ExternalKey__c, INVOICENO → CommercientSF8__INVOICENO__c, HEADERSEQNO → CommercientSF8__HEADERSEQNO__c, MODULECODE → CommercientSF8__MODULECODE__c, INVOICETYPE → CommercientSF8__INVOICETYPE__c
Sage Invoice History Detail	CommercientSF8__AR_INVOICEHISTORYDETAIL__c	57	INVOICENO, HEADERSEQNO, DETAILSEQNO → CommercientSF8__ExternalKey__c, INVOICENO → CommercientSF8__INVOICENO__c, HEADERSEQNO → CommercientSF8__HEADERSEQNO__c, DETAILSEQNO → CommercientSF8__DETAILSEQNO__c, ITEMCODE → CommercientSF8__ITEMCODE__c
Sage Transaction Payment History	CommercientSF8__AR_TRANSACTIONPAYMENTHISTORY__c	30	ARDIVISIONNO → CommercientSF8__ARDIVISIONNO__c, CUSTOMERNO → CommercientSF8__CUSTOMERNO__c, INVOICENO → CommercientSF8__INVOICENO__c, INVOICETYPE → CommercientSF8__INVOICETYPE__c, INVOICEHISTORYHEADERSEQNO → CommercientSF8__INVOICEHISTORYHEADERSEQNO__c

6. Community templates

The catalogue carries 50 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: 50
• Default operations: insert on 50, update on 50, delete on 50
• Marked circular-sync: 0
• Licence groups they span: 12
• Destination objects: CommercientSF8__SO_SALESORDERDETAIL__c, CommercientSF8__SO_SALESORDERHEADER__c, PriceBookEntry, Product2, CommercientSF8__SAGE100_CI_Item__c, ACCOUNT, CommercientSF8__AR_CUSTOMER__c, CommercientSF8__AR_INVOICEHISTORYDETAIL__c, CommercientSF8__AR_INVOICEHISTORYHEADER__c, CommercientSF8__AR_TRANSACTIONPAYMENTHISTORY__c, CommercientSF8__SAGE100_AP_VENDOR__c, CommercientSF8__SAGE100_PO_PURCHASEORDERDETAIL__c, CommercientSF8__SAGE100_PO_PURCHASEORDERHEADER__c, CommercientSF8__SO_SHIPTOADDRESS__c, Account, CASE, CommercientSF8__PRIMARYVENDORNO__c, CommercientSF8__Sage100_Invoice_Tracking_History__c, CommercientSF8__SAGE100_ItemWarehouse__c, CommercientSF8__SAGE100_SALESORDERHISTORYDETAIL__c, 4 more and 2 custom objects
• Object display names: AR_CUSTOMER, CI Item to Vendor lookup, Get Account, GET CASE, Get So_Salesorderheader, Invoice Details, Invoice Header, Invoice Tracking History, PriceBookEntry Create, PriceBookEntry Update, Product Reverse Lookup, Purchase Order, 29 more and 9 further templates
• Template groups: Product, Salesorder, Account, Purchase Order, Customer Multi Ship Addresses, Invoice, Invoice History Headers

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_SAGEMASS90_User
• vw_SAGEMASS90_CRM_ACCOUNT
• vw_SAGEMASS90_TRANSACTIONPAYMENTHISTORY
• vw_SAGEMASS90_CUSTOMER
• vw_SAGEMASS90_SHIPTOADDRESS
• vw_SAGEMASS90_INVOICEHISTORYHEADER
• vw_SAGEMASS90_INVOICEHISTORYDETAIL
• vw_SAGEMASS90_SALESORDERHEADER
• vw_SAGEMASS90_SALESORDERDETAIL
• vw_SAGEMASS90_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 Sage MAS 90 → 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.