CRMPro → Salesforce — Sage 200 Evolution: what the shipped templates set up

CRMPro → Salesforce — Sage 200 Evolution: 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-200-evolution.md, and that skill’s ERP table is what points at it. What follows is only what the shipped Sage 200 Evolution → 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 and existing ones updated; none are deleted.	Account, CommercientSF8__Client__c, CommercientSF8__SalesRep__c	SF_ERP_Salesforce_Clone_Client, SF_ERP_Salesforce_Clone_SalesRep
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__bvInvNumARFull_InvoiceHeader__c, CommercientSF8__bvInvLinesFull_InvoiceLine__c	CommercientFlags, SF_ERP_Salesforce_Clone__bvInvNumARFull, C, S, SF_ERP_Salesforce_Clone__bvInvLinesFull
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__bvInvNumARFull_SalesOrderHeader__c, CommercientSF8__bvInvLinesFull_SalesOrderLine__c	CommercientFlags, SF_ERP_Salesforce_Clone__bvInvNumARFull, C, S, SF_ERP_Salesforce_Clone__bvInvLinesFull

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_SAGE200EVOLUTION_User	1=0	'' / ''	1
Sales Person	CommercientSF8__SalesRep__c	CommercientSF8__ExternalKey__c	1	vw_SalesPerson	vw_SAGE200EVOLUTION_SalesPerson	CommercientSF8__ / __c	1
Account	Account	CommercientSF__Commercient_ArCustomerCode__c	2	vw_Account	vw_SAGE200EVOLUTION_Account	'' / ''	1
Customer	CommercientSF8__Client__c	CommercientSF8__ExternalKey__c	3	vw_Customer	vw_SAGE200EVOLUTION_Customer	CommercientSF8__ / __c	1
Customer to Account Reverse Lookup	Account	CommercientSF__Commercient_ArCustomerCode__c	4	vw_CustomerToAccountLookup	vw_SAGE200EVOLUTION_CustomerToAccountLookup	'' / ''	1
Sales Order Header	CommercientSF8__bvInvNumARFull_SalesOrderHeader__c	CommercientSF8__ExternalKey__c	5	vw_SalesOrderHeader	vw_SAGE200EVOLUTION_SalesOrderHeader	CommercientSF8__ / __c	1
Sales Order Detail	CommercientSF8__bvInvLinesFull_SalesOrderLine__c	CommercientSF8__ExternalKey__c	6	vw_SalesOrderDetail	vw_SAGE200EVOLUTION_SalesOrderDetail	CommercientSF8__ / __c	1
Invoice Header	CommercientSF8__bvInvNumARFull_InvoiceHeader__c	CommercientSF8__ExternalKey__c	7	vw_InvoiceHeader	vw_SAGE200EVOLUTION_InvoiceHeader	CommercientSF8__ / __c	1
Invoice Detail	CommercientSF8__bvInvLinesFull_InvoiceLine__c	CommercientSF8__ExternalKey__c	8	vw_InvoiceDetail	vw_SAGE200EVOLUTION_InvoiceDetail	CommercientSF8__ / __c	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, 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_SAGE200EVOLUTION_SalesPerson	insert + update	vw_SalesPerson:	—	ExternalKey	SF_ERP_Salesforce_Clone_SalesRep
vw_SAGE200EVOLUTION_Account	insert + update	vw_Account:	vw_SalesPerson:, vw_SAGE200EVOLUTION_User:	—	SF_ERP_Salesforce_Clone_Client
vw_SAGE200EVOLUTION_Customer	insert + update	vw_Customer:	vw_SalesPerson:, vw_Account:	ExternalKey	SF_ERP_Salesforce_Clone_Client
vw_SAGE200EVOLUTION_CustomerToAccountLookup	insert + update	vw_CustomerToAccountLookup:	vw_Customer:	—	SF_ERP_Salesforce_Clone_Client
vw_SAGE200EVOLUTION_SalesOrderHeader	insert + update	vw_SalesOrderHeader:	vw_SalesPerson:, vw_Account:, vw_Customer:	ExternalKey	CommercientFlags, SF_ERP_Salesforce_Clone__bvInvNumARFull, C, S
vw_SAGE200EVOLUTION_SalesOrderDetail	insert + update	vw_SalesOrderDetail:	vw_SalesOrderHeader:	ExternalKey	SF_ERP_Salesforce_Clone__bvInvLinesFull
vw_SAGE200EVOLUTION_InvoiceHeader	insert + update	vw_InvoiceHeader:	vw_SalesPerson:, vw_Account:, vw_Customer:	ExternalKey	CommercientFlags, SF_ERP_Salesforce_Clone__bvInvNumARFull, C, S
vw_SAGE200EVOLUTION_InvoiceDetail	insert + update	vw_InvoiceDetail:	vw_InvoiceHeader:	ExternalKey	SF_ERP_Salesforce_Clone__bvInvLinesFull

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

• 0 — GET USER
• 1 — Sales Person
• 2 — Account
• 3 — Customer
• 4 — Customer to Account Reverse Lookup
• 5 — Sales Order Header
• 6 — Sales Order Detail
• 7 — Invoice Header
• 8 — Invoice Detail

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_SAGE200EVOLUTION_Account reads vw_SalesPerson:, vw_SAGE200EVOLUTION_User:
• vw_SAGE200EVOLUTION_CustomerToAccountLookup reads vw_Customer:
• vw_SAGE200EVOLUTION_Customer reads vw_SalesPerson:, vw_Account:
• vw_SAGE200EVOLUTION_InvoiceHeader reads vw_SalesPerson:, vw_Account:, vw_Customer:
• vw_SAGE200EVOLUTION_InvoiceDetail reads vw_InvoiceHeader:
• vw_SAGE200EVOLUTION_SalesOrderHeader reads vw_SalesPerson:, vw_Account:, vw_Customer:
• vw_SAGE200EVOLUTION_SalesOrderDetail reads vw_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
Sales Person	CommercientSF8__SalesRep__c	30	idSalesRep → CommercientSF8__ExternalKey__c, Name → CommercientSF8__Name__c, Code → CommercientSF8__Code__c, Method → CommercientSF8__Method__c, Target1 → CommercientSF8__Target1__c
Account	Account	13	DCLink → CommercientSF__Commercient_ArCustomerCode__c, Name, Account → Name, Telephone → Phone, RepID → CommercientSF8__SAGE200EVOLUTION_SalesPerson__c, Physical1, Physical2 → BillingStreet
Customer	CommercientSF8__Client__c	104	DCLink → CommercientSF8__ExternalKey__c, RepID → SAGE200EVOLUTION_SalesPerson, DCLink → Account_Lookup, Name → CommercientSF8__Name__c, Title → Title
Customer to Account Reverse Lookup	Account	2	DCLink → CommercientSF__Commercient_ArCustomerCode__c, SFDCID → CommercientSF8__SAGE200EVOLUTION_Customer__c
Sales Order Header	CommercientSF8__bvInvNumARFull_SalesOrderHeader__c	319	AutoIndex → CommercientSF8__ExternalKey__c, OrderNum → Name, RepID → SAGE200EVOLUTION_SalesPerson, DCLink → Account_Lookup, Account → SAGE200EVOLUTION_Customer
Sales Order Detail	CommercientSF8__bvInvLinesFull_SalesOrderLine__c	211	iInvoiceID, idInvoiceLines → CommercientSF8__ExternalKey__c, iInvoiceID, idInvoiceLines → Name, SFDCID → SAGE200EVOLUTION_Sales_Order_Header, idInvoiceLines → idInvoiceLines, iInvoiceID → iInvoiceID
Invoice Header	CommercientSF8__bvInvNumARFull_InvoiceHeader__c	6	AutoIndex → CommercientSF8__ExternalKey__c, InvNumber → Name, RepID → SAGE200EVOLUTION_SalesPerson, DCLink → Account_Lookup, Account → SAGE200EVOLUTION_Customer
Invoice Detail	CommercientSF8__bvInvLinesFull_InvoiceLine__c	208	iInvoiceID,idInvoiceLines → CommercientSF8__ExternalKey__c, iInvoiceID,idInvoiceLines → Name, SFDCID → SAGE200EVOLUTION_Invoice_Header, idInvoiceLines → idInvoiceLines, iInvoiceID → iInvoiceID

6. 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_SAGE200EVOLUTION_User
• vw_Account
• vw_CustomerToAccountLookup
• vw_Customer
• vw_InvoiceHeader
• vw_InvoiceDetail
• vw_SalesOrderHeader
• vw_SalesOrderDetail
• vw_SalesPerson

7. 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 200 Evolution → 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.