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

CRMPro → Salesforce — JobBOSS: 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/jobboss.md, and that skill’s ERP table is what points at it. What follows is only what the shipped JobBOSS → 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 Owners	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, Contact, CommercientSF19__JobBoss_Customer__c, CommercientSF19__JobBoss_Employee__c	SF_ERP_Salesforce_Clone_Address, SF_ERP_Salesforce_Clone_Customer, BA, SA, SF_ERP_Salesforce_Clone_Contact, SF_ERP_Salesforce_Clone_Employee
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.	CommercientSF19__JobBoss_Address__c	SF_ERP_Salesforce_Clone_Address
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.	CommercientSF19__JobBoss_Invoice_Header__c, CommercientSF19__JobBoss_Invoice_Detail__c	SF_ERP_Salesforce_Clone_Invoice_Header, CommercientFlags, SF_ERP_Salesforce_Clone_Invoice_Detail
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.	CommercientSF19__JobBoss_SO_Header__c, CommercientSF19__JobBoss_SO_Detail__c	SF_ERP_Salesforce_Clone_SO_Header, CommercientFlags, SF_ERP_Salesforce_Clone_SO_Detail

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 Owners	User	CommercientSF6__SalespersonCode__c	0	vw_EPICOR10_Owners	1=0	'' / ''	1
JobBoss Salesperson	CommercientSF19__JobBoss_Employee__c	CommercientSF19__ExternalKey__c	1	vw_JOBBOSS_Salesperson	vw_JOBBOSS_Salesperson	CommercientSF19__ / __c	—
Accounts	Account	CommercientSF__Commercient_ArCustomerCode__c	2	vw_JOBBOSS_Account	vw_JOBBOSS_Account	'' / ''	—
SYNC ACCOUNT	Account	CommercientSF__Commercient_ArCustomerCode__c	2	vw_JOBBOSS_Account	vw_JOBBOSS_Account	'' / ''	1
JobBoss Customer	CommercientSF19__JobBoss_Customer__c	CommercientSF19__ExternalKey__c	4	vw_JOBBOSS_Customer	vw_JOBBOSS_Customer	CommercientSF19__ / __c	—
JobBoss Customer To Account Reverse Lookup	Account	CommercientSF__Commercient_ArCustomerCode__c	5	vw_JOBBOSS_CustomerToAccountLookup	vw_JOBBOSS_CustomerToAccountLookup	'' / ''	—
JobBoss Address	CommercientSF19__JobBoss_Address__c	CommercientSF19__ExternalKey__c	6	vw_JOBBOSS_Address	vw_JOBBOSS_Address	CommercientSF19__ / __c	—
JobBoss CONTACT	Contact	ExternalKey__c	7	vw_JOBBOSS_Contact	vw_JOBBOSS_Contact	'' / ''	1
JobBoss SalesOrderHeader	CommercientSF19__JobBoss_SO_Header__c	CommercientSF19__ExternalKey__c	7	vw_JOBBOSS_SalesOrderHeader	vw_JOBBOSS_SalesOrderHeader	CommercientSF19__ / __c	—
JobBoss SalesOrderDetail	CommercientSF19__JobBoss_SO_Detail__c	CommercientSF19__ExternalKey__c	8	vw_JOBBOSS_SalesOrderDetail	vw_JOBBOSS_SalesOrderDetail	CommercientSF19__ / __c	—
JobBoss InvoiceHeader	CommercientSF19__JobBoss_Invoice_Header__c	CommercientSF19__ExternalKey__c	9	vw_JOBBOSS_InvoiceHeader	vw_JOBBOSS_InvoiceHeader	CommercientSF19__ / __c	—
JobBoss InvoiceDetail	CommercientSF19__JobBoss_Invoice_Detail__c	CommercientSF19__ExternalKey__c	10	vw_JOBBOSS_InvoiceDetail	vw_JOBBOSS_InvoiceDetail	CommercientSF19__ / __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_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 Owners — 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_JOBBOSS_Salesperson	insert + update	vw_JOBBOSS_Salesperson:	—	—	SF_ERP_Salesforce_Clone_Employee
vw_JOBBOSS_Account	insert + update	—	vw_Salesperson:, vw_Account:	—	SF_ERP_Salesforce_Clone_Address, SF_ERP_Salesforce_Clone_Customer, BA, SA
vw_JOBBOSS_Account	insert + update	vw_JOBBOSS_Account:	vw_JOBBOSS_SalesPerson:, vw_JOBBOSS_User:	—	SF_ERP_Salesforce_Clone_Address, SF_ERP_Salesforce_Clone_Customer, BA, SA
vw_JOBBOSS_Customer	insert + update	vw_JOBBOSS_Customer:	vw_JOBBOSS_Account:, vw_JOBBOSS_SalesPerson:	—	SF_ERP_Salesforce_Clone_Customer
vw_JOBBOSS_CustomerToAccountLookup	insert + update	vw_JOBBOSS_CustomerToAccountLookup:	vw_JOBBOSS_Customer:	—	SF_ERP_Salesforce_Clone_Customer
vw_JOBBOSS_Address	insert + update	vw_JOBBOSS_Address:	vw_JOBBOSS_Account:, vw_JOBBOSS_Customer:	—	SF_ERP_Salesforce_Clone_Address
vw_JOBBOSS_Contact	insert + update	vw_JOBBOSS_Contact:	vw_JOBBOSS_Account:, vw_JOBBOSS_Customer:	ExternalKey__c	SF_ERP_Salesforce_Clone_Contact
vw_JOBBOSS_SalesOrderHeader	insert + update	vw_JOBBOSS_SalesOrderHeader:	vw_JOBBOSS_Account:, vw_JOBBOSS_Customer:	—	SF_ERP_Salesforce_Clone_SO_Header, CommercientFlags
vw_JOBBOSS_SalesOrderDetail	insert + update	vw_JOBBOSS_SalesOrderDetail:	vw_JOBBOSS_SalesOrderHeader:	—	SF_ERP_Salesforce_Clone_SO_Detail
vw_JOBBOSS_InvoiceHeader	insert + update	vw_JOBBOSS_InvoiceHeader:	vw_JOBBOSS_Account:, vw_JOBBOSS_Customer:	—	SF_ERP_Salesforce_Clone_Invoice_Header, CommercientFlags
vw_JOBBOSS_InvoiceDetail	insert + update	vw_JOBBOSS_InvoiceDetail:	vw_JOBBOSS_InvoiceHeader:	—	SF_ERP_Salesforce_Clone_Invoice_Detail

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

• 0 — Get Owners
• 1 — JobBoss Salesperson
• 2 — Accounts, SYNC ACCOUNT
• 4 — JobBoss Customer
• 5 — JobBoss Customer To Account Reverse Lookup
• 6 — JobBoss Address
• 7 — JobBoss CONTACT, JobBoss SalesOrderHeader
• 8 — JobBoss SalesOrderDetail
• 9 — JobBoss InvoiceHeader
• 10 — JobBoss InvoiceDetail

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_JOBBOSS_Account reads vw_Salesperson:, vw_Account:; no template in this set writes vw_Salesperson:, vw_Account:
• vw_JOBBOSS_CustomerToAccountLookup reads vw_JOBBOSS_Customer:
• vw_JOBBOSS_Account reads vw_JOBBOSS_SalesPerson:, vw_JOBBOSS_User:; no template in this set writes vw_JOBBOSS_User:
• vw_JOBBOSS_Contact reads vw_JOBBOSS_Account:, vw_JOBBOSS_Customer:
• vw_JOBBOSS_Customer reads vw_JOBBOSS_Account:, vw_JOBBOSS_SalesPerson:
• vw_JOBBOSS_Address reads vw_JOBBOSS_Account:, vw_JOBBOSS_Customer:
• vw_JOBBOSS_InvoiceHeader reads vw_JOBBOSS_Account:, vw_JOBBOSS_Customer:
• vw_JOBBOSS_InvoiceDetail reads vw_JOBBOSS_InvoiceHeader:
• vw_JOBBOSS_SalesOrderHeader reads vw_JOBBOSS_Account:, vw_JOBBOSS_Customer:
• vw_JOBBOSS_SalesOrderDetail reads vw_JOBBOSS_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
JobBoss Salesperson	CommercientSF19__JobBoss_Employee__c	28	Employee → CommercientSF19__ExternalKey__c, First_Name, Last_Name → Name, Employee → CommercientSF19__Employee__c, Work_Center → CommercientSF19__Work_Center__c, Address → CommercientSF19__Address__c
Accounts	Account	14	Customer → CommercientSF__Commercient_ArCustomerCode__c, Name → Name, Sales_Rep → CommercientSF19__JobBoss_Salesperson__c, Phone → Phone, Line1, Line2 → BillingStreet
SYNC ACCOUNT	Account	13	CommercientSFommercient_ArCustomerCode → CommercientSF__Commercient_ArCustomerCode__c, Phone → Phone, BillingStreet → BillingStreet, BillingCity → BillingCity, BillingState → BillingState
JobBoss Customer	CommercientSF19__JobBoss_Customer__c	24	Customer → CommercientSF19__ExternalKey__c, SFDCID → Account, SFDCID → JobBoss_Salesperson, Name → Name, Email_Address → Email_Address
JobBoss Customer To Account Reverse Lookup	Account	2	Customer → CommercientSF__Commercient_ArCustomerCode__c, SFDCID → CommercientSF19__JobBoss_Customer__c
JobBoss Address	CommercientSF19__JobBoss_Address__c	17	AddressKey → CommercientSF19__ExternalKey__c, Customer → Account, Customer → JobBoss_Customer, Name → Name, Line1 → Line1
JobBoss CONTACT	Contact	10	AccountID → AccountId, JobBoss_Customer → JobBoss_Customer__c, LastName → LastName, Email_Address → email_address__c, Email → Email
JobBoss SalesOrderHeader	CommercientSF19__JobBoss_SO_Header__c	30	Sales_Order → CommercientSF19__ExternalKey__c, Sales_Order → CommercientSF19__Name__c, Customer → CommercientSF19__Account__c, Customer → CommercientSF19__JobBoss_Customer__c, Sales_Order → CommercientSF19__Sales_Order__c
JobBoss SalesOrderDetail	CommercientSF19__JobBoss_SO_Detail__c	50	SO_DetailKey → CommercientSF19__ExternalKey__c, Sales_Order, SO_Line → CommercientSF19__Name__c, SFDCID → CommercientSF19__JobBoss_Sales_Order_Header__c, SO_Detail → CommercientSF19__SO_Detail__c, Sales_Order → CommercientSF19__Sales_Order__c
JobBoss InvoiceHeader	CommercientSF19__JobBoss_Invoice_Header__c	32	Document → CommercientSF19__ExternalKey__c, Document → CommercientSF19__Name__c, Customer → CommercientSF19__Account__c, Customer → CommercientSF19__JobBoss_Customer__c, Document_Date → CommercientSF19__Document_Date__c
JobBoss InvoiceDetail	CommercientSF19__JobBoss_Invoice_Detail__c	46	Invoice_DetailKey → CommercientSF19__ExternalKey__c, Document, Document_Line → CommercientSF19__Name__c, Document → CommercientSF19__JobBoss_Invoice_Header__c, Invoice_Detail → CommercientSF19__Invoice_Detail__c, Document → CommercientSF19__Document__c

6. Community templates

The catalogue carries 143 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: 143
• Default operations: insert on 143, update on 143, delete on 143
• Marked circular-sync: 0
• Licence groups they span: 14
• Destination objects: Account, Opportunity, Contact, OpportunityLineItem, Product2, CommercientSF19__JobBoss_Customer__c, CommercientSF19_JobBoss_Quote__c, PriceBookEntry, CommercientSF19__JobBoss_Address__c, CommercientSF19__JobBoss_Employee__c, CommercientSF19__JobBoss_Invoice_Detail__c, CommercientSF19__JobBoss_Invoice_Header__c, CommercientSF19__JobBoss_SO_Detail__c, CommercientSF19__JobBoss_SO_Header__c, CommercientSF19_JobBoss_Item__c, CommercientSF19_JobBoss_ItemWarehouse__c, CommercientSF19_JobBoss_QuoteLine__c, User, CommercientSF19__JobBoss_Job__c, CommercientSF19__JobBoss_JOB__c, 19 more and 10 custom objects
• Object display names: JobBoss Customer, JobBoss Customer To Account Reverse Lookup, Accounts, JobBoss CONTACT, JobBoss InvoiceDetail, JobBoss InvoiceHeader, JobBoss QUOTE, CREATE STANDARD PRICEBOOK, JobBoss Address, JobBoss Salesperson, Opportunity Line, SYNC ADDRESS, 54 more and 20 further templates
• Template groups: Account, CRM Opportunity and Line, Product, Invoice, Opportunity, Salesorder, Customer Multi Ship Addresses, CRM Order and Line, QuoteLine

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_EPICOR10_Owners
• vw_JOBBOSS_Account
• vw_JOBBOSS_CustomerToAccountLookup
• vw_JOBBOSS_Contact
• vw_JOBBOSS_Customer
• vw_JOBBOSS_Address
• vw_JOBBOSS_InvoiceHeader
• vw_JOBBOSS_InvoiceDetail
• vw_JOBBOSS_SalesOrderHeader
• vw_JOBBOSS_SalesOrderDetail
• vw_JOBBOSS_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 JobBOSS → 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.