CRMPro → Salesforce — SouthWare: what the shipped templates set up

CRMPro → Salesforce — SouthWare: 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/southware.md, and that skill’s ERP table is what points at it. What follows is only what the shipped SouthWare → 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 Salesforce Users	The templates push User to Salesforce. New records are created, existing ones updated, and records removed in the ERP are deleted.	User	—
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, CommercientSF40__RCUST__c, CommercientSF40__RSMAN__c	SF_ERP_Salesforce_Clone_SWBARCUST, SF_ERP_Salesforce_Clone_SWBARSHIP, SF_ERP_Salesforce_Clone_SWBARSMAN
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, existing ones updated, and records removed in the ERP are deleted.	CommercientSF40__RSHIP__c	SF_ERP_Salesforce_Clone_SWBARSHIP
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, existing ones updated, and records removed in the ERP are deleted.	CommercientSF40__SHST1__c, CommercientSF40__SHST2__c, CommercientSF40__SHST4__c	SF_ERP_Salesforce_Clone_SWBASHST1, CommercientFlags, SF_ERP_Salesforce_Clone_SWBASHST2, SF_ERP_Salesforce_Clone_SHST4, SF_ERP_Salesforce_Clone_SHST1
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, existing ones updated, and records removed in the ERP are deleted.	CommercientSF40__SBIL1__c, CommercientSF40__SBIL2__c	SF_ERP_Salesforce_Clone_SWBASBIL1, CommercientFlags, SF_ERP_Salesforce_Clone_SWBASBIL2

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 Salesforce Users	User	CommercientSF6__SalespersonCode__c	0	vw_SOUTHWARE_GetUser	1=0	'' / ''	1
SOUTHWARE SalesPerson Sync	CommercientSF40__RSMAN__c	CommercientSF40__ExternalKey__c	1	vw_SOUTHWARE_SalesPerson	vw_SOUTHWARE_SalesPerson	CommercientSF40__ / __c	1
SOUTHWARE Customer Sync	CommercientSF40__RCUST__c	CommercientSF40__ExternalKey__c	3	vw_SOUTHWARE_Customer	vw_SOUTHWARE_Customer	CommercientSF40__ / __c	1
Account Reverse Lookup Sync	Account	CommercientSF__Commercient_ArCustomerCode__c	4	vw_SOUTHWARE_AccountReverseLookup	vw_SOUTHWARE_AccountReverseLookup	'' / ''	1
SOUTHWARE Ship To Address Sync	CommercientSF40__RSHIP__c	CommercientSF40__ExternalKey__c	4	vw_SOUTHWARE_ShipToAddress	vw_SOUTHWARE_ShipToAddress	CommercientSF40__ / __c	1
SOUTHWARE Salesorder Header Sync	CommercientSF40__SBIL1__c	CommercientSF40__ExternalKey__c	5	vw_SOUTHWARE_SalesOrderHeader	vw_SOUTHWARE_SalesOrderHeader	CommercientSF40__ / __c	1
SOUTHWARE Salesorder Line Sync	CommercientSF40__SBIL2__c	CommercientSF40__ExternalKey__c	6	vw_SOUTHWARE_SalesOrderLine	vw_SOUTHWARE_SalesOrderLine	CommercientSF40__ / __c	1
SOUTHWARE Invoice Header Sync	CommercientSF40__SHST1__c	CommercientSF40__ExternalKey__c	7	vw_SOUTHWARE_InvoiceHeader	vw_SOUTHWARE_InvoiceHeader	CommercientSF40__ / __c	1
SOUTHWARE Invoice Line Sync	CommercientSF40__SHST2__c	CommercientSF40__ExternalKey__c	8	vw_SOUTHWARE_InvoiceLine	vw_SOUTHWARE_InvoiceLine	CommercientSF40__ / __c	1
SOUTHWARE Invoice Payment Sync	CommercientSF40__SHST4__c	CommercientSF40__ExternalKey__c	9	vw_SOUTHWARE_InvoicePayment	vw_SOUTHWARE_InvoicePayment	CommercientSF40__ / __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, IsAccountMatching False, 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 Salesforce Users — 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_SOUTHWARE_Account	insert + update	—	vw_SOUTHWARE_SalesPerson:, vw_SOUTHWARE_GetUser:, vw_SOUTHWARE_Account:	—	SF_ERP_Salesforce_Clone_SWBARCUST, SF_ERP_Salesforce_Clone_SWBARSHIP
vw_SOUTHWARE_SalesPerson	insert + update	vw_SOUTHWARE_SalesPerson:	—	ExternalKey	SF_ERP_Salesforce_Clone_SWBARSMAN
vw_SOUTHWARE_Customer	insert + update	vw_SOUTHWARE_Customer:	vw_SOUTHWARE_SalesPerson:, vw_SOUTHWARE_Account:	ExternalKey	SF_ERP_Salesforce_Clone_SWBARCUST
vw_SOUTHWARE_AccountReverseLookup	insert + update	vw_SOUTHWARE_AccountReverseLookup:	vw_SOUTHWARE_Customer:, vw_SOUTHWARE_Account:	—	SF_ERP_Salesforce_Clone_SWBARCUST
vw_SOUTHWARE_ShipToAddress	insert + update	vw_SOUTHWARE_ShipToAddress:	vw_SOUTHWARE_SalesPerson:, vw_SOUTHWARE_Account:, vw_SOUTHWARE_Customer:	ExternalKey	SF_ERP_Salesforce_Clone_SWBARSHIP
vw_SOUTHWARE_SalesOrderHeader	insert + update	vw_SOUTHWARE_SalesOrderHeader:	vw_SOUTHWARE_Account:, vw_SOUTHWARE_Customer:	ExternalKey	SF_ERP_Salesforce_Clone_SWBASBIL1, CommercientFlags
vw_SOUTHWARE_SalesOrderLine	insert + update	vw_SOUTHWARE_SalesOrderLine:	vw_SOUTHWARE_SalesOrderHeader:	ExternalKey	SF_ERP_Salesforce_Clone_SWBASBIL2
vw_SOUTHWARE_InvoiceHeader	insert + update	vw_SOUTHWARE_InvoiceHeader:	vw_SOUTHWARE_Account:, vw_SOUTHWARE_Customer:	ExternalKey	SF_ERP_Salesforce_Clone_SWBASHST1, CommercientFlags
vw_SOUTHWARE_InvoiceLine	insert + update	vw_SOUTHWARE_InvoiceLine:	vw_SOUTHWARE_InvoiceHeader:	ExternalKey	SF_ERP_Salesforce_Clone_SWBASHST2
vw_SOUTHWARE_InvoicePayment	insert + update	vw_SOUTHWARE_InvoicePayment:	vw_SOUTHWARE_Account:, vw_SOUTHWARE_Customer:, vw_SOUTHWARE_InvoiceHeader:	ExternalKey	SF_ERP_Salesforce_Clone_SHST4, SF_ERP_Salesforce_Clone_SHST1

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

• 0 — Get Salesforce Users
• 1 — SOUTHWARE SalesPerson Sync
• 3 — SOUTHWARE Customer Sync
• 4 — Account Reverse Lookup Sync, SOUTHWARE Ship To Address Sync
• 5 — SOUTHWARE Salesorder Header Sync
• 6 — SOUTHWARE Salesorder Line Sync
• 7 — SOUTHWARE Invoice Header Sync
• 8 — SOUTHWARE Invoice Line Sync
• 9 — SOUTHWARE Invoice Payment Sync

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_SOUTHWARE_Account reads vw_SOUTHWARE_SalesPerson:, vw_SOUTHWARE_GetUser:, vw_SOUTHWARE_Account:; no template in this set writes vw_SOUTHWARE_Account:
• vw_SOUTHWARE_AccountReverseLookup reads vw_SOUTHWARE_Customer:, vw_SOUTHWARE_Account:; no template in this set writes vw_SOUTHWARE_Account:
• vw_SOUTHWARE_Customer reads vw_SOUTHWARE_SalesPerson:, vw_SOUTHWARE_Account:; no template in this set writes vw_SOUTHWARE_Account:
• vw_SOUTHWARE_ShipToAddress reads vw_SOUTHWARE_SalesPerson:, vw_SOUTHWARE_Account:, vw_SOUTHWARE_Customer:; no template in this set writes vw_SOUTHWARE_Account:
• vw_SOUTHWARE_InvoiceHeader reads vw_SOUTHWARE_Account:, vw_SOUTHWARE_Customer:; no template in this set writes vw_SOUTHWARE_Account:
• vw_SOUTHWARE_InvoiceLine reads vw_SOUTHWARE_InvoiceHeader:
• vw_SOUTHWARE_InvoicePayment reads vw_SOUTHWARE_Account:, vw_SOUTHWARE_Customer:, vw_SOUTHWARE_InvoiceHeader:; no template in this set writes vw_SOUTHWARE_Account:
• vw_SOUTHWARE_SalesOrderHeader reads vw_SOUTHWARE_Account:, vw_SOUTHWARE_Customer:; no template in this set writes vw_SOUTHWARE_Account:
• vw_SOUTHWARE_SalesOrderLine reads vw_SOUTHWARE_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
Account Sync	Account	15	CommercientSFommercient_ArCustomerCode → CommercientSF__Commercient_ArCustomerCode__c, Phone → Phone, Type → Type, BillingStreet → BillingStreet, BillingCity → BillingCity
SOUTHWARE SalesPerson Sync	CommercientSF40__RSMAN__c	41	salespersonnumber → CommercientSF40__salespersonnumber__c, salespersonname → CommercientSF40__salespersonname__c, salespersoninitials → CommercientSF40__salespersoninitials__c, territory → CommercientSF40__territory__c, commisssalesptd → CommercientSF40__commisssalesptd__c
SOUTHWARE Customer Sync	CommercientSF40__RCUST__c	76	groupnumber → CommercientSF40__groupnumber__c, customernumber → CommercientSF40__customernumber__c, salespersonnumber → CommercientSF40__salespersonnumber__c, customername → CommercientSF40__customername__c, addressline1 → CommercientSF40__addressline1__c
Account Reverse Lookup Sync	Account	2	CommercientSFommercient_ArCustomerCode → CommercientSF__Commercient_ArCustomerCode__c, CommercientSF40__SouthWare_Customer → CommercientSF40__SouthWare_Customer__c
SOUTHWARE Ship To Address Sync	CommercientSF40__RSHIP__c	28	customernumber → CommercientSF40__customernumber__c, shiptonumber → CommercientSF40__shiptonumber__c, shiptoname → CommercientSF40__shiptoname__c, shiptoaddress1 → CommercientSF40__shiptoaddress1__c, shiptoaddress2 → CommercientSF40__shiptoaddress2__c
SOUTHWARE Salesorder Header Sync	CommercientSF40__SBIL1__c	93	Account → CommercientSF40__account__c, SouthWare_RCUST → CommercientSF40__southware_rcust__c, amount_1 → CommercientSF40__amount_1__c, appldeposoverride → CommercientSF40__appldeposoverride__c, araccount → CommercientSF40__araccount__c
SOUTHWARE Salesorder Line Sync	CommercientSF40__SBIL2__c	86	ordernumber → CommercientSF40__ordernumber__c, linenumber → CommercientSF40__linenumber__c, itemtypecdisr → CommercientSF40__itemtypecdisr__c, itemidstocksvc → CommercientSF40__itemidstocksvc__c, locationnumber → CommercientSF40__locationnumber__c
SOUTHWARE Invoice Header Sync	CommercientSF40__SHST1__c	106	Account → CommercientSF40__account__c, RCUST → CommercientSF40__rcust__c, acctsrecacctno → CommercientSF40__acctsrecacctno__c, applytonumber → CommercientSF40__applytonumber__c, billtoaddr3 → CommercientSF40__billtoaddr3__c
SOUTHWARE Invoice Line Sync	CommercientSF40__SHST2__c	72	invoicenumber → CommercientSF40__invoicenumber__c, linenumber → CommercientSF40__linenumber__c, invoicedate → CommercientSF40__invoicedate__c, customernumber → CommercientSF40__customernumber__c, lineitemcdisr → CommercientSF40__lineitemcdisr__c
SOUTHWARE Invoice Payment Sync	CommercientSF40__SHST4__c	40	InvoiceNumber → InvoiceNumber, Sequence → Sequence, ReceivedDate → ReceivedDate, Operator → CommercientSF40__Operator__c, Location → Location

6. Community templates

The catalogue carries 31 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: 31
• Default operations: insert on 31, update on 31, delete on 31
• Marked circular-sync: 0
• Licence groups they span: 11
• Destination objects: Account, CommercientSF40__RCUST__c, CommercientSF40__RSHIP__c, CommercientSF40__RSMAN__c, CommercientSF40__SBIL1__c, CommercientSF40__SBIL2__c, CommercientSF40__SHST1__c, CommercientSF40__SHST2__c, Opportunity, PricebookEntry, User, CommercientSF40__SHST4__c, Contact, ContentDocument, product2 and 2 custom objects
• Object display names: Account Reverse Lookup Sync, Account Sync, Get Salesforce Users, SOUTHWARE Customer Sync, SOUTHWARE Invoice Header Sync, SOUTHWARE Invoice Line Sync, SOUTHWARE Salesorder Header Sync, SOUTHWARE Salesorder Line Sync, SOUTHWARE SalesPerson Sync, SOUTHWARE Ship To Address Sync, Account Sync Update, Opportunity Sync and 9 more
• Template groups: Account, Invoice, Product, Salesorder, CRM Opportunity and Line, 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_SOUTHWARE_GetUser
• vw_SOUTHWARE_AccountReverseLookup
• vw_SOUTHWARE_Customer
• vw_SOUTHWARE_ShipToAddress
• vw_SOUTHWARE_InvoiceHeader
• vw_SOUTHWARE_InvoiceLine
• vw_SOUTHWARE_InvoicePayment
• vw_SOUTHWARE_SalesOrderHeader
• vw_SOUTHWARE_SalesOrderLine
• vw_SOUTHWARE_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 SouthWare → 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.