CRMPro → Salesforce — Sage 100 2014: what the shipped templates set up

CRMPro → Salesforce — Sage 100 2014: 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-100-2014.md, and that skill’s ERP table is what points at it. What follows is only what the shipped Sage 100 2014 → 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, Contact, CommercientSF8__AR_CUSTOMER__c, CommercientSF8__SAGE100_SalesPerson__c	SF_ERP_Salesforce_Clone_AR_CUSTOMER, SF_ERP_Salesforce_Clone_SO_SHIPTOADDRESS, SF_ERP_Salesforce_Clone_AR_CUSTOMERCONTACT, SF_ERP_Salesforce_Clone_AR_SALESPERSON
CRM Opportunity and Line	ERP SO_SALESORDERHEADER, SO_SALESORDERDETAIL data becomes Opportunity, OpportunityLineItem in Salesforce. New records are created and existing ones updated; none are deleted.	Opportunity, OpportunityLineItem	SF_ERP_Salesforce_Clone_SO_SALESORDERHEADER, CommercientFlags, SF_ERP_Salesforce_Clone_SO_SALESORDERDETAIL
CRM Order and Line	ERP AR_CUSTOMERCONTACT, SO_SALESORDERHEADER, SO_SALESORDERDETAIL data becomes Order, OrderItem in Salesforce. New records are created and existing ones updated; none are deleted.	Order, OrderItem	SF_ERP_Salesforce_Clone_SO_SALESORDERHEADER, SF_ERP_Salesforce_Clone_AR_CUSTOMERCONTACT, CommercientFlags, SF_ERP_Salesforce_Clone_SO_SALESORDERDETAIL
CRM Quote and Line	ERP SO_SALESORDERHEADER, SO_SALESORDERDETAIL data becomes Quote, QuoteLineItem in Salesforce. New records are created and existing ones updated; none are deleted.	Quote, QuoteLineItem	SF_ERP_Salesforce_Clone_SO_SALESORDERHEADER, CommercientFlags, SF_ERP_Salesforce_Clone_SO_SALESORDERDETAIL
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, SF_ERP_Salesforce_Clone_AR_CUSTOMER, SF_ERP_Salesforce_Clone_AR_OPENINVOICE, SF_ERP_Salesforce_Clone_AR_SALESPERSON, CommercientFlags, 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, CommercientSF8__SAGE100_SALESORDERHISTORYHEADER__c, CommercientSF8__SAGE100_SALESORDERHISTORYDETAIL__c	SF_ERP_Salesforce_Clone_SO_SALESORDERHEADER, SF_ERP_Salesforce_Clone_AR_CUSTOMER, CommercientFlags, SF_ERP_Salesforce_Clone_SO_SALESORDERDETAIL, SF_ERP_Salesforce_Clone_SO_SalesOrderHistoryHeader, SF_ERP_Salesforce_Clone_SO_SalesOrderHistoryDetail

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_SAGE1002014_User	1=0	'' / ''	1
Sales Person	CommercientSF8__SAGE100_SalesPerson__c	CommercientSF8__ExternalKey__c	1	vwSalesPerson	vw_SAGE1002014_SalesPerson	CommercientSF8__ / __C	1
Account	Account	CommercientSF__Commercient_ArCustomerCode__c	2	vw_SAGE1002014_Account	vw_SAGE1002014_Account	'' / ''	1
Contact	Contact	CommercientSF8__ExternalKey__c	3	vw_SAGE1002014_Contact	vw_SAGE1002014_Contact	'' / ''	1
Customer	CommercientSF8__AR_CUSTOMER__c	CommercientSF8__ExternalKey__c	3	vw_SAGE1002014_Customer	vw_SAGE1002014_Customer	CommercientSF8__ / __C	1
Address	CommercientSF8__SO_SHIPTOADDRESS__c	CommercientSF8__ExternalKey__c	4	vw_SAGE1002014_SO_SHIPTOADDRESS	vw_SAGE1002014_SO_SHIPTOADDRESS	CommercientSF8__ / __c	1
AccountCustomerLookup	Account	CommercientSF__Commercient_ArCustomerCode__c	5	vw_SAGE1002014_CustomerToAccountLookup	vw_SAGE1002014_CustomerToAccountLookup	'' / ''	1
SalesOrder	CommercientSF8__SO_SALESORDERHEADER__c	CommercientSF8__SALESORDERNO__c	8	vw_SAGE1002014_SalesOrderHeader	vw_SAGE1002014_SalesOrderHeader	CommercientSF8__ / __c	1
SalesOrderLine	CommercientSF8__SO_SALESORDERDETAIL__c	CommercientSF8__ExternalKey__c	9	vw_SAGE1002014_SalesOrderLine	vw_SAGE1002014_SalesOrderLine	CommercientSF8__ / __c	1
SalesOrder History Header	CommercientSF8__SAGE100_SALESORDERHISTORYHEADER__c	CommercientSF8__ExternalKey__c	10	vw_SAGE1002014_SalesOrderHistoryHeader	vw_SAGE1002014_SalesOrderHistoryHeader	CommercientSF8__ / __C	1
SalesOrder History Line	CommercientSF8__SAGE100_SALESORDERHISTORYDETAIL__c	CommercientSF8__ExternalKey__c	11	vw_SAGE1002014_SalesOrderHistoryLine	vw_SAGE1002014_SalesOrderHistoryLine	CommercientSF8__ / __C	1
Invoice Header	CommercientSF8__AR_INVOICEHISTORYHEADER__c	CommercientSF8__ExternalKey__c	12	vw_SAGE1002014_InvoiceHeader	vw_SAGE1002014_InvoiceHeader	CommercientSF8__ / __C	1
Invoice Details	CommercientSF8__AR_INVOICEHISTORYDETAIL__c	CommercientSF8__ExternalKey__c	13	vw_SAGE1002014_InvoiceLine	vw_SAGE1002014_InvoiceLine	CommercientSF8__ / __C	1
Opportunity Header	Opportunity	ExternalKey__c	21	vw_Opportunity_Header	vw_SAGE1002014_Opportunity_Header	'' / ''	1
Opportunity Line	OpportunityLineItem	ExternalKey__c	22	vw_Opportunity_Detail	vw_SAGE1002014_Opportunity_Line	'' / ''	1
Quote_Header	Quote	ExternalKey__c	23	vw_Quote_Header	vw_SAGE1002014_Quote_Header	'' / ''	1
Quote_LineItem	QuoteLineItem	ExternalKey__c	24	vw_Quote_Detail	vw_SAGE1002014_Quote_Line	'' / ''	1
Standard Order	Order	ExternalKey__c	45	vw_SAGE1002014_Standard_Order_Header	vw_SAGE1002014_Standard_Order_Header	'' / ''	1
Standard_Order_Line	OrderItem	ExternalKey__c	46	vw_SAGE1002014_Standard_Order_Line	vw_SAGE1002014_Standard_Order_Line	'' / ''	1
Standard Order Update	Order	ExternalKey__c	47	vw_SAGE1002014_Standard_Order_Header	vw_SAGE1002014_Standard_Order_Header_Update	'' / ''	1
Standard_Order_Line_Update	OrderItem	ExternalKey__c	48	vw_SAGE1002014_Standard_Order_Line	vw_SAGE1002014_Standard_Order_Line_Update	'' / ''	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, Account, Contact — those rows read records back from Salesforce as well as pushing. On Sales Person the SQL_Query names a view the same template’s CreateViewQuery does not create (vw_SAGE1002014_SalesPerson against vw_SAGE1002017_SalesPerson), so check the view exists under the name the row selects from before activating it.

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_SAGE1002017_SalesPerson	insert + update	vwSalesPerson:	—	ExternalKey	SF_ERP_Salesforce_Clone_AR_SALESPERSON
vw_SAGE1002014_Account	insert-only	vw_SAGE1002014_Account:	vw_SAGE1002014_User:	CommercientSF__Commercient_ArCustomerCode__c	SF_ERP_Salesforce_Clone_AR_CUSTOMER, SF_ERP_Salesforce_Clone_SO_SHIPTOADDRESS
vw_SAGE1002014_Contact	insert-only	vw_SAGE1002014_Contact:	vw_SAGE1002014_Customer:, vw_SAGE1002014_Account:	—	SF_ERP_Salesforce_Clone_AR_CUSTOMERCONTACT
vw_SAGE1002014_Customer	insert + update	vw_SAGE1002014_Customer:	vw_SAGE1002014_Account:, vwSalesPerson:	—	SF_ERP_Salesforce_Clone_AR_CUSTOMER
vw_SAGE1002014_SO_SHIPTOADDRESS	insert + update	vw_SAGE1002014_SO_SHIPTOADDRESS:	vw_SAGE1002014_Account:, vw_SAGE1002014_Customer:	ExternalKey	SF_ERP_Salesforce_Clone_SO_SHIPTOADDRESS
vw_SAGE1002014_CustomerToAccountLookup	insert + update	vw_SAGE1002014_CustomerToAccountLookup:	vw_SAGE1002014_Customer:	—	SF_ERP_Salesforce_Clone_AR_CUSTOMER
vw_SAGE1002014_SalesOrderHeader	insert + update	vw_SAGE1002014_SalesOrderHeader:	vw_SAGE1002014_Customer:, vw_SAGE1002014_Account:, vwSalesPerson:	—	SF_ERP_Salesforce_Clone_SO_SALESORDERHEADER, SF_ERP_Salesforce_Clone_AR_CUSTOMER, CommercientFlags
vw_SAGE1002014_SalesOrderLine	insert + update	vw_SAGE1002014_SalesOrderLine:	vw_SAGE1002014_SalesOrderHeader:, vw_SAGE1002014_CI_Item:	—	SF_ERP_Salesforce_Clone_SO_SALESORDERDETAIL, SF_ERP_Salesforce_Clone_SO_SALESORDERHEADER
vw_SAGE1002014_SalesOrderHistoryHeader	insert + update	vw_SAGE1002014_SalesOrderHistoryHeader:	vw_SAGE1002014_Customer:, vw_SAGE1002014_Account:	—	SF_ERP_Salesforce_Clone_SO_SalesOrderHistoryHeader, SF_ERP_Salesforce_Clone_AR_CUSTOMER, CommercientFlags
vw_SAGE1002014_SalesOrderHistoryLine	insert + update	vw_SAGE1002014_SalesOrderHistoryLine:	vw_SAGE1002014_SalesOrderHistoryHeader:, vw_SAGE1002014_CI_Item:	—	SF_ERP_Salesforce_Clone_SO_SalesOrderHistoryDetail, SF_ERP_Salesforce_Clone_SO_SalesOrderHistoryHeader, SF_ERP_Salesforce_Clone_AR_CUSTOMER
vw_SAGE1002014_InvoiceHeader	insert + update	vw_SAGE1002014_InvoiceHeader:	vw_SAGE1002014_Customer:, vw_SAGE1002014_Account:, vwSalesPerson:	—	SF_ERP_Salesforce_Clone_AR_INVOICEHISTORYHEADER, SF_ERP_Salesforce_Clone_AR_CUSTOMER, SF_ERP_Salesforce_Clone_AR_OPENINVOICE, SF_ERP_Salesforce_Clone_AR_SALESPERSON, CommercientFlags
vw_SAGE1002014_InvoiceLine	insert + update	vw_SAGE1002014_InvoiceLine:	vw_SAGE1002014_InvoiceHeader:, vw_SAGE1002014_CI_Item:	—	SF_ERP_Salesforce_Clone_AR_INVOICEHISTORYDETAIL, SF_ERP_Salesforce_Clone_AR_INVOICEHISTORYHEADER, SF_ERP_Salesforce_Clone_CI_ITEM
vw_SAGE1002014_Opportunity_Header	insert + update	vw_Opportunity_Header:	vw_SAGE1002014_Customer:, vw_SAGE1002014_Account:, vwSO_SALESORDERHEADER:, vwSalesPerson:	—	SF_ERP_Salesforce_Clone_SO_SALESORDERHEADER, CommercientFlags
vw_SAGE1002014_Opportunity_Line	insert-only	vw_Opportunity_Detail:	vw_Opportunity_Header:, vw_SAGE1002014_Product:, vw_SAGE1002014_PriceBookEntry:	—	SF_ERP_Salesforce_Clone_SO_SALESORDERDETAIL
vw_SAGE1002014_Quote_Header	insert + update	vw_Quote_Header:	vw_SAGE1002014_Customer:, vw_SAGE1002014_Account:, vw_Opportunity_Header:, vw_SAGE1002014_Terms:, vwSalesPerson:	—	SF_ERP_Salesforce_Clone_SO_SALESORDERHEADER, CommercientFlags
vw_SAGE1002014_Quote_Line	insert-only	vw_Quote_Detail:	vw_Quote_Header:, vw_SAGE1002014_Product:, vw_SAGE1002014_PriceBookEntry:	—	SF_ERP_Salesforce_Clone_SO_SALESORDERDETAIL, SF_ERP_Salesforce_Clone_SO_SALESORDERHEADER
vw_SAGE1002014_Standard_Order_Header	insert + update	vw_SAGE1002014_Standard_Order_Header:	vw_SAGE1002014_Account:, vw_SAGE1002014_Contact:, vw_Opportunity_Header:, vw_Quote_Header:	—	SF_ERP_Salesforce_Clone_SO_SALESORDERHEADER, SF_ERP_Salesforce_Clone_AR_CUSTOMERCONTACT, CommercientFlags
vw_SAGE1002014_Standard_Order_Line	insert + update	vw_SAGE1002014_Standard_Order_Line:	vw_SAGE1002014_Standard_Order_Header:, vw_SAGE1002014_Product:, vw_SAGE1002014_PriceBookEntry:, vw_Quote_Detail:	ExternalKey__c	SF_ERP_Salesforce_Clone_SO_SALESORDERDETAIL
vw_SAGE1002014_Standard_Order_Header_Update	insert + update	vw_SAGE1002014_Standard_Order_Header:	vw_SAGE1002014_Account:, vw_SAGE1002014_Contact:, vw_Opportunity_Header:, vw_Quote_Header:	—	SF_ERP_Salesforce_Clone_SO_SALESORDERHEADER, SF_ERP_Salesforce_Clone_AR_CUSTOMERCONTACT, CommercientFlags
vw_SAGE1002014_Standard_Order_Line_Update	insert + update	vw_SAGE1002014_Standard_Order_Line:	vw_SAGE1002014_Standard_Order_Header:, vw_SAGE1002014_Product:, vw_SAGE1002014_PriceBookEntry:, vw_Quote_Detail:	ExternalKey__c	SF_ERP_Salesforce_Clone_SO_SALESORDERDETAIL

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 48. 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 — Contact, Customer
• 4 — Address
• 5 — AccountCustomerLookup
• 8 — SalesOrder
• 9 — SalesOrderLine
• 10 — SalesOrder History Header
• 11 — SalesOrder History Line
• 12 — Invoice Header
• 13 — Invoice Details
• 21 — Opportunity Header
• 22 — Opportunity Line
• 23 — Quote_Header
• 24 — Quote_LineItem
• 45 — Standard Order
• 46 — Standard_Order_Line
• 47 — Standard Order Update
• 48 — Standard_Order_Line_Update

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_SAGE1002014_CustomerToAccountLookup reads vw_SAGE1002014_Customer:
• vw_SAGE1002014_Account reads vw_SAGE1002014_User:
• vw_SAGE1002014_Contact reads vw_SAGE1002014_Customer:, vw_SAGE1002014_Account:
• vw_SAGE1002014_Opportunity_Header reads vw_SAGE1002014_Customer:, vw_SAGE1002014_Account:, vwSO_SALESORDERHEADER:, vwSalesPerson:; no template in this set writes vwSO_SALESORDERHEADER:
• vw_SAGE1002014_Opportunity_Line reads vw_Opportunity_Header:, vw_SAGE1002014_Product:, vw_SAGE1002014_PriceBookEntry:; no template in this set writes vw_SAGE1002014_Product:, vw_SAGE1002014_PriceBookEntry:
• vw_SAGE1002014_Standard_Order_Header reads vw_SAGE1002014_Account:, vw_SAGE1002014_Contact:, vw_Opportunity_Header:, vw_Quote_Header:
• vw_SAGE1002014_Standard_Order_Line reads vw_SAGE1002014_Standard_Order_Header:, vw_SAGE1002014_Product:, vw_SAGE1002014_PriceBookEntry:, vw_Quote_Detail:; no template in this set writes vw_SAGE1002014_Product:, vw_SAGE1002014_PriceBookEntry:
• vw_SAGE1002014_Standard_Order_Header_Update reads vw_SAGE1002014_Account:, vw_SAGE1002014_Contact:, vw_Opportunity_Header:, vw_Quote_Header:
• vw_SAGE1002014_Standard_Order_Line_Update reads vw_SAGE1002014_Standard_Order_Header:, vw_SAGE1002014_Product:, vw_SAGE1002014_PriceBookEntry:, vw_Quote_Detail:; no template in this set writes vw_SAGE1002014_Product:, vw_SAGE1002014_PriceBookEntry:
• vw_SAGE1002014_Quote_Header reads vw_SAGE1002014_Customer:, vw_SAGE1002014_Account:, vw_Opportunity_Header:, vw_SAGE1002014_Terms:, vwSalesPerson:; no template in this set writes vw_SAGE1002014_Terms:
• vw_SAGE1002014_Quote_Line reads vw_Quote_Header:, vw_SAGE1002014_Product:, vw_SAGE1002014_PriceBookEntry:; no template in this set writes vw_SAGE1002014_Product:, vw_SAGE1002014_PriceBookEntry:
• vw_SAGE1002014_Customer reads vw_SAGE1002014_Account:, vwSalesPerson:
• vw_SAGE1002014_SO_SHIPTOADDRESS reads vw_SAGE1002014_Account:, vw_SAGE1002014_Customer:
• vw_SAGE1002014_InvoiceHeader reads vw_SAGE1002014_Customer:, vw_SAGE1002014_Account:, vwSalesPerson:
• vw_SAGE1002014_InvoiceLine reads vw_SAGE1002014_InvoiceHeader:, vw_SAGE1002014_CI_Item:; no template in this set writes vw_SAGE1002014_CI_Item:
• vw_SAGE1002014_SalesOrderHeader reads vw_SAGE1002014_Customer:, vw_SAGE1002014_Account:, vwSalesPerson:
• vw_SAGE1002014_SalesOrderLine reads vw_SAGE1002014_SalesOrderHeader:, vw_SAGE1002014_CI_Item:; no template in this set writes vw_SAGE1002014_CI_Item:
• vw_SAGE1002014_SalesOrderHistoryHeader reads vw_SAGE1002014_Customer:, vw_SAGE1002014_Account:
• vw_SAGE1002014_SalesOrderHistoryLine reads vw_SAGE1002014_SalesOrderHistoryHeader:, vw_SAGE1002014_CI_Item:; no template in this set writes vw_SAGE1002014_CI_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
Sales Person	CommercientSF8__SAGE100_SalesPerson__c	24	SALESPERSONDIVISIONNO,SALESPERSONNO → CommercientSF8__ExternalKey__c, SALESPERSONNAME → Name, SALESPERSONDIVISIONNO → SalespersonDivisionNo, SALESPERSONNO → SalespersonNo, ADDRESSLINE1 → ADDRESSLINE1
Address	CommercientSF8__SO_SHIPTOADDRESS__c	33	ARDIVISIONNO, CUSTOMERNO, SHIPTOCODE → CommercientSF8__ExternalKey__c, ARDIVISIONNO, CUSTOMERNO, SHIPTOCODE → Name, ARDIVISIONNO, CUSTOMERNO → Account, ARDIVISIONNO, CUSTOMERNO → CommercientSF8__Sage100_Customer_Records__c, ARDIVISIONNO → ARDIVISIONNO
AccountCustomerLookup	Account	2	ARDIVISIONNO, CUSTOMERNO → CommercientSF__Commercient_ArCustomerCode__c, SFDCID → CommercientSF8__Sage_Customer_Record__c
SalesOrderLine	CommercientSF8__SO_SALESORDERDETAIL__c	64	SALESORDERNO, LINEKEY → CommercientSF8__ExternalKey__c, SFDCID → CommercientSF8__Sage100_Open_Sales_Orders__c, SALESORDERNO, LINEKEY → Name, SALESORDERNO → CommercientSF8__SALESORDERNO__c, LINEKEY → CommercientSF8__LINEKEY__c
SalesOrder History Header	CommercientSF8__SAGE100_SALESORDERHISTORYHEADER__c	66	SALESORDERNO → CommercientSF8__ExternalKey__c, SALESORDERNO → Name, SFDCID → Account, SFDCID → Customer, ORDERSTATUS → OrderStatus
SalesOrder History Line	CommercientSF8__SAGE100_SALESORDERHISTORYDETAIL__c	50	SALESORDERNO, SEQUENCENO → CommercientSF8__ExternalKey__c, SALESORDERNO, SEQUENCENO → Name, SFDCID → CommercientSF8__Salesorder_History_Header__c, SEQUENCENO → CommercientSF8__SEQUENCENO__c, LINEKEY → CommercientSF8__LineKey__c
Invoice Header	CommercientSF8__AR_INVOICEHISTORYHEADER__c	88	INVOICENO, HEADERSEQNO → CommercientSF8__ExternalKey__c, INVOICENO, HEADERSEQNO → Name, ARDIVISIONNO, CUSTOMERNO → Account, ARDIVISIONNO, CUSTOMERNO → Sage100_Customer_Record, SALESPERSONDIVISIONNO, SALESPERSONNO → SalesPerson
Invoice Details	CommercientSF8__AR_INVOICEHISTORYDETAIL__c	60	INVOICENO, HEADERSEQNO, DETAILSEQNO → CommercientSF8__ExternalKey__c, INVOICENO, HEADERSEQNO, DETAILSEQNO → CommercientSF8__Name__c, SFDCID → CommercientSF8__Sage100_Invoice__c, SFDCID → CommercientSF8__Sage100_Item__c, INVOICENO → CommercientSF8__INVOICENO__c
Opportunity Header	Opportunity	7	SALESORDERNO → ExternalKey__c, SALESORDERNO → Name, SFDCID → AccountId, TAXABLEAMT → Amount, SFDCID → Pricebook2ID
Opportunity Line	OpportunityLineItem	6	SALESORDERNO, LINEKEY → ExternalKey__c, QUANTITYORDERED → Quantity__c, UNITPRICE → UnitPrice, ITEMCODEDESC → Description, SALESORDERNO → OpportunityId
Quote_Header	Quote	22	SALESORDERNO → ExternalKey__c, SALESORDERNO → Name, SALESORDERNO → OpportunityId, SALESPERSONDIVISIONNO,SALESPERSONNO → SAGE100_SalesPerson__c, TERMSCODE → SAGE100V5_Term__c
Quote_LineItem	QuoteLineItem	8	SALESORDERNO, LINEKEY → ExternalKey__c, SALESORDERNO → QuoteId, ITEMCODE → Product2Id, ITEMCODE → PricebookEntryId, PROMISEDATE → ServiceDate
Standard Order	Order	27	ARDIVISIONNO,SALESORDERNO → ExternalKey__c, CUSTOMERNO → AccountId, CONTACTCODE → BillToContactId, CONTACTCODE → ShipToContactId, SALESORDERNO → OpportunityId
Standard_Order_Line	OrderItem	12	SALESORDERNO, LINEKEY → ExternalKey__c, SALESORDERNO → OrderId, ITEMCODE → Product2Id, ITEMCODE → PricebookEntryId, SALESORDERNO, LINEKEY → QuoteLineItemId
Standard Order Update	Order	26	ARDIVISIONNO,SALESORDERNO → ExternalKey__c, CUSTOMERNO → AccountId, CONTACTCODE → BillToContactId, CONTACTCODE → ShipToContactId, SALESORDERNO → OpportunityId
Standard_Order_Line_Update	OrderItem	10	SALESORDERNO, LINEKEY → ExternalKey__c, SALESORDERNO → OrderId, SALESORDERNO, LINEKEY → QuoteLineItemId, ITEMCODEDESC → Description, EXPIRATIONDATE → EndDate

6. Community templates

The catalogue carries 16 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: 16
• Default operations: insert on 16, update on 16, delete on 16
• Marked circular-sync: 0
• Licence groups they span: 9
• Destination objects: Account, CommercientSF8__AR_CUSTOMER__c, CommercientSF8__AR_INVOICEHISTORYDETAIL__c, CommercientSF8__AR_INVOICEHISTORYHEADER__c, CommercientSF8__SAGE100_SALESORDERHISTORYDETAIL__c, CommercientSF8__SAGE100_SALESORDERHISTORYHEADER__c, CommercientSF8__SAGE100_SalesPerson__c, CommercientSF8__SO_SALESORDERDETAIL__c, CommercientSF8__SO_SALESORDERHEADER__c, CommercientSF8__SO_SHIPTOADDRESS__c, Contact, Opportunity, OpportunityLineItem, Quote, QuoteLineItem
• Object display names: Account, AccountCustomerLookup, Address, Contact, Customer, Invoice Details, Invoice Header, Opportunity Header, Opportunity Line, Quote_Header, Quote_LineItem, Sales Person and 4 more
• Template groups: Account, Salesorder, CRM Opportunity and Line, CRM Quote and Line, Invoice, 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_SAGE1002014_User
• vw_SAGE1002014_CustomerToAccountLookup
• vw_SAGE1002014_Account
• vw_SAGE1002014_Contact
• vw_Opportunity_Header
• vw_Opportunity_Detail
• vw_SAGE1002014_Standard_Order_Header
• vw_SAGE1002014_Standard_Order_Line
• vw_Quote_Header
• vw_Quote_Detail
• vw_SAGE1002014_Customer
• vw_SAGE1002014_SO_SHIPTOADDRESS
• vw_SAGE1002014_InvoiceHeader
• vw_SAGE1002014_InvoiceLine
• vw_SAGE1002014_SalesOrderHeader
• vw_SAGE1002014_SalesOrderLine
• vw_SAGE1002014_SalesOrderHistoryHeader
• vw_SAGE1002014_SalesOrderHistoryLine
• vwSalesPerson

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 100 2014 → 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.