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

CRMPro → Salesforce — Sage 300: 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-300.md, and that skill’s ERP table is what points at it. What follows is only what the shipped Sage 300 → 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, Contacts, CommercientSF8__SAGE300_Customer__c, CommercientSF8__SAGE300_SalesRep__c	SF_ERP_Salesforce_Clone_ARCUS, SF_ERP_Salesforce_Clone_ARCSP
AR Invoice Payments	Commercient Syncs the payment details that are held in the receivables file and held against an invoice in the ERP. The amount received from a customer, the date of payment, the method of payment, whether partial or full payment, etc New records are created and existing ones updated; none are deleted.	CommercientSF8__SAGE300_InvoicePayment__c	SF_ERP_Salesforce_Clone_ARTCP, SF_ERP_Salesforce_Clone_ARIBH, SF_ERP_Salesforce_Clone_ARTCR
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__SAGE300V1_INVOICEHEADER__c, CommercientSF8__SAGE300V1_INVOICELINE__c, CommercientSF8__AROBP__c	SF_ERP_Salesforce_Clone_ARIBH, CommercientFlags, SF_ERP_Salesforce_Clone_ARIBD, SF_ERP_Salesforce_Clone_ARIBDO, SF_ERP_Salesforce_Clone_AROBP
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__SAGE300_SalesOrderHeader__c, CommercientSF8__SAGE300_SalesOrderLine__c	SF_ERP_Salesforce_Clone_OEORDH, CommercientFlags, SF_ERP_Salesforce_Clone_OEORDD

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_SAGE300_User	1=0	'' / ''	1
SAGE300 SalesPerson	CommercientSF8__SAGE300_SalesRep__c	CommercientSF8__ExternalKey__c	2	vw_SAGE300_SalesPerson:	vw_SAGE300_SalesPerson	CommercientSF8__ / __c	1
Parent Account	Account	CommercientSF__Commercient_ArCustomerCode__c	3	vw_SAGE300_Account:	vw_SAGE300_Account	'' / ''	1
Child Account	Account	CommercientSF__Commercient_ArCustomerCode__c	4	vw_SAGE300_Account:	vw_SAGE300_ChildAccount	'' / ''	1
SAGE300 Customer	CommercientSF8__SAGE300_Customer__c	CommercientSF8__ExternalKey__c	5	vw_SAGE300_Customer:	vw_SAGE300_Customer	CommercientSF8__ / __c	1
Contacts	Contacts	Commercient_ExternalKey	6	vw_SAGE300_Contacts:	vw_SAGE300_Contacts	'' / ''	1
SAGE300 SalesOrderHeader	CommercientSF8__SAGE300_SalesOrderHeader__c	CommercientSF8__ExternalKey__c	8	vw_SAGE300_SalesOrderHeader:	vw_SAGE300_SalesOrderHeader	CommercientSF8__ / __c	1
SAGE300 SalesOrderDetail	CommercientSF8__SAGE300_SalesOrderLine__c	CommercientSF8__ExternalKey__c	9	vw_SAGE300_SalesOrderDetail:	vw_SAGE300_SalesOrderDetail	CommercientSF8__ / __c	1
Invoice Header	CommercientSF8__SAGE300V1_INVOICEHEADER__c	CommercientSF8__ExternalKey__c	10	vw_SAGE300_InvoiceHeader	vw_SAGE300_InvoiceHeader	CommercientSF8__ / __c	1
Invoice Line	CommercientSF8__SAGE300V1_INVOICELINE__c	CommercientSF8__ExternalKey__c	11	vw_SAGE300_InvoiceLine	vw_SAGE300_InvoiceLine	CommercientSF8__ / __c	1
Invoice Payment	CommercientSF8__SAGE300_InvoicePayment__c	CommercientSF8__ExternalKey__c	12	vw_SAGE300_InvoicePayment	vw_SAGE300_InvoicePayment	CommercientSF8__ / __c	1
Invoice Document Payment	CommercientSF8__AROBP__c	CommercientSF8__ExternalKey__c	13	vw_SAGE300_InvoiceDocumentPayment	vw_SAGE300_InvoiceDocumentPayment	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, Contacts — those rows read records back from Salesforce as well as pushing. On SAGE300 SalesPerson the SQL_Query names a view the same template’s CreateViewQuery does not create (vw_SAGE300_SalesPerson against vw_SAGE300_Account), 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_SAGE300_Account	insert + update	—	vw_SAGE300_User:, vw_SAGE300_SalesPerson:, vw_SAGE300_Account:	—	SF_ERP_Salesforce_Clone_ARCUS, SF_ERP_Salesforce_Clone_ARCSP
vw_SAGE300_Account	insert + update	—	vw_SAGE300_User:, vw_SAGE300_SalesPerson:, vw_SAGE300_Account:	CommercientSF__Commercient_ArCustomerCode__c	SF_ERP_Salesforce_Clone_ARCUS, SF_ERP_Salesforce_Clone_ARCSP
vw_SAGE300_ChildAccount	insert + update	—	vw_SAGE300_User:, vw_SAGE300_Account:	CommercientSF__Commercient_ArCustomerCode__c	SF_ERP_Salesforce_Clone_ARCSP, SF_ERP_Salesforce_Clone_ARCUS
vw_SAGE300_Customer	insert-only	—	vw_SAGE300_Account:, vw_SAGE300_Customer:	ExternalKey	SF_ERP_Salesforce_Clone_ARCUS
vw_SAGE300_Contacts	insert + update	—	vw_SAGE300_Account:, vw_SAGE300_Customer:, vw_SAGE300_Contacts:	ExternalKey, Commercient_ExternalKey	SF_ERP_Salesforce_Clone_ARCUS
vw_SAGE300_SalesOrderHeader	insert-only	—	vw_SAGE300_Account:, vw_SAGE300_Customer:, vw_SAGE300_SalesOrderHeader:	ExternalKey	SF_ERP_Salesforce_Clone_OEORDH, CommercientFlags
vw_SAGE300_SalesOrderDetail	insert-only	—	vw_SAGE300_SalesOrderHeader:, vw_SAGE300_Item:, vw_SAGE300_Product:, vw_SAGE300_SalesOrderDetail:	ExternalKey	SF_ERP_Salesforce_Clone_OEORDD
vw_SAGE300_InvoiceHeader	insert + update	vw_SAGE300_InvoiceHeader:	vw_SAGE300_Account:, vw_SAGE300_Customer:	—	SF_ERP_Salesforce_Clone_ARIBH, CommercientFlags
vw_SAGE300_InvoiceLine	insert + update	vw_SAGE300_InvoiceLine:	vw_SAGE300_InvoiceHeader:, UpdateInvoiceLineExternalKey:	—	SF_ERP_Salesforce_Clone_ARIBD, SF_ERP_Salesforce_Clone_ARIBDO
vw_SAGE300_InvoicePayment	insert + update	vw_SAGE300_InvoicePayment:	vw_SAGE300_Account:, vw_SAGE300_Customer:, vw_SAGE300_InvoiceHeader:	—	SF_ERP_Salesforce_Clone_ARTCP, SF_ERP_Salesforce_Clone_ARIBH, SF_ERP_Salesforce_Clone_ARTCR
vw_SAGE300_InvoiceDocumentPayment	insert + update	vw_SAGE300_InvoiceDocumentPayment:	vw_SAGE300_Account:, vw_SAGE300_Customer:, vw_SAGE300_InvoiceHeader:	—	SF_ERP_Salesforce_Clone_AROBP, SF_ERP_Salesforce_Clone_ARIBH

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

• 0 — GET USER
• 2 — SAGE300 SalesPerson
• 3 — Parent Account
• 4 — Child Account
• 5 — SAGE300 Customer
• 6 — Contacts
• 8 — SAGE300 SalesOrderHeader
• 9 — SAGE300 SalesOrderDetail
• 10 — Invoice Header
• 11 — Invoice Line
• 12 — Invoice Payment
• 13 — Invoice Document Payment

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_SAGE300_Account reads vw_SAGE300_User:, vw_SAGE300_SalesPerson:, vw_SAGE300_Account:; no template in this set writes vw_SAGE300_SalesPerson:, vw_SAGE300_Account:
• vw_SAGE300_ChildAccount reads vw_SAGE300_User:, vw_SAGE300_Account:; no template in this set writes vw_SAGE300_Account:
• vw_SAGE300_InvoicePayment reads vw_SAGE300_Account:, vw_SAGE300_Customer:, vw_SAGE300_InvoiceHeader:; no template in this set writes vw_SAGE300_Account:, vw_SAGE300_Customer:
• vw_SAGE300_Contacts reads vw_SAGE300_Account:, vw_SAGE300_Customer:, vw_SAGE300_Contacts:; no template in this set writes vw_SAGE300_Account:, vw_SAGE300_Customer:, vw_SAGE300_Contacts:
• vw_SAGE300_Customer reads vw_SAGE300_Account:, vw_SAGE300_Customer:; no template in this set writes vw_SAGE300_Account:, vw_SAGE300_Customer:
• vw_SAGE300_InvoiceHeader reads vw_SAGE300_Account:, vw_SAGE300_Customer:; no template in this set writes vw_SAGE300_Account:, vw_SAGE300_Customer:
• vw_SAGE300_InvoiceLine reads vw_SAGE300_InvoiceHeader:, UpdateInvoiceLineExternalKey:; no template in this set writes UpdateInvoiceLineExternalKey:
• vw_SAGE300_InvoiceDocumentPayment reads vw_SAGE300_Account:, vw_SAGE300_Customer:, vw_SAGE300_InvoiceHeader:; no template in this set writes vw_SAGE300_Account:, vw_SAGE300_Customer:
• vw_SAGE300_SalesOrderHeader reads vw_SAGE300_Account:, vw_SAGE300_Customer:, vw_SAGE300_SalesOrderHeader:; no template in this set writes vw_SAGE300_Account:, vw_SAGE300_Customer:, vw_SAGE300_SalesOrderHeader:
• vw_SAGE300_SalesOrderDetail reads vw_SAGE300_SalesOrderHeader:, vw_SAGE300_Item:, vw_SAGE300_Product:, vw_SAGE300_SalesOrderDetail:; no template in this set writes vw_SAGE300_SalesOrderHeader:, vw_SAGE300_Item:, vw_SAGE300_Product:, vw_SAGE300_SalesOrderDetail:
• vw_SAGE300_Account reads vw_SAGE300_User:, vw_SAGE300_SalesPerson:, vw_SAGE300_Account:; no template in this set writes vw_SAGE300_SalesPerson:, vw_SAGE300_Account:

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
SAGE300 SalesPerson	CommercientSF8__SAGE300_SalesRep__c	12	IDCUST → CommercientSF__Commercient_ArCustomerCode__c, NAMECUST → Name, TEXTSTRE1, TEXTSTRE2, TEXTSTRE3 → BillingStreet, NAMECITY → BillingCity, CODESTTE → BillingState
Parent Account	Account	13	IDCUST → CommercientSF__Commercient_ArCustomerCode__c, NAMECUST → Name, TEXTSTRE1, TEXTSTRE2, TEXTSTRE3 → BillingStreet, NAMECITY → BillingCity, CODESTTE → BillingState
Child Account	Account	7	IDCUST, IDCUSTSHPT → CommercientSF__Commercient_ArCustomerCode__c, NAMECUST, IDCUSTSHPT → Name, TEXTSTRE1, TEXTSTRE2, TEXTSTRE3, TEXTSTRE4 → ShippingStreet, NAMECITY → ShippingCity, CODESTTE → ShippingState
SAGE300 Customer	CommercientSF8__SAGE300_Customer__c	2	IDCUST → CommercientSF8__ExternalKey__c, NAMECUST → Name
Contacts	Contacts	9	Account_Name → Account_Name, Sage300_Customer → Sage300_Customer, Commercient_ExternalKey → Commercient_ExternalKey, Last_Name → Last_Name, First_Name → First_Name
SAGE300 SalesOrderHeader	CommercientSF8__SAGE300_SalesOrderHeader__c	175	ORDUNIQ → CommercientSF8__ExternalKey__c, ORDUNIQ → Name, CUSTOMER → CommercientSF8__Account__c, CUSTOMER → CommercientSF8__Customer__c, AUDTDATE → CommercientSF8__AUDTDATE__c
SAGE300 SalesOrderDetail	CommercientSF8__SAGE300_SalesOrderLine__c	3	ORDUNIQ, LINENUM → CommercientSF8__ExternalKey__c, ORDUNIQ, LINENUM → Name, ORDUNIQ → Sales_Order_Header
Invoice Header	CommercientSF8__SAGE300V1_INVOICEHEADER__c	100	CNTBTCH,CNTITEM → CommercientSF8__ExternalKey__c, IDINVC → Name, IDCUST → Account, IDCUST → Customer, AUDTUSER → AUDTUSER
Invoice Line	CommercientSF8__SAGE300V1_INVOICELINE__c	86	CNTBTCH,CNTITEM,CNTLINE → CommercientSF8__ExternalKey__c, CNTBTCH,CNTITEM,CNTLINE → Name, SFDCID → CommercientSF8__Invoice_Header__c, AUDTUSER → AUDTUSER, AUDTORG → AUDTORG
Invoice Payment	CommercientSF8__SAGE300_InvoicePayment__c	82	IDINVC → CommercientSF8__ExternalKey__c, IDINVC → CommercientSF8__Name__c, ARVERSION → CommercientSF8__ARVERSION__c, IDACCTSET → CommercientSF8__IDACCTSET__c, IDBANK → CommercientSF8__IDBANK__c
Invoice Document Payment	CommercientSF8__AROBP__c	43	IDCUST,CNTPAYMNBR,IDRMIT,DATEBUS,TRANSTYPE,CNTSEQNCE → CommercientSF8__ExternalKey__c, IDCUST,IDINVC,CNTPAYMNBR,IDRMIT,DATEBUS,TRANSTYPE,CNTSEQNCE → CommercientSF8__Name__c, IDCUST → CommercientSF8__IDCUST__c, IDINVC → CommercientSF8__IDINVC__c, CNTPAYMNBR → CommercientSF8__CNTPAYMNBR__c

6. Community templates

The catalogue carries 254 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: 254
• Default operations: insert on 254, update on 254, delete on 254
• Marked circular-sync: 2
• Licence groups they span: 13
• Destination objects: Account, CommercientSF8__SAGE300_Customer__c, Product2, CommercientSF8__SAGE300V1_INVOICELINE__c, CommercientSF8__SAGE300V1_INVOICEHEADER__c, PriceBookEntry, CommercientSF8__SAGE300_SalesRep__c, CommercientSF8__SAGE300_SalesOrderHeader__c, CommercientSF8__SAGE300_SalesOrderLine__c, CommercientSF8__SAGE300_InvoicePayment__c, CommercientSF8__SAGE300_ShipToAddress__c, CommercientSF8__AROBP__c, User, CommercientSF8__SAGE300_InvoiceHeader__c, CommercientSF8__SAGE300_InvoiceLine__c, CommercientSF8__SAGE300_Terms__c, Contacts, CommercientSF8__SAGE300_SalesHistoryDetail__c, Contact, Inventory__c, 17 more and 12 custom objects
• Object display names: Invoice Header, Invoice Line, SAGE300 Customer, Account, Child Account, Contacts, Invoice Document Payment, Parent Account, SAGE300 SalesOrderDetail, SAGE300 SalesOrderHeader, SAGE300 SalesPerson, SYNC ITEM TO PRODUCT LOOKUP, 87 more and 32 further templates
• Template groups: Account, Product, Invoice, Salesorder, Customer Multi Ship Addresses, CRM Opportunity and Line, CRM Ownership

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_SAGE300_User
• vw_SAGE300_Account:
• vw_SAGE300_InvoicePayment
• vw_SAGE300_Contacts:
• vw_SAGE300_Customer:
• vw_SAGE300_InvoiceHeader
• vw_SAGE300_InvoiceLine
• vw_SAGE300_InvoiceDocumentPayment
• vw_SAGE300_SalesOrderHeader:
• vw_SAGE300_SalesOrderDetail:
• vw_SAGE300_SalesPerson:

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