CRMPro → Salesforce — Aptean Encompix: what the shipped templates set up

CRMPro → Salesforce — Aptean Encompix: 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/aptean-encompix.md, and that skill’s ERP table is what points at it. What follows is only what the shipped Aptean Encompix → 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
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, CommercientSF21__Aptean_Encompix_customer__c, CommercientSF21__Aptean_Encompix_slsprsn__c	SF_ERP_Salesforce_Clone_customer, SF_ERP_Salesforce_Clone_custship, SF_ERP_Salesforce_Clone_slsprsn
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.	CommercientSF21__Aptean_Encompix_custship__c	SF_ERP_Salesforce_Clone_custship
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.	CommercientSF21__Aptean_Encompix_invoice__c, CommercientSF21__Aptean_Encompix_inv_regl__c	SF_ERP_Salesforce_Clone_invoice, SF_ERP_Salesforce_Clone_inv
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.	CommercientSF21__Aptean_Encompix_so_hdr__c	SF_ERP_Salesforce_Clone_so

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
APTEAN ENCOMPIX Salesperson	CommercientSF21__Aptean_Encompix_slsprsn__c	CommercientSF21__ExternalKey__c	1	vw_APTEANENCOMPIX_Salesperson	vw_APTEANENCOMPIX_Salesperson	CommercientSF21__ / __c	1
Account Update	Account	CommercientSF__Commercient_ArCustomerCode__c	3	vw_APTEANENCOMPIX_Account	vw_APTEANENCOMPIX_Account	'' / ''	1
APTEAN ENCOMPIX Customer	CommercientSF21__Aptean_Encompix_customer__c	CommercientSF21__ExternalKey__c	4	vw_APTEANENCOMPIX_Customer	vw_APTEANENCOMPIX_Customer	CommercientSF21__ / __c	1
Customer To Account Lookup	Account	CommercientSF__Commercient_ArCustomerCode__c	5	vw_APTEANENCOMPIX_CustomerToAccountLookup	vw_APTEANENCOMPIX_CustomerToAccountLookup	'' / ''	1
APTEAN ENCOMPIX ShipToAddress	CommercientSF21__Aptean_Encompix_custship__c	CommercientSF21__ExternalKey__c	6	vw_APTEANENCOMPIX_ShipToAddress	vw_APTEANENCOMPIX_ShipToAddress	CommercientSF21__ / __c	1
APTEAN ENCOMPIX SalesOrderHeader	CommercientSF21__Aptean_Encompix_so_hdr__c	CommercientSF21__ExternalKey__c	12	vw_APTEANENCOMPIX_SalesOrderHeader	vw_APTEANENCOMPIX_SalesOrderHeader	CommercientSF21__ / __c	1
APTEAN ENCOMPIX InvoiceHeader	CommercientSF21__Aptean_Encompix_invoice__c	CommercientSF21__ExternalKey__c	13	vw_APTEANENCOMPIX_InvoiceHeader	vw_APTEANENCOMPIX_InvoiceHeader	CommercientSF21__ / __c	1
APTEAN ENCOMPIX InvoiceLine	CommercientSF21__Aptean_Encompix_inv_regl__c	CommercientSF21__ExternalKey__c	15	vw_APTEANENCOMPIX_InvoiceLine	vw_APTEANENCOMPIX_InvoiceLine	CommercientSF21__ / __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 Account Update — 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_APTEANENCOMPIX_Salesperson	insert + update	vw_APTEANENCOMPIX_Salesperson:	—	ExternalKey	SF_ERP_Salesforce_Clone_slsprsn
vw_APTEANENCOMPIX_Account	insert + update	vw_APTEANENCOMPIX_Account:	vw_APTEANENCOMPIX_Salesperson:, vw_APTEANENCOMPIX_Terms:	—	SF_ERP_Salesforce_Clone_customer, SF_ERP_Salesforce_Clone_custship, SF_ERP_Salesforce_Clone_slsprsn
vw_APTEANENCOMPIX_Customer	insert + update	vw_APTEANENCOMPIX_Customer:	vw_APTEANENCOMPIX_Account:	ExternalKey	SF_ERP_Salesforce_Clone_customer
vw_APTEANENCOMPIX_CustomerToAccountLookup	insert + update	vw_APTEANENCOMPIX_CustomerToAccountLookup:	vw_APTEANENCOMPIX_Customer:, vw_APTEANENCOMPIX_Account:	—	SF_ERP_Salesforce_Clone_customer
vw_APTEANENCOMPIX_ShipToAddress	insert + update	vw_APTEANENCOMPIX_ShipToAddress:	vw_APTEANENCOMPIX_Account:, vw_APTEANENCOMPIX_Customer:	ExternalKey	SF_ERP_Salesforce_Clone_custship
vw_APTEANENCOMPIX_SalesOrderHeader	insert + update	vw_APTEANENCOMPIX_SalesOrderHeader:	vw_APTEANENCOMPIX_Account:, vw_APTEANENCOMPIX_Customer:	ExternalKey	SF_ERP_Salesforce_Clone_so
vw_APTEANENCOMPIX_InvoiceHeader	insert + update	vw_APTEANENCOMPIX_InvoiceHeader:	vw_APTEANENCOMPIX_Account:, vw_APTEANENCOMPIX_Customer:, vw_APTEANENCOMPIX_SalesOrderHeader:	ExternalKey	SF_ERP_Salesforce_Clone_invoice
vw_APTEANENCOMPIX_InvoiceLine	insert + update	vw_APTEANENCOMPIX_InvoiceLine:	vw_APTEANENCOMPIX_InvoiceHeader:, vw_APTEANENCOMPIX_JobHdr:, vw_APTEANENCOMPIX_ItemMaster:	ExternalKey	SF_ERP_Salesforce_Clone_inv, SF_ERP_Salesforce_Clone_invoice

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 to 1, 3, 4, 5, 6, 12, 13, 15. A run processes active rows in ascending Sync_Order, which is the order the templates put them in:

• 1 — APTEAN ENCOMPIX Salesperson
• 3 — Account Update
• 4 — APTEAN ENCOMPIX Customer
• 5 — Customer To Account Lookup
• 6 — APTEAN ENCOMPIX ShipToAddress
• 12 — APTEAN ENCOMPIX SalesOrderHeader
• 13 — APTEAN ENCOMPIX InvoiceHeader
• 15 — APTEAN ENCOMPIX InvoiceLine

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_APTEANENCOMPIX_Account reads vw_APTEANENCOMPIX_Salesperson:, vw_APTEANENCOMPIX_Terms:; no template in this set writes vw_APTEANENCOMPIX_Terms:
• vw_APTEANENCOMPIX_CustomerToAccountLookup reads vw_APTEANENCOMPIX_Customer:, vw_APTEANENCOMPIX_Account:
• vw_APTEANENCOMPIX_Customer reads vw_APTEANENCOMPIX_Account:
• vw_APTEANENCOMPIX_ShipToAddress reads vw_APTEANENCOMPIX_Account:, vw_APTEANENCOMPIX_Customer:
• vw_APTEANENCOMPIX_InvoiceHeader reads vw_APTEANENCOMPIX_Account:, vw_APTEANENCOMPIX_Customer:, vw_APTEANENCOMPIX_SalesOrderHeader:
• vw_APTEANENCOMPIX_InvoiceLine reads vw_APTEANENCOMPIX_InvoiceHeader:, vw_APTEANENCOMPIX_JobHdr:, vw_APTEANENCOMPIX_ItemMaster:; no template in this set writes vw_APTEANENCOMPIX_JobHdr:, vw_APTEANENCOMPIX_ItemMaster:
• vw_APTEANENCOMPIX_SalesOrderHeader reads vw_APTEANENCOMPIX_Account:, vw_APTEANENCOMPIX_Customer:

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
APTEAN ENCOMPIX Salesperson	CommercientSF21__Aptean_Encompix_slsprsn__c	58	slsprsn → CommercientSF21__slsprsn__c, comm_pct → comm_pct, next_lvl → CommercientSF21__next_lvl__c, chg_dt → CommercientSF21__chg_dt__c, chg_time → CommercientSF21__chg_time__c
Account Update	Account	17	CommercientSFommercient_ArCustomerCode → CommercientSF__Commercient_ArCustomerCode__c, Phone → Phone, BillingStreet → BillingStreet, BillingCity → BillingCity, BillingCountryCode → BillingCountryCode
APTEAN ENCOMPIX Customer	CommercientSF21__Aptean_Encompix_customer__c	91	Account → Account, cust_id → CommercientSF21__cust_id__c, addr_1 → CommercientSF21__addr_1__c, xxx_addr_2 → CommercientSF21__xxx_addr_2__c, city → CommercientSF21__city__c
Customer To Account Lookup	Account	2	CommercientSFommercient_ArCustomerCode → CommercientSF__Commercient_ArCustomerCode__c, CommercientSF21__Aptean_Encompix_Customer → CommercientSF21__Aptean_Encompix_Customer__c
APTEAN ENCOMPIX ShipToAddress	CommercientSF21__Aptean_Encompix_custship__c	78	Account → Account, Aptean_Encompix_Customer → Aptean_Encompix_Customer, cust_id → CommercientSF21__cust_id__c, shipto → CommercientSF21__shipto__c, addr_1 → CommercientSF21__addr_1__c
APTEAN ENCOMPIX SalesOrderHeader	CommercientSF21__Aptean_Encompix_so_hdr__c	94	Account → Account, Aptean_Encompix_Customer → Aptean_Encompix_Customer, order_no → CommercientSF21__order_no__c, cust_id → CommercientSF21__cust_id__c, cust_po → CommercientSF21__cust_po__c
APTEAN ENCOMPIX InvoiceHeader	CommercientSF21__Aptean_Encompix_invoice__c	79	Account → Account, Aptean_Encompix_Customer → Aptean_Encompix_Customer, Aptean_Encompix_Sales_Order_Header → Aptean_Encompix_Sales_Order_Header__c, ar_account → ar_account, cust_id → CommercientSF21__cust_id__c
APTEAN ENCOMPIX InvoiceLine	CommercientSF21__Aptean_Encompix_inv_regl__c	86	Aptean_Encompix_Invoice_Header → Aptean_Encompix_Invoice_Header, Job_HDR → Job_HDR__c, Aptean_Encompix_Item → Aptean_Encompix_Item, disc_amt → disc_amt, item_desc → item_desc

6. Community templates

The catalogue carries 22 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: 22
• Default operations: insert on 22, update on 22, delete on 22
• Marked circular-sync: 0
• Licence groups they span: 10
• Destination objects: Account, Product2, ACCOUNTMATCHING__c, Aptean_Encompix_Employee__c, CommercientSF21__Aptean_Encompix_customer__c, CommercientSF21__Aptean_Encompix_custship__c, CommercientSF21__Aptean_Encompix_inv_regl__c, CommercientSF21__Aptean_Encompix_invoice__c, CommercientSF21__Aptean_Encompix_item__c, CommercientSF21__Aptean_Encompix_job_bom__c, CommercientSF21__Aptean_Encompix_slsprsn__c, CommercientSF21__Aptean_Encompix_so_hdr__c, CommercientSF21__Aptean_Encompix_terms__c, CUSTOMER1__c, ITEMMASTER__c, Job_HDR__c, Labor_Log__c and 2 custom objects
• Object display names: Account Create, Account Update, APTEAN ENCOMPIX Customer, Aptean Encompix Employee, APTEAN ENCOMPIX InvoiceHeader, APTEAN ENCOMPIX InvoiceLine, APTEAN ENCOMPIX Item Master, APTEAN ENCOMPIX Job Header, APTEAN ENCOMPIX Labor Log, APTEAN ENCOMPIX Sales Job BOM, APTEAN ENCOMPIX SalesOrderHeader, APTEAN ENCOMPIX Salesperson, 8 more and 2 further templates
• Template groups: Account, Product, Invoice, Customer Multi Ship Addresses, Salesorder

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_APTEANENCOMPIX_Account
• vw_APTEANENCOMPIX_CustomerToAccountLookup
• vw_APTEANENCOMPIX_Customer
• vw_APTEANENCOMPIX_ShipToAddress
• vw_APTEANENCOMPIX_InvoiceHeader
• vw_APTEANENCOMPIX_InvoiceLine
• vw_APTEANENCOMPIX_SalesOrderHeader
• vw_APTEANENCOMPIX_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 Aptean Encompix → 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.