CRMPro → Salesforce — Exact MAX: what the shipped templates set up

CRMPro → Salesforce — Exact MAX: 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/exact-max.md, and that skill’s ERP table is what points at it. What follows is only what the shipped Exact MAX → 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
Commodity Codes	ERP COMMODITY_CODES data becomes CommercientSF19__Commodity_Codes__c in Salesforce. New records are created and existing ones updated; none are deleted.	CommercientSF19__Commodity_Codes__c	SF_ERP_Salesforce_Clone_Commodity_Codes
Get User	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 and existing ones updated; none are deleted.	Account, CommercientSF19__Customer_Master__c, CommercientSF19__Sales_Rep_Master__c	SF_ERP_Salesforce_Clone_Customer_Master, SF_ERP_Salesforce_Clone_Shipping_Master, SF_ERP_Salesforce_Clone_Sales_Rep_Master, SF_ERP_Salesforce_Clone_Code_Master
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__Shipping_Master__c	SF_ERP_Salesforce_Clone_Shipping_Master
Product	ERP PART_MASTER, PART_SALES, PART_STOCK data becomes CommercientSF19__Part_Master__c, CommercientSF19__Part_Stock__c, CommercientSF19__Part_Sales__c in Salesforce. New records are created and existing ones updated; none are deleted.	CommercientSF19__Part_Master__c, CommercientSF19__Part_Stock__c, CommercientSF19__Part_Sales__c, Product2, CommercientSF19__Product_Structure__c	SF_ERP_Salesforce_Clone_Part_Master, SF_ERP_Salesforce_Clone_Part_Sales, SF_ERP_Salesforce_Clone_Part_Stock, SF_ERP_Salesforce_Clone_Product_Structure
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__Invoice_Master__c, CommercientSF19__Invoice_Detail__c	SF_ERP_Salesforce_Clone_Invoice_Master, CommercientFlags, SF_ERP_Salesforce_Clone_Invoice_Detail
Pricebook	ERP PART_MASTER, PART_SALES data becomes PricebookEntry, PriceBookEntry in Salesforce. New records are created and existing ones updated; none are deleted.	PricebookEntry, PriceBookEntry	SF_ERP_Salesforce_Clone_Part_Master, SF_ERP_Salesforce_Clone_Part_Sales
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__SO_Master__c, CommercientSF19__SO_Detail__c	SF_ERP_Salesforce_Clone_SO_Master, 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
Sales Person	CommercientSF19__Sales_Rep_Master__c	CommercientSF19__ExternalKey__c	1	vw_SalesPerson	vw_EXACTMAX_SalesPerson	CommercientSF19__ / __c	—
Account	Account	CommercientSF__Commercient_ArCustomerCode__c	4	vw_Account	vw_EXACTMAX_Account	'' / ''	—
Customer Master	CommercientSF19__Customer_Master__c	CommercientSF19__ExternalKey__c	5	vw_Customer	vw_EXACTMAX_Customer	CommercientSF19__ / __c	—
Customer Reverse Lookup Account	Account	CommercientSF__Commercient_ArCustomerCode__c	6	vw_CustomerToAccountLookup	vw_EXACTMAX_CustomerToAccountLookup	'' / ''	—
Shipping Master	CommercientSF19__Shipping_Master__c	CommercientSF19__ExternalKey__c	7	vw_ShipToAddress	vw_EXACTMAX_ShipToAddress	CommercientSF19__ / __c	—
Commodity Codes	CommercientSF19__Commodity_Codes__c	CommercientSF19__ExternalKey__c	8	vw_Commodity_Codes	vw_EXACTMAX_Commodity_Codes	CommercientSF19__ / __c	—
Part Master	CommercientSF19__Part_Master__c	CommercientSF19__ExternalKey__c	9	vw_PartMaster	vw_EXACTMAX_PartMaster	CommercientSF19__ / __C	—
Sales Order Header	CommercientSF19__SO_Master__c	CommercientSF19__ExternalKey__c	10	vw_SalesOrder	vw_EXACTMAX_SalesOrderHeader	CommercientSF19__ / __c	—
Sales Order Line	CommercientSF19__SO_Detail__c	CommercientSF19__ExternalKey__c	11	vw_SalesOrderLine	vw_EXACTMAX_SalesOrderLine	CommercientSF19__ / __c	—
Invoice Header	CommercientSF19__Invoice_Master__c	CommercientSF19__ExternalKey__c	12	vw_InvoiceHeader	vw_EXACTMAX_InvoiceHeader	CommercientSF19__ / __c	—
Invoice Line	CommercientSF19__Invoice_Detail__c	CommercientSF19__ExternalKey__c	13	vw_InvoiceLine	vw_EXACTMAX_InvoiceLine	CommercientSF19__ / __c	—
Product	Product2	CommercientSF__ExternalKey__c	14	vw_Product	vw_EXACTMAX_Product	'' / ''	—
Product Reverse Lookup	CommercientSF19__Part_Master__c	CommercientSF19__ExternalKey__c	15	vw_ProductReverseLookup	vw_EXACTMAX_PRODUCT_REVERSE_LOOKUP	CommercientSF19__ / __c	—
Create Standard PriceBook	PricebookEntry	ExternalKey__C	16	vw_ProductPriceBook	vw_EXACTMAX_StandardPriceBook	'' / ''	—
Get User	User	Id	17	vw_EXACTMAX_User	SELECT 1=0	'' / ''	1
Part Stock	CommercientSF19__Part_Stock__c	CommercientSF19__ExternalKey__c	19	vw_PartStock	vw_EXACTMAX_Part_Stock	CommercientSF19__ / __C	—
Update Standard Pricebook	PriceBookEntry	ExternalKey__C	20	vw_ProductPriceBook	vw_EXACTMAX_StandardPriceBook_Update	'' / ''	—
Part Sales	CommercientSF19__Part_Sales__c	CommercientSF19__ExternalKey__c	21	vw_PartSales	vw_EXACTMAX_Part_Sales	CommercientSF19__ / __c	—
Product Structure	CommercientSF19__Product_Structure__c	CommercientSF19__ExternalKey__c	22	vw_ProductStructure	vw_EXACTMAX_ProductStructure	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_Delete_Records 0, Sync_Batch_Size 200. Is_Active_Get_Records is set on Create Standard PriceBook; IsAccountMatching is set on Account. Text columns a template does not use are inserted as '' rather than left NULL. Get_SOQL_Query carries a query on Get User, Create Standard PriceBook — those rows read records back from Salesforce as well as pushing. On Customer Reverse Lookup Account, Product Reverse Lookup the SQL_Query names a view the same template’s CreateViewQuery does not create (vw_EXACTMAX_CustomerToAccountLookup against vw_CustomerToAccountLookup; vw_EXACTMAX_PRODUCT_REVERSE_LOOKUP against vw_PRODUCT_REVERSE_LOOKUP), 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_EXACTMAX_SalesPerson	insert + update	vw_SalesPerson:	—	—	SF_ERP_Salesforce_Clone_Sales_Rep_Master
vw_EXACTMAX_Account	insert + update	vw_Account:	vw_SalesPerson:, vw_EXACTMAX_User:	—	SF_ERP_Salesforce_Clone_Customer_Master, SF_ERP_Salesforce_Clone_Shipping_Master, SF_ERP_Salesforce_Clone_Sales_Rep_Master, SF_ERP_Salesforce_Clone_Code_Master
vw_EXACTMAX_Customer	insert + update	vw_Customer:	vw_SalesPerson:, vw_Account:	—	SF_ERP_Salesforce_Clone_Customer_Master
vw_CustomerToAccountLookup	insert + update	vw_CustomerToAccountLookup:	vw_Customer:	—	SF_ERP_Salesforce_Clone_Customer_Master
vw_EXACTMAX_ShipToAddress	insert + update	vw_ShipToAddress:	vw_Customer:, vw_Account:	—	SF_ERP_Salesforce_Clone_Shipping_Master
vw_EXACTMAX_Commodity_Codes	insert + update	vw_Commodity_Codes:	—	—	SF_ERP_Salesforce_Clone_Commodity_Codes
vw_EXACTMAX_PartMaster	insert + update	vw_PartMaster:	vw_Commodity_Codes:	—	SF_ERP_Salesforce_Clone_Part_Master
vw_EXACTMAX_SalesOrderHeader	insert + update	vw_SalesOrder:	vw_Account:, vw_Customer:, vw_SalesPerson:	—	SF_ERP_Salesforce_Clone_SO_Master, CommercientFlags
vw_EXACTMAX_SalesOrderLine	insert + update	vw_SalesOrderLine:	vw_SalesOrder:, vw_PartMaster:	—	SF_ERP_Salesforce_Clone_SO_Detail
vw_EXACTMAX_InvoiceHeader	insert + update	vw_InvoiceHeader:	vw_Account:, vw_Customer:, vw_SalesPerson:	—	SF_ERP_Salesforce_Clone_Invoice_Master, CommercientFlags
vw_EXACTMAX_InvoiceLine	insert + update	vw_InvoiceLine:	vw_InvoiceHeader:, vw_PartMaster:	—	SF_ERP_Salesforce_Clone_Invoice_Detail
vw_EXACTMAX_Product	insert + update	vw_Product:	vw_PartMaster:	CommercientSF__ExternalKey__c	SF_ERP_Salesforce_Clone_Part_Master, SF_ERP_Salesforce_Clone_Part_Sales
vw_PRODUCT_REVERSE_LOOKUP	insert + update	vw_ProductReverseLookup:	vw_Product:	—	SF_ERP_Salesforce_Clone_Part_Master, SF_ERP_Salesforce_Clone_Part_Sales
vw_EXACTMAX_StandardPriceBook	insert-only	vw_ProductPriceBook:	vw_Product:	—	SF_ERP_Salesforce_Clone_Part_Master, SF_ERP_Salesforce_Clone_Part_Sales
vw_EXACTMAX_Part_Stock	insert + update	vw_PartStock:	vw_PartMaster:	—	SF_ERP_Salesforce_Clone_Part_Stock
vw_EXACTMAX_StandardPriceBook_Update	insert + update	vw_ProductPriceBook:	vw_Product:	—	SF_ERP_Salesforce_Clone_Part_Master, SF_ERP_Salesforce_Clone_Part_Sales
vw_EXACTMAX_Part_Sales	insert + update	vw_PartSales:	vw_PartMaster:, vw_Product:	—	SF_ERP_Salesforce_Clone_Part_Sales
vw_EXACTMAX_ProductStructure	insert + update	vw_ProductStructure:	vw_PartMaster:, vw_Product:	—	SF_ERP_Salesforce_Clone_Product_Structure

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

• 1 — Sales Person
• 4 — Account
• 5 — Customer Master
• 6 — Customer Reverse Lookup Account
• 7 — Shipping Master
• 8 — Commodity Codes
• 9 — Part Master
• 10 — Sales Order Header
• 11 — Sales Order Line
• 12 — Invoice Header
• 13 — Invoice Line
• 14 — Product
• 15 — Product Reverse Lookup
• 16 — Create Standard PriceBook
• 17 — Get User
• 19 — Part Stock
• 20 — Update Standard Pricebook
• 21 — Part Sales
• 22 — Product Structure

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_CustomerToAccountLookup reads vw_Customer:
• vw_EXACTMAX_Account reads vw_SalesPerson:, vw_EXACTMAX_User:
• vw_EXACTMAX_Customer reads vw_SalesPerson:, vw_Account:
• vw_EXACTMAX_ShipToAddress reads vw_Customer:, vw_Account:
• vw_EXACTMAX_PartMaster reads vw_Commodity_Codes:
• vw_PRODUCT_REVERSE_LOOKUP reads vw_Product:
• vw_EXACTMAX_Part_Stock reads vw_PartMaster:
• vw_EXACTMAX_Part_Sales reads vw_PartMaster:, vw_Product:
• vw_EXACTMAX_InvoiceHeader reads vw_Account:, vw_Customer:, vw_SalesPerson:
• vw_EXACTMAX_InvoiceLine reads vw_InvoiceHeader:, vw_PartMaster:
• vw_EXACTMAX_StandardPriceBook reads vw_Product:
• vw_EXACTMAX_StandardPriceBook_Update reads vw_Product:
• vw_EXACTMAX_Product reads vw_PartMaster:
• vw_EXACTMAX_ProductStructure reads vw_PartMaster:, vw_Product:
• vw_EXACTMAX_SalesOrderHeader reads vw_Account:, vw_Customer:, vw_SalesPerson:
• vw_EXACTMAX_SalesOrderLine reads vw_SalesOrder:, vw_PartMaster:

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	CommercientSF19__Sales_Rep_Master__c	25	SLSREP_26 → CommercientSF19__ExternalKey__c, SLSNME_26 → Name, SLSTER_26 → CommercientSF19__SLSTER__c, MCOMP_26 → CommercientSF19__MCOMP__c, MSITE_26 → CommercientSF19__MSITE__c
Account	Account	17	CUSTID_23 → CommercientSF__Commercient_ArCustomerCode__c, NAME_23 → Name, PHONE_23 → Phone, SFDCID → CommercientSF19__EXACTMAX_Sales_Rep_Master__c, CUSTYP_23 → Type
Customer Master	CommercientSF19__Customer_Master__c	74	CUSTID_23 → CommercientSF19__ExternalKey__c, CUSTID_23 → CommercientSF19__Account__c, DSCRTE_23 → CommercientSF19__DSCRTE_23__c, CLIMIT_23 → CommercientSF19__CLIMIT_23__c, SLSMTD_23 → CommercientSF19__SLSMTD_23__c
Customer Reverse Lookup Account	Account	2	CUSTID_23 → CommercientSF__Commercient_ArCustomerCode__c, SFDCID → CommercientSF19__EXACTMAX_Customer_Master__c
Shipping Master	CommercientSF19__Shipping_Master__c	36	CUSTID_24,SHPCDE_24 → CommercientSF19__ExternalKey__c, CUSTID_24,SHPCDE_24 → CommercientSF19__Name__c, CUSTID_24 → Account, CUSTID_24 → CommercientSF19__Customer_Master__c, NAME_24 → CommercientSF19__NAME_24__c
Commodity Codes	CommercientSF19__Commodity_Codes__c	15	COMCDE_48 → CommercientSF19__ExternalKey__c, COMCDE_48 → CommercientSF19__Name__c, COMCDE_48 → CommercientSF19__COMCDE_48__c, DESC_48 → CommercientSF19__DESC_48__c, UDFKEY_48 → CommercientSF19__UDFKEY_48__c
Part Master	CommercientSF19__Part_Master__c	131	PRTNUM_01 → CommercientSF19__ExternalKey__c, PRTNUM_01 → Name, TYPE_01 → CommercientSF19__TYPE_01__c, COMCDE_01 → CommercientSF19__EXACTMAX_Commodity_Codes__c, CLSCDE_01 → CommercientSF19__CLSCDE_01__c
Sales Order Header	CommercientSF19__SO_Master__c	71	ORDNUM_27 → CommercientSF19__ExternalKey__c, SPLIT1_27 → CommercientSF19__SPLIT1_27__c, SPLIT2_27 → CommercientSF19__SPLIT2_27__c, SPLIT3_27 → CommercientSF19__SPLIT3_27__c, COMMIS_27 → CommercientSF19__COMMIS_27__c
Sales Order Line	CommercientSF19__SO_Detail__c	76	ORDNUM_28,LINNUM_28,DELNUM_28 → CommercientSF19__ExternalKey__c, ORDNUM_28,LINNUM_28,DELNUM_28 → CommercientSF19__Name__c, DELNUM_28 → CommercientSF19__DELNUM_28__c, STATUS_28 → CommercientSF19__STATUS_28__c, CUSTID_28 → CommercientSF19__CUSTID_28__c
Invoice Header	CommercientSF19__Invoice_Master__c	83	ORDNUM_31,INVCE_31 → CommercientSF19__ExternalKey__c, ORDNUM_31,INVCE_31 → CommercientSF19__Name__c, CUSTID_31 → Account, CUSTID_31 → CommercientSF19__EXACTMAX_Customer_Master__c, REP1_31 → CommercientSF19__EXACTMAX_Sales_Rep_Master__c
Invoice Line	CommercientSF19__Invoice_Detail__c	60	ORDNUM_32,LINNUM_32,DELNUM_32,INVCE_32 → CommercientSF19__ExternalKey__c, ORDNUM_32,LINNUM_32,DELNUM_32,INVCE_32 → CommercientSF19__Name__c, SFDCID → CommercientSF19__Invoice_Master__c, PRICE_32 → CommercientSF19__PRICE_32__c, ORGQTY_32 → CommercientSF19__ORGQTY_32__c
Product	Product2	6	PRTNUM_01 → CommercientSF__ExternalKey__c, PMDES1_01 → Name, PRTNUM_01 → ProductCode, PMDES2_01 → Description, IsActive → IsActive
Product Reverse Lookup	CommercientSF19__Part_Master__c	2	PRTNUM_01 → CommercientSF19__ExternalKey__c, SFDCID → CommercientSF19__Product__c
Create Standard PriceBook	PricebookEntry	5	PRTNUM_01 → ExternalKey__c, SFDCID → Pricebook2Id, SFDCID → Product2ID, IsActive → IsActive, PRICE_29 → UnitPrice
Part Stock	CommercientSF19__Part_Stock__c	39	MAXID → CommercientSF19__ExternalKey__c, SFDCID → CommercientSF19__Part_Master__c, MAXID → Name, PRTNUM_06 → PRTNUM_06, STK_06 → STK_06
Update Standard Pricebook	PriceBookEntry	3	PRTNUM_01 → ExternalKey__c, IsActive → IsActive, PRICE_29 → UnitPrice
Part Sales	CommercientSF19__Part_Sales__c	84	PRTNUM_29 → CommercientSF19__ExternalKey__c, PRTNUM_29 → Name, SLSCAT_29 → SLSCAT_29, PMDES1_29 → PMDES1_29, PMDES2_29 → PMDES2_29
Product Structure	CommercientSF19__Product_Structure__c	33	PARPRT_02 → CommercientSF19__PARPRT_02__c, name → CommercientSF19__Name__c, COMPRT_02 → CommercientSF19__COMPRT_02__c, EFFDTE_02 → CommercientSF19__EFFDTE_02__c, FILL01_02 → CommercientSF19__FILL01_02__c

6. Community templates

The catalogue carries 44 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: 44
• Default operations: insert on 44, update on 44, delete on 44
• Marked circular-sync: 0
• Licence groups they span: 8
• Destination objects: Account, CommercientSF19__Part_Master__c, CommercientSF19__SO_Detail__c, CommercientSF19__Commodity_Codes__c, CommercientSF19__Customer_Master__c, CommercientSF19__Invoice_Detail__c, CommercientSF19__Invoice_Master__c, CommercientSF19__Part_Sales__c, CommercientSF19__Sales_Rep_Master__c, CommercientSF19__Shipping_Master__c, CommercientSF19__SO_Master__c, PricebookEntry, PriceBookEntry, Product2, account, CommercientSF19__CodeMaster__c, CommercientSF19__MATCHING__c, CommercientSF19__Part_Stock__c, CommercientSF19__Product_Structure__c, Customer_Part_Data__c, 3 more and 2 custom objects
• Object display names: Account, Commodity Codes, Create Standard PriceBook, Customer Master, Invoice Header, Invoice Line, Part Master, Part Sales, Product, Product Reverse Lookup, Sales Order Header, Sales Order Line, 15 more and 2 further templates
• Template groups: Account, Product, Salesorder, 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_Commodity_Codes
• vw_EXACTMAX_User
• vw_CustomerToAccountLookup
• vw_Account
• vw_Customer
• vw_ShipToAddress
• vw_PartMaster
• vw_ProductReverseLookup
• vw_PartStock
• vw_PartSales
• vw_InvoiceHeader
• vw_InvoiceLine
• vw_ProductPriceBook
• vw_Product
• vw_ProductStructure
• vw_SalesOrder
• vw_SalesOrderLine
• vw_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 Exact MAX → 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.