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

CRMPro → Salesforce — Famous: 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/famous.md, and that skill’s ERP table is what points at it. What follows is only what the shipped Famous → 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 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, FAMOUS_Customer__c, FAMOUS_Salesperson__c	SF_ERP_Salesforce_Clone_FC_NAME_CATEGORY, SF_ERP_Salesforce_Clone_FC_NAME_ROLE, SF_ERP_Salesforce_Clone_FC_NAME, SF_ERP_Salesforce_Clone_AR_CUST, SF_ERP_Salesforce_Clone_FC_NAME_LOCATION, SF_ERP_Salesforce_Clone_AR_CUST_CLASS
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.	FAMOUS_ShipToAddress__c	SF_ERP_Salesforce_Clone_FC_NAME_CATEGORY, SF_ERP_Salesforce_Clone_FC_NAME_ROLE, SF_ERP_Salesforce_Clone_FC_NAME, SF_ERP_Salesforce_Clone_AR_CUST, SF_ERP_Salesforce_Clone_FC_NAME_LOCATION, SF_ERP_Salesforce_Clone_AR_CUST_CLASS
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.	FAMOUS_Invoice_Header__c, FAMOUS_Invoice_Detail__c	SF_ERP_Salesforce_Clone_AR_TRX_HEADER, SF_ERP_Salesforce_Clone_FC_NAME, SF_ERP_Salesforce_Clone_FC_NAME_LOCATION, SF_ERP_Salesforce_Clone_FC_SALEPERSON, SF_ERP_Salesforce_Clone_FC_SALE_TERMS, SF_ERP_Salesforce_Clone_AR_TRX_LINE
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.	FAMOUS_Sales_Order_Header__c, FAMOUS_Sales_Order_Detail__c, FAMOUS_Sales_Order_History_Header__c, FAMOUS_Sales_Order_History_Detail__c	SF_ERP_Salesforce_Clone_AR_TRX_HEADER, SF_ERP_Salesforce_Clone_FC_NAME, SF_ERP_Salesforce_Clone_FC_NAME_LOCATION, SF_ERP_Salesforce_Clone_FC_SALEPERSON, SF_ERP_Salesforce_Clone_FC_SALE_TERMS, SF_ERP_Salesforce_Clone_AR_TRX_LINE

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
Account	Account	CommercientSF__Commercient_ArCustomerCode__c	1	vw_FAMOUS_Account	vw_FAMOUS_Account	'' / ''	1
Child Account	Account	CommercientSF__Commercient_ArCustomerCode__c	2	vw_FAMOUS_ChildAccount	vw_FAMOUS_ChildAccount	'' / ''	1
FAMOUS Salesperson	FAMOUS_Salesperson__c	ExternalKey__c	3	vw_FAMOUS_Salesperson	vw_FAMOUS_Salesperson	'' / __c	1
FAMOUS Customer	FAMOUS_Customer__c	ExternalKey__c	4	vw_FAMOUS_Customer	vw_FAMOUS_Customer	'' / __c	1
Customer To Account Reverse Lookup	Account	CommercientSF__Commercient_ArCustomerCode__c	5	vw_FAMOUS_CustomerToAccountReverseLookup	vw_FAMOUS_CustomerToAccountReverseLookup	'' / ''	1
FAMOUS Ship To Address	FAMOUS_ShipToAddress__c	ExternalKey__c	6	vw_FAMOUS_ShipToAddress	vw_FAMOUS_ShipToAddress	'' / __c	1
FAMOUS Sales Order Header	FAMOUS_Sales_Order_Header__c	ExternalKey__c	10	vw_FAMOUS_SalesOrderHeader	vw_FAMOUS_SalesOrderHeader	'' / __c	1
FAMOUS Sales Order Detail	FAMOUS_Sales_Order_Detail__c	ExternalKey__c	11	vw_FAMOUS_SalesOrderDetail	vw_FAMOUS_SalesOrderDetail	'' / __c	1
FAMOUS Invoice Header	FAMOUS_Invoice_Header__c	ExternalKey__c	12	vw_FAMOUS_InvoiceHeader	vw_FAMOUS_InvoiceHeader	'' / __c	1
FAMOUS Invoice Detail	FAMOUS_Invoice_Detail__c	ExternalKey__c	13	vw_FAMOUS_InvoiceDetail	vw_FAMOUS_InvoiceDetail	'' / __c	1
FAMOUS Sales Order History Header	FAMOUS_Sales_Order_History_Header__c	ExternalKey__c	14	vw_FAMOUS_SalesOrderHistoryHeader	vw_FAMOUS_SalesOrderHistoryHeader	'' / __c	1
FAMOUS Sales Order History Detail	FAMOUS_Sales_Order_History_Detail__c	ExternalKey__c	15	vw_FAMOUS_SalesOrderHistoryDetail	vw_FAMOUS_SalesOrderHistoryDetail	'' / __c	1
Get User	User	Id	17	vw_FAMOUS_User	SELECT 1=0	'' / ''	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 User, Account, Child Account — 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_FAMOUS_Account	insert + update	vw_FAMOUS_Account:	vw_FAMOUS_User:	—	SF_ERP_Salesforce_Clone_FC_NAME_CATEGORY, SF_ERP_Salesforce_Clone_FC_NAME_ROLE, SF_ERP_Salesforce_Clone_FC_NAME, SF_ERP_Salesforce_Clone_AR_CUST, SF_ERP_Salesforce_Clone_FC_NAME_LOCATION
vw_FAMOUS_ChildAccount	insert + update	vw_FAMOUS_ChildAccount:	vw_FAMOUS_Account:, vw_FAMOUS_User:	—	SF_ERP_Salesforce_Clone_FC_NAME_CATEGORY, SF_ERP_Salesforce_Clone_FC_NAME_ROLE, SF_ERP_Salesforce_Clone_FC_NAME, SF_ERP_Salesforce_Clone_AR_CUST, SF_ERP_Salesforce_Clone_FC_NAME_LOCATION
vw_FAMOUS_Salesperson	insert + update	vw_FAMOUS_Salesperson:	—	ExternalKey__c	SF_ERP_Salesforce_Clone_FC_SALEPERSON, SF_ERP_Salesforce_Clone_FC_NAME
vw_FAMOUS_Customer	insert + update	vw_FAMOUS_Customer:	vw_FAMOUS_Salesperson:, vw_FAMOUS_Account:	—	SF_ERP_Salesforce_Clone_FC_NAME_CATEGORY, SF_ERP_Salesforce_Clone_FC_NAME_ROLE, SF_ERP_Salesforce_Clone_FC_NAME, SF_ERP_Salesforce_Clone_AR_CUST, SF_ERP_Salesforce_Clone_FC_NAME_LOCATION
vw_FAMOUS_CustomerToAccountReverseLookup	insert + update	vw_FAMOUS_CustomerToAccountReverseLookup:	vw_FAMOUS_Account:, vw_FAMOUS_Customer:	—	SF_ERP_Salesforce_Clone_FC_NAME_CATEGORY, SF_ERP_Salesforce_Clone_FC_NAME_ROLE, SF_ERP_Salesforce_Clone_FC_NAME, SF_ERP_Salesforce_Clone_AR_CUST
vw_FAMOUS_ShipToAddress	insert + update	vw_FAMOUS_ShipToAddress:	vw_FAMOUS_Salesperson:, vw_FAMOUS_ChildAccount:, vw_FAMOUS_Customer:	—	SF_ERP_Salesforce_Clone_FC_NAME_CATEGORY, SF_ERP_Salesforce_Clone_FC_NAME_ROLE, SF_ERP_Salesforce_Clone_FC_NAME, SF_ERP_Salesforce_Clone_AR_CUST, SF_ERP_Salesforce_Clone_FC_NAME_LOCATION
vw_FAMOUS_SalesOrderHeader	insert + update	vw_FAMOUS_SalesOrderHeader:	vw_FAMOUS_Account:, vw_FAMOUS_Customer:	—	SF_ERP_Salesforce_Clone_AR_TRX_HEADER, SF_ERP_Salesforce_Clone_FC_NAME, SF_ERP_Salesforce_Clone_FC_NAME_LOCATION, SF_ERP_Salesforce_Clone_FC_SALEPERSON, SF_ERP_Salesforce_Clone_FC_SALE_TERMS
vw_FAMOUS_SalesOrderDetail	insert + update	vw_FAMOUS_SalesOrderDetail:	vw_FAMOUS_SalesOrderHeader:, vw_FAMOUS_Product:	—	SF_ERP_Salesforce_Clone_AR_TRX_LINE, SF_ERP_Salesforce_Clone_AR_TRX_HEADER, SF_ERP_Salesforce_Clone_IC_PRODUCT_ID
vw_FAMOUS_InvoiceHeader	insert + update	vw_FAMOUS_InvoiceHeader:	vw_FAMOUS_Account:, vw_FAMOUS_Customer:	—	SF_ERP_Salesforce_Clone_AR_TRX_HEADER, SF_ERP_Salesforce_Clone_FC_NAME, SF_ERP_Salesforce_Clone_FC_NAME_LOCATION, SF_ERP_Salesforce_Clone_FC_SALEPERSON, SF_ERP_Salesforce_Clone_FC_SALE_TERMS
vw_FAMOUS_InvoiceDetail	insert + update	vw_FAMOUS_InvoiceDetail:	vw_FAMOUS_InvoiceHeader:, vw_FAMOUS_Product:	—	SF_ERP_Salesforce_Clone_AR_TRX_LINE, SF_ERP_Salesforce_Clone_AR_TRX_HEADER, SF_ERP_Salesforce_Clone_IC_PRODUCT_ID
vw_FAMOUS_SalesOrderHistoryHeader	insert + update	vw_FAMOUS_SalesOrderHistoryHeader:	vw_FAMOUS_Account:, vw_FAMOUS_Customer:	—	SF_ERP_Salesforce_Clone_AR_TRX_HEADER, SF_ERP_Salesforce_Clone_FC_NAME, SF_ERP_Salesforce_Clone_FC_NAME_LOCATION, SF_ERP_Salesforce_Clone_FC_SALEPERSON, SF_ERP_Salesforce_Clone_FC_SALE_TERMS
vw_FAMOUS_SalesOrderHistoryDetail	insert + update	vw_FAMOUS_SalesOrderHistoryDetail:	vw_FAMOUS_SalesOrderHistoryHeader:, vw_FAMOUS_Product:	—	SF_ERP_Salesforce_Clone_AR_TRX_LINE, SF_ERP_Salesforce_Clone_AR_TRX_HEADER, SF_ERP_Salesforce_Clone_IC_PRODUCT_ID

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

• 1 — Account
• 2 — Child Account
• 3 — FAMOUS Salesperson
• 4 — FAMOUS Customer
• 5 — Customer To Account Reverse Lookup
• 6 — FAMOUS Ship To Address
• 10 — FAMOUS Sales Order Header
• 11 — FAMOUS Sales Order Detail
• 12 — FAMOUS Invoice Header
• 13 — FAMOUS Invoice Detail
• 14 — FAMOUS Sales Order History Header
• 15 — FAMOUS Sales Order History Detail
• 17 — Get User

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_FAMOUS_Account reads vw_FAMOUS_User:
• vw_FAMOUS_ChildAccount reads vw_FAMOUS_Account:, vw_FAMOUS_User:
• vw_FAMOUS_CustomerToAccountReverseLookup reads vw_FAMOUS_Account:, vw_FAMOUS_Customer:
• vw_FAMOUS_Customer reads vw_FAMOUS_Salesperson:, vw_FAMOUS_Account:
• vw_FAMOUS_ShipToAddress reads vw_FAMOUS_Salesperson:, vw_FAMOUS_ChildAccount:, vw_FAMOUS_Customer:
• vw_FAMOUS_InvoiceHeader reads vw_FAMOUS_Account:, vw_FAMOUS_Customer:
• vw_FAMOUS_InvoiceDetail reads vw_FAMOUS_InvoiceHeader:, vw_FAMOUS_Product:; no template in this set writes vw_FAMOUS_Product:
• vw_FAMOUS_SalesOrderHeader reads vw_FAMOUS_Account:, vw_FAMOUS_Customer:
• vw_FAMOUS_SalesOrderDetail reads vw_FAMOUS_SalesOrderHeader:, vw_FAMOUS_Product:; no template in this set writes vw_FAMOUS_Product:
• vw_FAMOUS_SalesOrderHistoryHeader reads vw_FAMOUS_Account:, vw_FAMOUS_Customer:
• vw_FAMOUS_SalesOrderHistoryDetail reads vw_FAMOUS_SalesOrderHistoryHeader:, vw_FAMOUS_Product:; no template in this set writes vw_FAMOUS_Product:

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	Account	15	CommercientSFommercient_ArCustomerCode → CommercientSF__Commercient_ArCustomerCode__c, BillingStreet → BillingStreet, BillingCity → BillingCity, BillingState → BillingState, BillingPostalCode → BillingPostalCode
Child Account	Account	16	CommercientSFommercient_ArCustomerCode → CommercientSF__Commercient_ArCustomerCode__c, ParentID → ParentID, BillingStreet → BillingStreet, BillingCity → BillingCity, BillingState → BillingState
FAMOUS Salesperson	FAMOUS_Salesperson__c	2	Salesperson_ID → salesperson_id__c, Salesperson_Name → salesperson_name__c
FAMOUS Customer	FAMOUS_Customer__c	13	LOOKUPTO_Account → account__c, LOOKUPTO_FAMOUS_Salesperson → famoussalesperson__c, Customer_ID → customer_id__c, Customer_Name → customer_name__c, Customer_Class → customer_class__c
Customer To Account Reverse Lookup	Account	2	CommercientSFommercient_ArCustomerCode → CommercientSF__Commercient_ArCustomerCode__c, FAMOUS_Customer → FAMOUS_Customer__c
FAMOUS Ship To Address	FAMOUS_ShipToAddress__c	23	LOOKUPTO_Account → account__c, LOOKUPTO_FAMOUS_Salesperson → famoussalesperson__c, LOOKUPTO_FAMOUS_Customer → famouscustomer__c, Location → location__c, Location_Sequence → location_sequence__c
FAMOUS Sales Order Header	FAMOUS_Sales_Order_Header__c	13	LOOKUPTO_Account → account__c, LOOKUPTO_FAMOUS_Customer → famouscustomer__c, Order_Number → order_number__c, Customer_ID → customer_id__c, Customer_Name → customer_name__c
FAMOUS Sales Order Detail	FAMOUS_Sales_Order_Detail__c	12	LOOKUPTO_FAMOUS_Sales_Order_Header → famoussalesorderheader__c, LOOKUPTO_Product2 → product2__c, Order_Number → order_number__c, Line_Number → line_number__c, Line_Type → line_type__c
FAMOUS Invoice Header	FAMOUS_Invoice_Header__c	20	LOOKUPTO_Account → account__c, LOOKUPTO_FAMOUS_Customer → famouscustomer__c, Order_Number → order_number__c, Customer_ID → customer_id__c, Customer_Name → customer_name__c
FAMOUS Invoice Detail	FAMOUS_Invoice_Detail__c	13	LOOKUPTO_FAMOUS_Invoice_Header → famousinvoiceheader__c, LOOKUPTO_Product2 → product2__c, Order_Number → order_number__c, Line_Number → line_number__c, Line_Type → line_type__c
FAMOUS Sales Order History Header	FAMOUS_Sales_Order_History_Header__c	13	LOOKUPTO_Account → account__c, LOOKUPTO_FAMOUS_Customer → famouscustomer__c, Order_Number → order_number__c, Customer_ID → customer_id__c, Customer_Name → customer_name__c
FAMOUS Sales Order History Detail	FAMOUS_Sales_Order_History_Detail__c	12	LOOKUPTO_FAMOUS_Sales_Order_History_Header → famoussalesorderhistoryheader__c, LOOKUPTO_Product2 → product2__c, Order_Number → order_number__c, Line_Number → line_number__c, Line_Type → line_type__c

6. Community templates

The catalogue carries 15 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: 15
• Default operations: insert on 15, update on 15, delete on 15
• Marked circular-sync: 0
• Licence groups they span: 8
• Destination objects: Account, Product2, FAMOUS_Customer__c, FAMOUS_Invoice_Detail__c, FAMOUS_Invoice_Header__c, FAMOUS_Item__c, FAMOUS_Sales_Order_Detail__c, FAMOUS_Sales_Order_Header__c, FAMOUS_Sales_Order_History_Detail__c, FAMOUS_Sales_Order_History_Header__c, FAMOUS_Salesperson__c, FAMOUS_ShipToAddress__c
• Object display names: Account, Child Account, Customer To Account Reverse Lookup, FAMOUS Customer, FAMOUS Invoice Detail, FAMOUS Invoice Header, FAMOUS Item, FAMOUS Sales Order Detail, FAMOUS Sales Order Header, FAMOUS Sales Order History Detail, FAMOUS Sales Order History Header, FAMOUS Salesperson and 3 more
• Template groups: Account, Salesorder, Product, 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_FAMOUS_User
• vw_FAMOUS_Account
• vw_FAMOUS_ChildAccount
• vw_FAMOUS_CustomerToAccountReverseLookup
• vw_FAMOUS_Customer
• vw_FAMOUS_ShipToAddress
• vw_FAMOUS_InvoiceHeader
• vw_FAMOUS_InvoiceDetail
• vw_FAMOUS_SalesOrderHeader
• vw_FAMOUS_SalesOrderDetail
• vw_FAMOUS_SalesOrderHistoryHeader
• vw_FAMOUS_SalesOrderHistoryDetail
• vw_FAMOUS_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 Famous → 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.