CRMPro → Salesforce — Sage 50 Canada: what the shipped templates set up

CRMPro → Salesforce — Sage 50 Canada: 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-50-canada.md, and that skill’s ERP table is what points at it. What follows is only what the shipped Sage 50 Canada → 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, CommercientSF8__SAGE50CA_Customer__c	SF_ERP_Salesforce_Clone_tcustomr, SF_ERP_Salesforce_Clone_tcustshp
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.	CommercientSF8__SAGE50CA_Address__c	SF_ERP_Salesforce_Clone_tcustshp, SF_ERP_Salesforce_Clone_tcustomr
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.	CommercientSF8__SAGE50CA_Invoice__c, CommercientSF8__SAGE50CA_InvoiceDetail__c	SF_ERP_Salesforce_Clone_titlu, SF_ERP_Salesforce_Clone_tcustomr, CommercientFlags, SF_ERP_Salesforce_Clone_titluli
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.	CommercientSF8__SAGE50CA_Salesorder__c, CommercientSF8__SAGE50CA_SalesOrderLine__c	SF_ERP_Salesforce_Clone_tsalordr, CommercientFlags, SF_ERP_Salesforce_Clone_tsoline

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_Sage50CA_User	1=0	'' / ''	1
Account	Account	CommercientSF__Commercient_ArCustomerCode__c	2	vw_SAGE50CA_Account	vw_SAGE50CA_Account	'' / ''	1
Sage50CA Customer	CommercientSF8__SAGE50CA_Customer__c	CommercientSF8__ExternalKey__c	3	vw_SAGE50CA_Customer	vw_SAGE50CA_Customer	CommercientSF8__ / __c	1
SAGE50CA CustomerToAccountLookup	Account	CommercientSF__Commercient_ArCustomerCode__c	4	vw_SAGE50CA_CustomerToAccountLookup	vw_SAGE50CA_CustomerToAccountLookup	'' / ''	1
SAGE50CA ShipToAddress	CommercientSF8__SAGE50CA_Address__c	CommercientSF8__ExternalKey__c	5	vw_SAGE50CA_ShipToAddress	vw_SAGE50CA_ShipToAddress	CommercientSF8__ / __c	1
SAGE50CA SalessOrderHeader	CommercientSF8__SAGE50CA_Salesorder__c	CommercientSF8__ExternalKey__c	6	vw_SAGE50CA_SalessOrderHeader	vw_SAGE50CA_SalessOrderHeader	CommercientSF8__ / __c	1
SAGE50CA SalessOrderDetail	CommercientSF8__SAGE50CA_SalesOrderLine__c	CommercientSF8__ExternalKey__c	7	vw_SAGE50CA_SalessOrderDetail	vw_SAGE50CA_SalessOrderDetail	CommercientSF8__ / __c	1
SAGE50CA InvoiceHeader	CommercientSF8__SAGE50CA_Invoice__c	CommercientSF8__ExternalKey__c	8	vw_SAGE50CA_InvoiceHeader	vw_SAGE50CA_InvoiceHeader	CommercientSF8__ / __c	1
SAGE50CA InvoiceDetail	CommercientSF8__SAGE50CA_InvoiceDetail__c	CommercientSF8__ExternalKey__c	9	vw_SAGE50CA_InvoiceLine	vw_SAGE50CA_InvoiceLine	CommercientSF8__ / __c	1
Contact	Contact	ExternalKey__c	10	vw_SAGE50CA_Contact	vw_SAGE50CA_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 — 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_SAGE50CA_Account	insert-only	vw_SAGE50CA_Account:	—	CommercientSF__Commercient_ArCustomerCode__c	SF_ERP_Salesforce_Clone_tcustomr, SF_ERP_Salesforce_Clone_tcustshp
vw_SAGE50CA_Customer	insert + update	vw_SAGE50CA_Customer:	vw_SAGE50CA_Account:	ExternalKey	SF_ERP_Salesforce_Clone_tcustomr
vw_SAGE50CA_CustomerToAccountLookup	insert + update	vw_SAGE50CA_CustomerToAccountLookup:	vw_SAGE50CA_Customer:	—	SF_ERP_Salesforce_Clone_tcustomr
vw_SAGE50CA_ShipToAddress	insert + update	vw_SAGE50CA_ShipToAddress:	vw_SAGE50CA_Account:, vw_SAGE50CA_Customer:, vw_SAGE50CA_GetOwner:	—	SF_ERP_Salesforce_Clone_tcustshp, SF_ERP_Salesforce_Clone_tcustomr
vw_SAGE50CA_SalessOrderHeader	insert + update	vw_SAGE50CA_SalessOrderHeader:	vw_SAGE50CA_Account:, vw_SAGE50CA_Customer:	ExternalKey	SF_ERP_Salesforce_Clone_tsalordr, CommercientFlags
vw_SAGE50CA_SalessOrderDetail	insert + update	vw_SAGE50CA_SalessOrderDetail:	vw_SAGE50CA_SalessOrderHeader:	—	SF_ERP_Salesforce_Clone_tsoline
vw_SAGE50CA_InvoiceHeader	insert + update	vw_SAGE50CA_InvoiceHeader:	vw_SAGE50CA_Account:, vw_SAGE50CA_Customer:	ExternalKey__c	SF_ERP_Salesforce_Clone_titlu, SF_ERP_Salesforce_Clone_tcustomr, CommercientFlags
vw_SAGE50CA_InvoiceLine	insert + update	vw_SAGE50CA_InvoiceLine:	vw_SAGE50CA_InvoiceHeader:	—	SF_ERP_Salesforce_Clone_titluli
vw_SAGE50CA_Contact	insert + update	vw_SAGE50CA_Contact:	vw_SAGE50CA_Account:	ExternalKey__c	SF_ERP_Salesforce_Clone_tcustomr

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 USER
• 2 — Account
• 3 — Sage50CA Customer
• 4 — SAGE50CA CustomerToAccountLookup
• 5 — SAGE50CA ShipToAddress
• 6 — SAGE50CA SalessOrderHeader
• 7 — SAGE50CA SalessOrderDetail
• 8 — SAGE50CA InvoiceHeader
• 9 — SAGE50CA InvoiceDetail
• 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_SAGE50CA_CustomerToAccountLookup reads vw_SAGE50CA_Customer:
• vw_SAGE50CA_Contact reads vw_SAGE50CA_Account:
• vw_SAGE50CA_Customer reads vw_SAGE50CA_Account:
• vw_SAGE50CA_ShipToAddress reads vw_SAGE50CA_Account:, vw_SAGE50CA_Customer:, vw_SAGE50CA_GetOwner:; no template in this set writes vw_SAGE50CA_GetOwner:
• vw_SAGE50CA_InvoiceHeader reads vw_SAGE50CA_Account:, vw_SAGE50CA_Customer:
• vw_SAGE50CA_InvoiceLine reads vw_SAGE50CA_InvoiceHeader:
• vw_SAGE50CA_SalessOrderHeader reads vw_SAGE50CA_Account:, vw_SAGE50CA_Customer:
• vw_SAGE50CA_SalessOrderDetail reads vw_SAGE50CA_SalessOrderHeader:

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
Account	Account	12	CommercientSFommercient_ArCustomerCode → CommercientSF__Commercient_ArCustomerCode__c, BillingStreet → BillingStreet, BillingCity → BillingCity, BillingState → BillingState, BillingCountry → BillingCountry
Sage50CA Customer	CommercientSF8__SAGE50CA_Customer__c	62	Account → Account, bInactive → bInactive, bCanSaveCC → bCanSaveCC, bEFTMyCode → bEFTMyCode, bEFTMyRef → CommercientSF8__bEFTMyRef__c
SAGE50CA CustomerToAccountLookup	Account	2	CommercientSFommercient_ArCustomerCode → CommercientSF__Commercient_ArCustomerCode__c, CommercientSF8__SAGE50CA_Customer → CommercientSF8__SAGE50CA_Customer__c
SAGE50CA ShipToAddress	CommercientSF8__SAGE50CA_Address__c	19	ExternalKey → CommercientSF8__ExternalKey__c, Account → Account, SAGE50CA_Customer → CommercientSF8__SAGE50CA_Customer__c, lCustId → CommercientSF8__lCustId__c, lId → CommercientSF8__lId__c
SAGE50CA SalessOrderHeader	CommercientSF8__SAGE50CA_Salesorder__c	59	Account → Account, Customer → CommercientSF8__Customer__c, lAcctNum → lAcctNum, lChqId → CommercientSF8__lChqId__c, sChqNum → CommercientSF8__sChqNum__c
SAGE50CA SalessOrderDetail	CommercientSF8__SAGE50CA_SalesOrderLine__c	25	tsalordr → tsalordr__c, lAcctId → lAcctId, dAmount → CommercientSF8__dAmount__c, bDefBsPric → bDefBsPric, lAcctDptId → lAcctDptId
SAGE50CA InvoiceHeader	CommercientSF8__SAGE50CA_Invoice__c	36	tcustomr → tcustomr__c, Account → Account, lAcctId → lAcctId__c, bAlocToAll → bAlocToAll__c, lAddrId → lAddrId__c
SAGE50CA InvoiceDetail	CommercientSF8__SAGE50CA_InvoiceDetail__c	25	titlu → titlu__c, dBasePrice → dBasePrice__c, sDesc → sDesc__c, dDOQty → dDOQty__c, dDutyAmt → dDutyAmt__c
Contact	Contact	11	AccountID → AccountID, LastName → LastName, FirstName → FirstName, Email → Email, Phone → Phone

6. Community templates

The catalogue carries 41 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: 41
• Default operations: insert on 41, update on 41, delete on 41
• Marked circular-sync: 1
• Licence groups they span: 10
• Destination objects: Account, Contact, Opportunity, Product2, CommercientSF8__SAGE50CA_Customer__c, CommercientSF8__ACCOUNTMATCHING__c, CommercientSF8__CONTACTMATCHING__c, CommercientSF8__PRODUCTMATCHING__c, CommercientSF8__SAGE50CA_Address__c, CommercientSF8__SAGE50CA_Item__c, CommercientSF8__SAGE50CA_Salesorder__c, CommercientSF8__SAGE50CA_SalesOrderLine__c, CommercientSF8__SAGE50CA_Warehouse__c, OpportunityLineItem, PriceBookEntry, temp__c and 11 custom objects
• Object display names: Account, Item Master, SAGE50CA CustomerToAccountLookup, Product, Sage50CA Customer, SAGE50CA InvoiceDetail, SAGE50CA InvoiceHeader, SAGE50CA SalessOrderDetail, SAGE50CA SalessOrderHeader, SAGE50CA ShipToAddress, Warehouse, AccountUpdate, 14 more and a further template
• Template groups: Account, Product, CRM Opportunity and Line, 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_Sage50CA_User
• vw_SAGE50CA_Account
• vw_SAGE50CA_CustomerToAccountLookup
• vw_SAGE50CA_Contact
• vw_SAGE50CA_Customer
• vw_SAGE50CA_ShipToAddress
• vw_SAGE50CA_InvoiceHeader
• vw_SAGE50CA_InvoiceLine
• vw_SAGE50CA_SalessOrderHeader
• vw_SAGE50CA_SalessOrderDetail

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 50 Canada → 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.