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

CRMPro → Salesforce — Sage 50 UK: 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-uk.md, and that skill’s ERP table is what points at it. What follows is only what the shipped Sage 50 UK → 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
Sage50 UK Audit Header	ERP AUDIT_HEADER data becomes CommercientSF8__SAGE50UK_AUDIT_HEADER__c in Salesforce. New records are created and existing ones updated; none are deleted.	CommercientSF8__SAGE50UK_AUDIT_HEADER__c	SF_ERP_Salesforce_Clone_AUDIT_HEADER
Sage50 UK Audit Split	ERP AUDIT_HEADER, AUDIT_SPLIT data becomes CommercientSF8__SAGE50UK_AUDIT_SPLIT__c in Salesforce. New records are created and existing ones updated; none are deleted.	CommercientSF8__SAGE50UK_AUDIT_SPLIT__c	SF_ERP_Salesforce_Clone_AUDIT_SPLIT, SF_ERP_Salesforce_Clone_AUDIT_HEADER
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, Contact, CommercientSF8__SAGE50UK_Customer__c	SF_ERP_Salesforce_Clone_SALES_LEDGER, SF_ERP_Salesforce_Clone_SALES_DEL_ADDR
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__SAGE50UK_Address__c	SF_ERP_Salesforce_Clone_SALES_DEL_ADDR
Product	The templates push CommercientSF8__SAGE50UK_Item__c, Product2 to Salesforce. New records are created and existing ones updated; none are deleted.	CommercientSF8__SAGE50UK_Item__c, Product2	SF_ERP_Salesforce_Clone_STOCK
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__SAGE50UK_InvoiceHeader__c, CommercientSF8__SAGE50UK_InvoiceDetail__c	SF_ERP_Salesforce_Clone_INVOICE, CommercientFlags, SF_ERP_Salesforce_Clone_INVOICE_ITEM
Pricebook	The templates push PricebookEntry to Salesforce. New records are created and existing ones updated; none are deleted.	PricebookEntry	SF_ERP_Salesforce_Clone_STOCK
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__SAGE50UK_SalesOrderHeader__c, CommercientSF8__SAGE50UK_SalesOrderDetail__c	SF_ERP_Salesforce_Clone_SALES_ORDER, CommercientFlags, SF_ERP_Salesforce_Clone_SOP_ITEM

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_SAGE50UK_User	1=0	'' / ''	1
Account	Account	CommercientSF__Commercient_ArCustomerCode__c	1	vw_SAGE50UK_Account	vw_SAGE50UK_Account	'' / ''	—
Customer Master	CommercientSF8__SAGE50UK_Customer__c	CommercientSF8__ExternalKey__c	2	vw_SAGE50UK_Customer	vw_SAGE50UK_Customer	CommercientSF8__ / __c	—
Customer Reverse Lookup Account	Account	CommercientSF__Commercient_ArCustomerCode__c	3	vw_SAGE50UK_CustomerToAccountLookup	vw_SAGE50UK_CustomerToAccountLookup	'' / ''	—
Sage50 UK Address	CommercientSF8__SAGE50UK_Address__c	CommercientSF8__ExternalKey__c	4	vw_SAGE50UK_Address	vw_SAGE50UK_Address	CommercientSF8__ / __c	—
Sales Order Header	CommercientSF8__SAGE50UK_SalesOrderHeader__c	CommercientSF8__ExternalKey__c	5	vw_SAGE50UK_SalesOrderHeader	vw_SAGE50UK_SalesOrderHeader	CommercientSF8__ / __c	—
Sales Order Details	CommercientSF8__SAGE50UK_SalesOrderDetail__c	CommercientSF8__ExternalKey__c	6	vw_SAGE50UK_SalesOrderDetail	vw_SAGE50UK_SalesOrderDetail	CommercientSF8__ / __c	—
Invoice Header	CommercientSF8__SAGE50UK_InvoiceHeader__c	CommercientSF8__ExternalKey__c	7	vw_SAGE50UK_InvoiceHeader	vw_SAGE50UK_InvoiceHeader	CommercientSF8__ / __c	—
Invoice Details	CommercientSF8__SAGE50UK_InvoiceDetail__c	CommercientSF8__ExternalKey__c	8	vw_SAGE50UK_InvoiceDetail	vw_SAGE50UK_InvoiceDetail	CommercientSF8__ / __c	—
Product	Product2	CommercientSF__ExternalKey__c	9	vw_SAGE50UK_Product	vw_SAGE50UK_Product	'' / ''	—
Item Master	CommercientSF8__SAGE50UK_Item__c	CommercientSF8__ExternalKey__c	10	vw_SAGE50UK_Item	vw_SAGE50UK_Item	CommercientSF8__ / __c	—
Item To Product Reverse Lookup	Product2	CommercientSF__ExternalKey__c	11	vw_SAGE50UK_ItemToProductLookup	vw_SAGE50UK_ItemToProductLookup	'' / ''	—
Create Standard PriceBook	PricebookEntry	ExternalKey__C	12	vw_SAGE50UK_StandardPriceBook	vw_SAGE50UK_StandardPriceBook	'' / ''	—
Standard Pricebook Update	PricebookEntry	ExternalKey__c	13	vw_ProductPriceBook	vw_SAGE50UK_ProductStandardPricebookUpdate	'' / ''	—
Contacts	Contact	CommercientSF8__ExternalKey__c	18	vw_SAGE50UK_Contact	vw_SAGE50UK_Contact	'' / ''	—
Sage50 UK Audit Header	CommercientSF8__SAGE50UK_AUDIT_HEADER__c	CommercientSF8__ExternalKey__c	19	vw_SAGE50UK_AuditHeader	vw_SAGE50UK_AuditHeader	CommercientSF8__ / __c	1
Sage50 UK Audit Split	CommercientSF8__SAGE50UK_AUDIT_SPLIT__c	CommercientSF8__ExternalKey__c	20	vw_SAGE50UK_AuditSplit	vw_SAGE50UK_AuditSplit	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_Delete_Records 0, Sync_Batch_Size 200. Is_Active_Get_Records is set on Create Standard PriceBook; IsAccountMatching is set on Account. Text columns a template does not use are inserted as '' rather than left NULL. Get_SOQL_Query carries a query on GET USER, Create Standard PriceBook — 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_SAGE50UK_Account	insert + update	vw_SAGE50UK_Account:	—	CommercientSF__Commercient_ArCustomerCode__c	SF_ERP_Salesforce_Clone_SALES_LEDGER, SF_ERP_Salesforce_Clone_SALES_DEL_ADDR
vw_SAGE50UK_Customer	insert + update	vw_SAGE50UK_Customer:	vw_SAGE50UK_Account:, vw_SAGE50UK_Address:	ExternalKey	SF_ERP_Salesforce_Clone_SALES_LEDGER, SF_ERP_Salesforce_Clone_SALES_DEL_ADDR
vw_SAGE50UK_CustomerToAccountLookup	insert + update	vw_SAGE50UK_CustomerToAccountLookup:	vw_SAGE50UK_Customer:	—	SF_ERP_Salesforce_Clone_SALES_LEDGER
vw_SAGE50UK_Address	insert + update	vw_SAGE50UK_Address:	vw_SAGE50UK_Account:, vw_SAGE50UK_Customer:	ExternalKey	SF_ERP_Salesforce_Clone_SALES_DEL_ADDR
vw_SAGE50UK_SalesOrderHeader	insert + update	vw_SAGE50UK_SalesOrderHeader:	vw_SAGE50UK_Account:, vw_SAGE50UK_Customer:	ExternalKey	SF_ERP_Salesforce_Clone_SALES_ORDER, CommercientFlags
vw_SAGE50UK_SalesOrderDetail	insert + update	vw_SAGE50UK_SalesOrderDetail:	vw_SAGE50UK_SalesOrderHeader:, vw_SAGE50UK_Item:	ExternalKey	SF_ERP_Salesforce_Clone_SOP_ITEM
vw_SAGE50UK_InvoiceHeader	insert + update	vw_SAGE50UK_InvoiceHeader:	vw_SAGE50UK_Account:, vw_SAGE50UK_Customer:	ExternalKey	SF_ERP_Salesforce_Clone_INVOICE, CommercientFlags
vw_SAGE50UK_InvoiceDetail	insert + update	vw_SAGE50UK_InvoiceDetail:	vw_SAGE50UK_InvoiceHeader:, vw_SAGE50UK_Item:	ExternalKey	SF_ERP_Salesforce_Clone_INVOICE_ITEM
vw_SAGE50UK_Product	insert + update	vw_SAGE50UK_Product:	—	—	SF_ERP_Salesforce_Clone_STOCK
vw_SAGE50UK_Item	insert + update	vw_SAGE50UK_Item:	vw_SAGE50UK_Product:	ExternalKey	SF_ERP_Salesforce_Clone_STOCK
vw_SAGE50UK_ItemToProductLookup	insert + update	vw_SAGE50UK_ItemToProductLookup:	vw_SAGE50UK_Item:	—	SF_ERP_Salesforce_Clone_STOCK
vw_SAGE50UK_StandardPriceBook	insert-only	vw_SAGE50UK_StandardPriceBook:	vw_SAGE50UK_Product:	—	SF_ERP_Salesforce_Clone_STOCK
vw_SAGE50UK_ProductStandardPricebookUpdate	insert + update	—	vw_SAGE50UK_StandardPriceBook:, vw_SAGE50UK_Product:	—	SF_ERP_Salesforce_Clone_STOCK
vw_SAGE50UK_Contact	insert + update	vw_SAGE50UK_Contact:	vw_SAGE50UK_Account:	—	SF_ERP_Salesforce_Clone_SALES_LEDGER
vw_SAGE50UK_AuditHeader	insert + update	vw_SAGE50UK_AuditHeader:	vw_SAGE50UK_Account:, vw_SAGE50UK_Customer:, vw_SAGE50UK_SalesOrderHeader:, vw_SAGE50UK_InvoiceHeader:	—	SF_ERP_Salesforce_Clone_AUDIT_HEADER
vw_SAGE50UK_AuditSplit	insert + update	vw_SAGE50UK_AuditSplit:	vw_SAGE50UK_AuditHeader:, vw_SAGE50UK_Account:, vw_SAGE50UK_Customer:	ExternalKey	SF_ERP_Salesforce_Clone_AUDIT_SPLIT, SF_ERP_Salesforce_Clone_AUDIT_HEADER

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

• 0 — GET USER
• 1 — Account
• 2 — Customer Master
• 3 — Customer Reverse Lookup Account
• 4 — Sage50 UK Address
• 5 — Sales Order Header
• 6 — Sales Order Details
• 7 — Invoice Header
• 8 — Invoice Details
• 9 — Product
• 10 — Item Master
• 11 — Item To Product Reverse Lookup
• 12 — Create Standard PriceBook
• 13 — Standard Pricebook Update
• 18 — Contacts
• 19 — Sage50 UK Audit Header
• 20 — Sage50 UK Audit Split

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_SAGE50UK_AuditHeader reads vw_SAGE50UK_Account:, vw_SAGE50UK_Customer:, vw_SAGE50UK_SalesOrderHeader:, vw_SAGE50UK_InvoiceHeader:
• vw_SAGE50UK_AuditSplit reads vw_SAGE50UK_AuditHeader:, vw_SAGE50UK_Account:, vw_SAGE50UK_Customer:
• vw_SAGE50UK_CustomerToAccountLookup reads vw_SAGE50UK_Customer:
• vw_SAGE50UK_Contact reads vw_SAGE50UK_Account:
• vw_SAGE50UK_Customer reads vw_SAGE50UK_Account:, vw_SAGE50UK_Address:
• vw_SAGE50UK_Address reads vw_SAGE50UK_Account:, vw_SAGE50UK_Customer:
• vw_SAGE50UK_Item reads vw_SAGE50UK_Product:
• vw_SAGE50UK_InvoiceHeader reads vw_SAGE50UK_Account:, vw_SAGE50UK_Customer:
• vw_SAGE50UK_InvoiceDetail reads vw_SAGE50UK_InvoiceHeader:, vw_SAGE50UK_Item:
• vw_SAGE50UK_StandardPriceBook reads vw_SAGE50UK_Product:
• vw_SAGE50UK_ProductStandardPricebookUpdate reads vw_SAGE50UK_StandardPriceBook:, vw_SAGE50UK_Product:
• vw_SAGE50UK_ItemToProductLookup reads vw_SAGE50UK_Item:
• vw_SAGE50UK_SalesOrderHeader reads vw_SAGE50UK_Account:, vw_SAGE50UK_Customer:
• vw_SAGE50UK_SalesOrderDetail reads vw_SAGE50UK_SalesOrderHeader:, vw_SAGE50UK_Item:

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	13	ACCOUNT_REF → CommercientSF__Commercient_ArCustomerCode__c, NAME → Name, ADDRESS_1, ADDRESS_2 → BillingStreet, ADDRESS_3 → BillingCity, ADDRESS_4 → BillingState
Customer Master	CommercientSF8__SAGE50UK_Customer__c	76	ACCOUNT_REF → CommercientSF8__ExternalKey__c, NAME → Name, STATUS_NUMBER → CommercientSF8__STATUS_NUMBER__c, DEPT_NUMBER → CommercientSF8__DEPT_NUMBER__c, CURRENCY → CommercientSF8__CURRENCY__c
Customer Reverse Lookup Account	Account	2	ACCOUNT_REF → CommercientSF__Commercient_ArCustomerCode__c, SFDCID → CommercientSF8__SAGE50UK_Customer__c
Sage50 UK Address	CommercientSF8__SAGE50UK_Address__c	26	REFERENCE → ExternalKey, ACCOUNT_REF → Account, ACCOUNT_REF → Customer, TAX_CODE → TAX_CODEN, ADDRESS_TYPE → ADDRESS_TYPE
Sales Order Header	CommercientSF8__SAGE50UK_SalesOrderHeader__c	93	ORDER_NUMBER → CommercientSF8__ExternalKey__c, ACCOUNT_REF → CommercientSF8__Account__c, ACCOUNT_REF → CommercientSF8__Customer__c, DESPATCH_STATUS_CODE → CommercientSF8__DESPATCH_STATUS_CODEN__c, ORDER_TYPE_CODE → CommercientSF8__ORDER_TYPE_CODEN__c
Sales Order Details	CommercientSF8__SAGE50UK_SalesOrderDetail__c	50	ORDER_NUMBER,ITEM_NUMBER,JOB_NUMBER → CommercientSF8__ExternalKey__c, ORDER_NUMBER,ITEM_NUMBER,JOB_NUMBER → CommercientSF8__Name__c, ORDER_NUMBER → CommercientSF8__Sales_Order_Header__c, SERVICE_FLAG → CommercientSF8__SERVICE_FLAGN__c, TAX_CODE_ID → CommercientSF8__TAX_CODE_IDN__c
Invoice Header	CommercientSF8__SAGE50UK_InvoiceHeader__c	93	INVOICE_NUMBER → CommercientSF8__ExternalKey__c, ACCOUNT_REF → Account, ACCOUNT_REF → Customer, INVOICE_TYPE_CODE → CommercientSF8__INVOICE_TYPE_CODE__c, GLOBAL_DEPT_NUMBER → CommercientSF8__GLOBAL_DEPT_NUMBER__c
Invoice Details	CommercientSF8__SAGE50UK_InvoiceDetail__c	44	INVOICE_NUMBER, ITEM_NUMBER → CommercientSF8__ExternalKey__c, SFDCID → CommercientSF8__Invoice_Header__c, SERVICE_FLAG → CommercientSF8__SERVICE_FLAG__c, TAX_CODE_ID → CommercientSF8__TAX_CODE_ID__c, ITEM_NUMBER → CommercientSF8__ITEM_NUMBER__c
Product	Product2	5	STOCK_CODE → CommercientSF__ExternalKey__c, STOCK_CODE → ProductCode, DESCRIPTION → Name, DESCRIPTION → Description, INACTIVE_FLAG → IsActive
Item Master	CommercientSF8__SAGE50UK_Item__c	92	STOCK_CODE → CommercientSF8__ExternalKey__c, WEB_DESCRIPTION → Name, SFDCID → Product, WEB_PUBLISH → WEB_PUBLISH, WEB_SPECIAL → WEB_SPECIAL
Item To Product Reverse Lookup	Product2	2	STOCK_CODE → CommercientSF__ExternalKey__c, SFDCID → CommercientSF8__SAGE50UK_Item__c
Create Standard PriceBook	PricebookEntry	5	STOCK_CODE → ExternalKey__c, SFDCID → Pricebook2Id, SFDCID → Product2ID, INACTIVE_FLAG → IsActive, SALES_PRICE → UnitPrice
Standard Pricebook Update	PricebookEntry	4	STOCK_CODE → ExternalKey__c, INACTIVE_FLAG → IsActive, SALES_PRICE → UnitPrice, SUPPLIER_PART_NUMBER → Ltr_Volume__c
Contacts	Contact	7	ACCOUNT_REF → CommercientSF8__ExternalKey__c, SFDCID → AccountID, CONTACT_NAME → LastName, CONTACT_NAME → FirstName, E_MAIL → Email
Sage50 UK Audit Header	CommercientSF8__SAGE50UK_AUDIT_HEADER__c	90	TRAN_NUMBER, ACCOUNT_REF, SALES_PURCHASE_REF, INV_REF → CommercientSF8__ExternalKey__c, TRAN_NUMBER, ACCOUNT_REF, SALES_PURCHASE_REF, INV_REF → CommercientSF8__Name__c, ACCOUNT_REF → CommercientSF8__Account__c, ACCOUNT_REF → CommercientSF8__Customer__c, SALES_PURCHASE_REF → CommercientSF8__Sales_Order_Header__c

6. Community templates

The catalogue carries 266 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: 266
• Default operations: insert on 266, update on 266, delete on 266
• Marked circular-sync: 2
• Licence groups they span: 12
• Destination objects: Account, Product2, PricebookEntry, CommercientSF8__SAGE50UK_InvoiceDetail__c, CommercientSF8__SAGE50UK_Customer__c, CommercientSF8__SAGE50UK_InvoiceHeader__c, CommercientSF8__SAGE50UK_SalesOrderDetail__c, CommercientSF8__SAGE50UK_SalesOrderHeader__c, CommercientSF8__SAGE50UK_Address__c, CommercientSF8__SAGE50UK_Item__c, Contact, CommercientSF8__SAGE50UK_AUDIT_HEADER__c, CommercientSF8__SAGE50UK_AUDIT_SPLIT__c, PriceBookEntry, Invoice__c, CommercientSF8_SAGE50UK_SalesReceipt__c, CommercientSF8__ACCOUNT__c, CommercientSF8__ACCOUNTMATCHING__c, CommercientSF8__SAGE50UK_PurchaseOrderDetail__c, CommercientSF8__SAGE50UK_PurchaseOrderHeader__c and 8 more
• Object display names: Account, Invoice Details, Invoice Header, Customer Reverse Lookup Account, Customer Master, Sage50 UK Address, Sales Order Details, Sales Order Header, Contacts, Item To Product Reverse Lookup, Product, Create Standard PriceBook, 36 more and 5 further templates
• Template groups: Account, Product, Invoice, Salesorder, Customer Multi Ship Addresses, Pricebook, CRM Quote and Line, CRM Opportunity and Line

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_SAGE50UK_AuditHeader
• vw_SAGE50UK_AuditSplit
• vw_SAGE50UK_User
• vw_SAGE50UK_Account
• vw_SAGE50UK_CustomerToAccountLookup
• vw_SAGE50UK_Contact
• vw_SAGE50UK_Customer
• vw_SAGE50UK_Address
• vw_SAGE50UK_Item
• vw_SAGE50UK_InvoiceHeader
• vw_SAGE50UK_InvoiceDetail
• vw_SAGE50UK_StandardPriceBook
• vw_ProductPriceBook
• vw_SAGE50UK_Product
• vw_SAGE50UK_ItemToProductLookup
• vw_SAGE50UK_SalesOrderHeader
• vw_SAGE50UK_SalesOrderDetail

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 UK → 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.