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

CRMPro → Salesforce — Sage 200 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-200-uk.md, and that skill’s ERP table is what points at it. What follows is only what the shipped Sage 200 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
SYNC COLOUR	ERP PRODGROUPSEARCHCAT, PRODGROUPSEARCHVAL, PRODUCTGROUP data becomes SAGE200UK_Colour__c in Salesforce. New records are created and existing ones updated; none are deleted.	SAGE200UK_Colour__c	SF_ERP_Salesforce_Clone_ProductGroup, SF_ERP_Salesforce_Clone_stockitem, SF_ERP_Salesforce_Clone_ProdGroupSearchVal, SF_ERP_Salesforce_Clone_SearchValue, SF_ERP_Salesforce_Clone_ProdGroupSearchCat, SF_ERP_Salesforce_Clone_StockItemSearchCatVal
SYNC RANGE	ERP PRODGROUPSEARCHCAT, PRODGROUPSEARCHVAL, PRODUCTGROUP data becomes SAGE200UK_Range__c in Salesforce. New records are created and existing ones updated; none are deleted.	SAGE200UK_Range__c	SF_ERP_Salesforce_Clone_ProductGroup, SF_ERP_Salesforce_Clone_stockitem, SF_ERP_Salesforce_Clone_ProdGroupSearchCat, SF_ERP_Salesforce_Clone_SearchValue, SF_ERP_Salesforce_Clone_SearchCategory, SF_ERP_Salesforce_Clone_StockItemSearchCatVal
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__SAGE200UK_Customer__c	SF_ERP_Salesforce_Clone_SLCustomerAccount, SF_ERP_Salesforce_Clone_SLCustomerLocation, SF_ERP_Salesforce_Clone_custdeliveryaddress, SF_ERP_Salesforce_Clone_SLCustomerContact, SF_ERP_Salesforce_Clone_SLCustomerContactValue, SF_ERP_Salesforce_Clone_priceband
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__SAGE200UK_Address__c, CommercientSF8__SAGE200UK_CUSTDELIVERYADDRESS__c, CommercientSF8__SAGE200UK_SOPDOCDELADDRESS__c	SF_ERP_Salesforce_Clone_SLCustomerLocation, SF_ERP_Salesforce_Clone_custdeliveryaddress, SF_ERP_Salesforce_Clone_SOPDocDelAddress
Product	ERP STOCKITEM, WAREHOUSE, WAREHOUSEITEM data becomes CommercientSF8__SAGE200UK_Item__c, CommercientSF8__SAGE200UK_WAREHOUSE__c, CommercientSF8__SAGE200UK_WarehouseItem__c in Salesforce. New records are created and existing ones updated; none are deleted.	CommercientSF8__SAGE200UK_Item__c, CommercientSF8__SAGE200UK_WAREHOUSE__c, CommercientSF8__SAGE200UK_WarehouseItem__c, Product_Group__c, Product2	SF_ERP_Salesforce_Clone_stockitem, SF_ERP_Salesforce_Clone_warehouse, SF_ERP_Salesforce_Clone_warehouseitem, SF_ERP_Salesforce_Clone_ProductGroup
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__SAGE200UK_InvoiceHeader__c, CommercientSF8__SAGE200UK_InvoiceDetail__c	SF_ERP_Salesforce_Clone_sopinvoicecredit, SF_ERP_Salesforce_Clone_SLPostedCustomerTran, CommercientFlags, SF_ERP_Salesforce_Clone_sopinvoicecreditline, SF_ERP_Salesforce_Clone_stockitem
Pricebook	ERP PRICEBAND, STOCKITEM, STOCKITEMPRICE data becomes Pricebook2, PricebookEntry, PriceBookEntry in Salesforce. New records are created and existing ones updated; none are deleted.	Pricebook2, PricebookEntry, PriceBookEntry	SF_ERP_Salesforce_Clone_priceband, SF_ERP_Salesforce_Clone_stockitem, SF_ERP_Salesforce_Clone_stockitemprice
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__SAGE200UK_SalesOrderHeader__c, CommercientSF8__SAGE200UK_SalesOrderDetail__c	SF_ERP_Salesforce_Clone_soporderreturn, SF_ERP_Salesforce_Clone_warehouse, SF_ERP_Salesforce_Clone_soporderreturnline, SF_ERP_Salesforce_Clone_stockitem

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_SAGE200UK_User	1=0	'' / ''	1
SYNC PRICEBAND	Pricebook2	ExternalKey__c	0	vw_SAGE200UK_priceband	vw_SAGE200UK_priceband	'' / ''	—
Account	Account	CommercientSF__Commercient_ArCustomerCode__c	1	vwAccount	vw_SAGE200UK_Account	'' / ''	—
Address	CommercientSF8__SAGE200UK_Address__c	CommercientSF8__ExternalKey__c	2	vw_SAGE200UK_Address	vw_SAGE200UK_Address	CommercientSF8__ / __c	—
Contacts	Contact	ExternalKey__c	3	vw_SAGE200UK_Contacts	vw_SAGE200UK_Contacts	'' / ''	1
Customer	CommercientSF8__SAGE200UK_Customer__c	CommercientSF8__ExternalKey__c	3	vw_SAGE200UK_Customer	vw_SAGE200UK_Customer	CommercientSF8__ / __c	—
Account Reverse lookup	Account	CommercientSF__Commercient_ArCustomerCode__c	4	AccountReverseLookup	vw_SAGE200UK_AccountReverseLookup	'' / ''	—
SYNC CUSTDELIVERYADDRESS	CommercientSF8__SAGE200UK_CUSTDELIVERYADDRESS__c	CommercientSF8__ExternalKey__c	4	vw_SAGE200UK_custdeliveryaddress	vw_SAGE200UK_custdeliveryaddress	CommercientSF8__ / __c	—
SYNC COLOUR	SAGE200UK_Colour__c	ExternalKey__c	5	vw_SAGE200UK_Colour	vw_SAGE200UK_Colour	'' / __c	—
SYNC RANGE	SAGE200UK_Range__c	ExternalKey__c	5	vw_SAGE200UK_Range	vw_SAGE200UK_Range	'' / __c	—
SYNC PRODUCTGROUP	Product_Group__c	ExternalKey__c	5	vw_SAGE200UK_ProductGroup	vw_SAGE200UK_ProductGroup	'' / __c	—
Product	Product2	CommercientSF__ExternalKey__c	5	Product2	vw_SAGE200UK_Product	'' / ''	—
SYNC SOPDOCDELADDRESS	CommercientSF8__SAGE200UK_SOPDOCDELADDRESS__c	CommercientSF8__ExternalKey__c	6	vw_SAGE200UK_SOPDocDelAddress	vw_SAGE200UK_SOPDocDelAddress	CommercientSF8__ / __c	—
Price Book Entry Create	PricebookEntry	ExternalKey__c	6	PricebookEntry	vw_SAGE200UK_ProductPriceBookCreate	'' / ''	—
Price Book Entry Update	PriceBookEntry	ExternalKey__c	7	PriceBookEntry	vw_SAGE200UK_ProductPriceBookUpdate	'' / ''	—
Item Master	CommercientSF8__SAGE200UK_Item__c	CommercientSF8__ExternalKey__c	8	vw_SAGE200UK_Item	vw_SAGE200UK_Item	CommercientSF8__ / __c	—
SYNC WAREHOUSE	CommercientSF8__SAGE200UK_WAREHOUSE__c	CommercientSF8__ExternalKey__c	9	vw_SAGE200UK_warehouse	vw_SAGE200UK_warehouse	CommercientSF8__ / __c	—
Item Warehouse	CommercientSF8__SAGE200UK_WarehouseItem__c	CommercientSF8__ExternalKey__c	10	vw_SAGE200UK_WarehouseItem	vw_SAGE200UK_WarehouseItem	CommercientSF8__ / __c	—
Item Reverse lookup	Product2	CommercientSF__ExternalKey__c	11	ItemReverseLookup	vw_SAGE200UK_ItemReverseLookup	'' / ''	—
Sales Order	CommercientSF8__SAGE200UK_SalesOrderHeader__c	CommercientSF8__ExternalKey__c	12	vw_SAGE200UK_SalesOrderHeader	vw_SAGE200UK_SalesOrderHeader	CommercientSF8__ / __c	—
Sales Order Line	CommercientSF8__SAGE200UK_SalesOrderDetail__c	CommercientSF8__ExternalKey__c	13	vw_SAGE200UK_SalesOrderDetail	vw_SAGE200UK_SalesOrderDetail	CommercientSF8__ / __c	—
Invoice	CommercientSF8__SAGE200UK_InvoiceHeader__c	CommercientSF8__ExternalKey__c	14	vw_SAGE200UK_InvoiceHeader	vw_SAGE200UK_InvoiceHeader	CommercientSF8__ / __c	—
Invoice Line	CommercientSF8__SAGE200UK_InvoiceDetail__c	CommercientSF8__ExternalKey__c	15	vw_SAGE200UK_InvoiceDetail	vw_SAGE200UK_InvoiceDetail	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_Active_Delete_Records 0, Sync_Batch_Size 200. Is_Create_Fields is set on Price Book Entry Create; Is_Active_Get_Records is set on Price Book Entry Create; 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, Price Book Entry Create — 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_SAGE200UK_priceband	insert + update	vw_SAGE200UK_priceband:	—	—	SF_ERP_Salesforce_Clone_priceband
vw_SAGE200UK_Account	insert + update	vwAccount:	—	—	SF_ERP_Salesforce_Clone_SLCustomerAccount, SF_ERP_Salesforce_Clone_SLCustomerLocation, SF_ERP_Salesforce_Clone_custdeliveryaddress
vw_SAGE200UK_Address	insert-only	vw_SAGE200UK_Address:	vwAccount:	ExternalKey	SF_ERP_Salesforce_Clone_SLCustomerLocation
vw_SAGE200UK_Customer	insert-only	vw_SAGE200UK_Customer:	vw_SAGE200UK_Address:, vwAccount:	ExternalKey	SF_ERP_Salesforce_Clone_SLCustomerAccount, SF_ERP_Salesforce_Clone_priceband, SF_ERP_Salesforce_Clone_SLCustomerContact, SF_ERP_Salesforce_Clone_SLCustomerContactValue, SF_ERP_Salesforce_Clone_SLCustomerLocation
vw_SAGE200UK_AccountReverseLookup	insert + update	AccountReverseLookup:	vw_SAGE200UK_Customer:	—	SF_ERP_Salesforce_Clone_SLCustomerAccount
vw_SAGE200UK_custdeliveryaddress	insert + update	vw_SAGE200UK_custdeliveryaddress:	vwAccount:	—	SF_ERP_Salesforce_Clone_custdeliveryaddress
vw_SAGE200UK_Colour		vw_SAGE200UK_Colour:	—	—	SF_ERP_Salesforce_Clone_ProductGroup, SF_ERP_Salesforce_Clone_stockitem, SF_ERP_Salesforce_Clone_ProdGroupSearchVal, SF_ERP_Salesforce_Clone_SearchValue, SF_ERP_Salesforce_Clone_ProdGroupSearchCat
vw_SAGE200UK_Range	insert + update	vw_SAGE200UK_Range:	—	—	SF_ERP_Salesforce_Clone_ProductGroup, SF_ERP_Salesforce_Clone_stockitem, SF_ERP_Salesforce_Clone_ProdGroupSearchCat, SF_ERP_Salesforce_Clone_SearchValue, SF_ERP_Salesforce_Clone_SearchCategory
vw_SAGE200UK_ProductGroup	insert + update	vw_SAGE200UK_ProductGroup:	—	—	SF_ERP_Salesforce_Clone_ProductGroup
vw_SAGE200UK_Product	insert + update	Product2:	—	CommercientSF__ExternalKey__c	SF_ERP_Salesforce_Clone_stockitem, SF_ERP_Salesforce_Clone_ProductGroup
vw_SAGE200UK_SOPDocDelAddress	insert + update	vw_SAGE200UK_SOPDocDelAddress:	vw_SAGE200UK_SalesOrderHeader:	—	SF_ERP_Salesforce_Clone_SOPDocDelAddress
vw_SAGE200UK_ProductPriceBookCreate	insert-only	PriceBookEntry:	vw_SAGE200UK_priceband:, Product2:	ExternalKey__c	SF_ERP_Salesforce_Clone_stockitem, SF_ERP_Salesforce_Clone_stockitemprice, SF_ERP_Salesforce_Clone_priceband
vw_SAGE200UK_ProductPriceBookUpdate	insert + update	PriceBookEntry:	Product2:	ExternalKey__c	SF_ERP_Salesforce_Clone_stockitem, SF_ERP_Salesforce_Clone_stockitemprice, SF_ERP_Salesforce_Clone_priceband
vw_SAGE200UK_Item	insert-only	vw_SAGE200UK_Item:	Product2:, vw_SAGE200UK_ProductGroup:, vw_SAGE200UK_Colour:, vw_SAGE200UK_Range:	ExternalKey	SF_ERP_Salesforce_Clone_stockitem
vw_SAGE200UK_warehouse	insert + update	vw_SAGE200UK_warehouse:	—	—	SF_ERP_Salesforce_Clone_warehouse
vw_SAGE200UK_WarehouseItem	insert-only	vw_SAGE200UK_WarehouseItem:	Product2:, vw_SAGE200UK_Item:, vw_SAGE200UK_warehouse:	ExternalKey	SF_ERP_Salesforce_Clone_warehouseitem, SF_ERP_Salesforce_Clone_warehouse, SF_ERP_Salesforce_Clone_stockitem
vw_SAGE200UK_ItemReverseLookup	insert + update	ItemReverseLookup:	vw_SAGE200UK_Item:	—	SF_ERP_Salesforce_Clone_stockitem
vw_SAGE200UK_SalesOrderHeader	insert-only	vw_SAGE200UK_SalesOrderHeader:	vw_SAGE200UK_Customer:, vwAccount:, vw_SAGE200UK_warehouse:	ExternalKey	SF_ERP_Salesforce_Clone_soporderreturn, SF_ERP_Salesforce_Clone_warehouse
vw_SAGE200UK_SalesOrderDetail	insert-only	vw_SAGE200UK_SalesOrderDetail:	vw_SAGE200UK_Item:, vw_SAGE200UK_ProductGroup:, vw_SAGE200UK_Colour:, vw_SAGE200UK_Range:, vw_SAGE200UK_SalesOrderHeader:	ExternalKey	SF_ERP_Salesforce_Clone_soporderreturnline, SF_ERP_Salesforce_Clone_stockitem
vw_SAGE200UK_InvoiceHeader	insert-only	vw_SAGE200UK_InvoiceHeader:	vw_SAGE200UK_Customer:, vwAccount:	ExternalKey	SF_ERP_Salesforce_Clone_sopinvoicecredit, SF_ERP_Salesforce_Clone_SLPostedCustomerTran, CommercientFlags
vw_SAGE200UK_InvoiceDetail	insert-only	vw_SAGE200UK_InvoiceDetail:	vw_SAGE200UK_Item:, vw_SAGE200UK_ProductGroup:, vw_SAGE200UK_Colour:, vw_SAGE200UK_Range:, vw_SAGE200UK_InvoiceHeader:	ExternalKey	SF_ERP_Salesforce_Clone_sopinvoicecreditline, SF_ERP_Salesforce_Clone_stockitem

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

• 0 — GET USER, SYNC PRICEBAND
• 1 — Account
• 2 — Address
• 3 — Contacts, Customer
• 4 — Account Reverse lookup, SYNC CUSTDELIVERYADDRESS
• 5 — SYNC COLOUR, SYNC RANGE, SYNC PRODUCTGROUP, Product
• 6 — SYNC SOPDOCDELADDRESS, Price Book Entry Create
• 7 — Price Book Entry Update
• 8 — Item Master
• 9 — SYNC WAREHOUSE
• 10 — Item Warehouse
• 11 — Item Reverse lookup
• 12 — Sales Order
• 13 — Sales Order Line
• 14 — Invoice
• 15 — Invoice Line

Several of these rows share a Sync_Order value: each template group carries its own numbering, so give the imported processes an order across the whole set rather than taking the template values as one.

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_SAGE200UK_AccountReverseLookup reads vw_SAGE200UK_Customer:
• Contacts reads Contacts:; no template in this set writes Contacts:
• vw_SAGE200UK_Customer reads vw_SAGE200UK_Address:, vwAccount:
• vw_SAGE200UK_Address reads vwAccount:
• vw_SAGE200UK_custdeliveryaddress reads vwAccount:
• vw_SAGE200UK_SOPDocDelAddress reads vw_SAGE200UK_SalesOrderHeader:
• vw_SAGE200UK_Item reads Product2:, vw_SAGE200UK_ProductGroup:, vw_SAGE200UK_Colour:, vw_SAGE200UK_Range:
• vw_SAGE200UK_WarehouseItem reads Product2:, vw_SAGE200UK_Item:, vw_SAGE200UK_warehouse:
• vw_SAGE200UK_InvoiceHeader reads vw_SAGE200UK_Customer:, vwAccount:
• vw_SAGE200UK_InvoiceDetail reads vw_SAGE200UK_Item:, vw_SAGE200UK_ProductGroup:, vw_SAGE200UK_Colour:, vw_SAGE200UK_Range:, vw_SAGE200UK_InvoiceHeader:
• vw_SAGE200UK_ProductPriceBookCreate reads vw_SAGE200UK_priceband:, Product2:
• vw_SAGE200UK_ProductPriceBookUpdate reads Product2:
• vw_SAGE200UK_ItemReverseLookup reads vw_SAGE200UK_Item:
• vw_SAGE200UK_SalesOrderHeader reads vw_SAGE200UK_Customer:, vwAccount:, vw_SAGE200UK_warehouse:
• vw_SAGE200UK_SalesOrderDetail reads vw_SAGE200UK_Item:, vw_SAGE200UK_ProductGroup:, vw_SAGE200UK_Colour:, vw_SAGE200UK_Range:, vw_SAGE200UK_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 PRICEBAND	Pricebook2	5	PriceBandID → ExternalKey__c, Name → Name, Description → Description, OpLock → OpLock, IsActive → IsActive
Account	Account	10	SLCustomerAccountID → CommercientSF__Commercient_ArCustomerCode__c, CustomerAccountName → Name, AddressLine1, AddressLine2, AddressLine3 → BillingStreet, City → BillingCity, Country → BillingCountry
Address	CommercientSF8__SAGE200UK_Address__c	14	AddressLine1 → AddressLine1, AddressLine2 → AddressLine2, AddressLine3 → AddressLine3, AddressLine4 → AddressLine4, PostCode → PostCode
Contacts	Contact	19	RecordNumber → RecordNumber, CustomerID → CustomerID, LastName → LastName, MiddleName → MiddleName, FirstName → FirstName
Customer	CommercientSF8__SAGE200UK_Customer__c	105	SLCustomerLocationID → CommercientSF8__Address__c, CustomerAccountName → Name, SLCustomerAccountID → CommercientSF8__Account__c, SLCustomerAccountID → CommercientSF8__ExternalKey__c, CustomerAccountNumber → CustomerAccountNumber
Account Reverse lookup	Account	2	SLCustomerAccountID → CommercientSF__Commercient_ArCustomerCode__c, SFDCID → SAGE200UK_Customer__c
SYNC CUSTDELIVERYADDRESS	CommercientSF8__SAGE200UK_CUSTDELIVERYADDRESS__c	19	CustDeliveryAddressID → CommercientSF8__ExternalKey__c, Description → CommercientSF8__Name__c, AddressLine1 → CommercientSF8__AddressLine1__c, AddressLine2 → CommercientSF8__AddressLine2__c, AddressLine3 → CommercientSF8__AddressLine3__c
SYNC COLOUR	SAGE200UK_Colour__c	4	Code → ExternalKey__c, Name → Desc, Name → Name, OpLock → OpLock
SYNC RANGE	SAGE200UK_Range__c	5	Code → ExternalKey__c, OpLock → TimeStamp, Name → Desc, Name → Range, Description → Description
SYNC PRODUCTGROUP	Product_Group__c	34	ProductGroupID → ExternalKey__c, Description → Name, Code → Code, UseDescriptionOnDocs → UseDescriptionOnDocs, StockItemTypeID → StockItemTypeID
Product	Product2	5	Code → CommercientSF__ExternalKey__c, Name → Name, Code → ProductCode, StockItemStatusID → IsActive, Description → Description
SYNC SOPDOCDELADDRESS	CommercientSF8__SAGE200UK_SOPDOCDELADDRESS__c	19	SOPOrderReturnID → CommercientSF8__SAGE200UK_SalesOrderHeader__c, SOPDocDelAddressID → CommercientSF8__ExternalKey__c, Description → Name, PostalName → PostalName, AddressLine1 → AddressLine1
Price Book Entry Create	PricebookEntry	4	Code, PriceBandID → ExternalKey__c, IsActive → IsActive, Price → UnitPrice, Code → Product2ID
Price Book Entry Update	PriceBookEntry	3	Code → ExternalKey__c, IsActive → IsActive, Price → UnitPrice
Item Master	CommercientSF8__SAGE200UK_Item__c	76	Code → CommercientSF8__Product__c, StockItemStatusID → CurrentStatus, ProductGroupID → Product_Group__c, Code → SAGE200UK_Colour__c, Code → SAGE200UK_Range__c
SYNC WAREHOUSE	CommercientSF8__SAGE200UK_WAREHOUSE__c	36	WarehouseID → CommercientSF8__ExternalKey__c, Name → Name, Description → Description, UseForSalesTrading → UseForSalesTrading, PostalName → PostalName
Item Warehouse	CommercientSF8__SAGE200UK_WarehouseItem__c	27	WarehouseID → CommercientSF8__SAGE200UK_Warehouse__c, ItemID → CommercientSF8__Product__c, ItemID → CommercientSF8__Item__c, WarehouseItemID → Name, WarehouseItemID → ExternalKey
Item Reverse lookup	Product2	2	Code → CommercientSF__ExternalKey__c, SFDCID → CommercientSF8__SAGE200UK_Item__c
Sales Order	CommercientSF8__SAGE200UK_SalesOrderHeader__c	100	CustomerID → CommercientSF8__Customer__c, CustomerID → CommercientSF8__Account__c, WarehouseID → SAGE200UK_Warehouse__c, SOPOrderReturnID → Name, WarehouseID → WarehouseName
Sales Order Line	CommercientSF8__SAGE200UK_SalesOrderDetail__c	102	SOPOrderReturnID → CommercientSF8__SalesOrderHeader__c, ItemCode → SAGE200UK_Colour__c, ItemCode → ItemCode, NominalAccountRef → NominalAccountRef, NominalCostCentre → NominalCostCentre
Invoice	CommercientSF8__SAGE200UK_InvoiceHeader__c	54	CustomerID → CommercientSF8__Customer__c, CustomerID → CommercientSF8__Account__c, DocumentStatusID → DocumentStatus__c, SOPInvoiceCreditTypeID → InvoiceCreditTypeName__c, SOPInvoiceCreditID → Name
Invoice Line	CommercientSF8__SAGE200UK_InvoiceDetail__c	28	SOPInvoiceCreditID → CommercientSF8__InvoiceHeader__c, PrintSequenceNumber,SOPInvoiceCreditLineID → CommercientSF8__ExternalKey__c, DespatchReceiptNos → DespatchReceiptNos, UserName → UserName, OrderReturnNo → OrderReturnNo

6. Community templates

The catalogue carries 114 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: 114
• Default operations: insert on 114, update on 114, delete on 114
• Marked circular-sync: 2
• Licence groups they span: 12
• Destination objects: Account, CommercientSF8__SAGE200UK_Address__c, CommercientSF8__SAGE200UK_Customer__c, CommercientSF8__SAGE200UK_InvoiceDetail__c, CommercientSF8__SAGE200UK_InvoiceHeader__c, CommercientSF8__SAGE200UK_SalesOrderDetail__c, CommercientSF8__SAGE200UK_SalesOrderHeader__c, Contact, Product2, SAGE200UK_OpenARInvoiceHeader__c, PriceBookEntry, CommercientSF8__SAGE200UK_Item__c, CommercientSF8__SAGE200UK_WAREHOUSE__c, CommercientSF8__SAGE200UK_WarehouseItem__c, Pricebook2, CommercientSF8__ACCOUNT__c, CommercientSF8__SAGE200UK_CUSTDELIVERYADDRESS__c, CommercientSF8__SAGE200UK_SOPDOCDELADDRESS__c, CommercientSF8_SAGE200UK_InvoiceDetail__c, Pricebookentry, 5 more and 15 custom objects
• Object display names: Account, Account Reverse lookup, Customer, Address, Invoice, Invoice Line, Sales Order Line, Sales Order, Contact, Sage200UK Open AR_Invoice Header, Contacts, Item Master, 26 more and 13 further templates
• Template groups: Account, Invoice, Salesorder, Product, Customer Multi Ship Addresses, Open AR Invoice Header, Purchase Order

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_SAGE200UK_Colour
• vw_SAGE200UK_Range
• vw_SAGE200UK_User
• vwAccount
• AccountReverseLookup
• vw_SAGE200UK_Contacts
• vw_SAGE200UK_Customer
• vw_SAGE200UK_Address
• vw_SAGE200UK_custdeliveryaddress
• vw_SAGE200UK_SOPDocDelAddress
• vw_SAGE200UK_Item
• vw_SAGE200UK_warehouse
• vw_SAGE200UK_WarehouseItem
• vw_SAGE200UK_InvoiceHeader
• vw_SAGE200UK_InvoiceDetail
• vw_SAGE200UK_priceband
• PricebookEntry
• PriceBookEntry
• vw_SAGE200UK_ProductGroup
• Product2
• ItemReverseLookup
• vw_SAGE200UK_SalesOrderHeader
• vw_SAGE200UK_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 200 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.