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

CRMPro → Salesforce — NetSuite: 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/netsuite.md, and that skill’s ERP table is what points at it. What follows is only what the shipped NetSuite → 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 users to Salesforce. New records are created, existing ones updated, and records removed in the ERP are deleted.	users	—
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, CommercientSF13__NETSUITE_CUSTOMERS__c, CommercientSF13__NETSUITE_SalesPerson__c	SF_ERP_Salesforce_Clone_CUSTOMER, SF_ERP_Salesforce_Clone_CUSTOMERADDRESSBOOK, 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.	CommercientSF13__NETSUITE_CUSTOMERADDRESSBOOK__c	SF_ERP_Salesforce_Clone_CUSTOMERADDRESSBOOK, SF_ERP_Salesforce_Clone_CUSTOMER
Product	ERP ITEM, INVENTORYITEM, ASSEMBLYITEM data becomes CommercientSF13__NETSUITE_ITEM__c, CommercientSF13__NETSUITE_Warehouse__c, Product2 in Salesforce. New records are created and existing ones updated; none are deleted.	CommercientSF13__NETSUITE_ITEM__c, CommercientSF13__NETSUITE_Warehouse__c, Product2	SF_ERP_Salesforce_Clone_ITEM, SF_ERP_Salesforce_Clone_InventoryItem
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.	CommercientSF13__NETSUITE_INVOICE__c, CommercientSF13__NETSUITE_INVOICEITEM__c	SF_ERP_Salesforce_Clone_INVOICE, CommercientFlags, SF_ERP_Salesforce_Clone_INVOICEITEM
Pricebook	ERP PRICELIST, ASSEMBLYITEM, NONINVENTORYRESALEITEM data becomes PriceBook2, PricebookEntry in Salesforce. New records are created and existing ones updated; none are deleted.	PriceBook2, PricebookEntry	SF_ERP_Salesforce_Clone_PriceList
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.	CommercientSF13__NETSUITE_SALESORDER__c, CommercientSF13__NETSUITE_SALESORDERITEM__c	SF_ERP_Salesforce_Clone_SALESORDER, CommercientFlags, SF_ERP_Salesforce_Clone_SALESORDERITEM

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 USER	users	—	0	vw_NETSUITE_User	1=0	'' / ''	1
Account	Account	CommercientSF__Commercient_ArCustomerCode__c	1	vw_NETSUITE_Account	vw_NETSUITE_Account	'' / ''	1
NetSuite Salesperson	CommercientSF13__NETSUITE_SalesPerson__c	CommercientSF13__ExternalKey__c	1	vw_NETSUITE_SalesPerson	vw_NETSUITE_SalesPerson	CommercientSF13__ / __c	1
Account-Child	Account	CommercientSF__Commercient_ArCustomerCode__c	2	vw_NETSUITE_Account	vw_NETSUITE_Account_Child	'' / ''	1
Customer	CommercientSF13__NETSUITE_CUSTOMERS__c	CommercientSF13__ExternalKey__c	3	vw_NETSUITE_Customer	vw_NETSUITE_Customer	CommercientSF13__ / __c	1
Customer To Account Reverse Lookup	Account	CommercientSF__Commercient_ArCustomerCode__c	4	vw_NETSUITE_CustomerToAccountLookup	vw_NETSUITE_CustomerToAccountLookup	'' / ''	1
Customer Address Book	CommercientSF13__NETSUITE_CUSTOMERADDRESSBOOK__c	CommercientSF13__ExternalKey__c	5	vw_NETSUITE_CustomerAddressBook	vw_NETSUITE_CustomerAddressBook	CommercientSF13__ / __c	1
SalesOrder	CommercientSF13__NETSUITE_SALESORDER__c	CommercientSF13__ExternalKey__c	6	vw_NETSUITE_SalesOrder	vw_NETSUITE_SalesOrder	CommercientSF13__ / __c	1
salesOrder Line	CommercientSF13__NETSUITE_SALESORDERITEM__c	CommercientSF13__ExternalKey__c	7	vw_NETSUITE_SalesOrderLine	vw_NETSUITE_SalesOrderLine	CommercientSF13__ / __c	1
Invoice	CommercientSF13__NETSUITE_INVOICE__c	CommercientSF13__ExternalKey__c	8	vw_NETSUITE_Invoice	vw_NETSUITE_Invoice	CommercientSF13__ / __c	1
Invoice Line	CommercientSF13__NETSUITE_INVOICEITEM__c	CommercientSF13__ExternalKey__c	9	vw_NETSUITE_InvoiceLine	vw_NETSUITE_InvoiceLine	CommercientSF13__ / __c	1
Contact	Contact	ExternalKey__c	10	vw_NETSUITE_Contact	vw_NETSUITE_Contact	'' / ''	1
Item	CommercientSF13__NETSUITE_ITEM__c	CommercientSF13__ExternalKey__c	11	vw_NETSUITE_Item	vw_NETSUITE_Item	CommercientSF13__ / __c	1
Product	Product2	CommercientSF__ExternalKey__c	12	vw_NETSUITE_Product	vw_NETSUITE_Product	'' / ''	1
ProductToItemReverseLookup	CommercientSF13__NETSUITE_ITEM__c	CommercientSF13__ExternalKey__c	13	vw_NETSUITE_ProductToItemReverseLookup	vw_NETSUITE_ProductToItemReverseLookup	CommercientSF13__ / __c	1
Item Warehouse	CommercientSF13__NETSUITE_Warehouse__c	CommercientSF13__ExternalKey__c	14	vw_NETSUITE_ItemWarehouse	vw_NETSUITE_ItemWarehouse	CommercientSF13__ / __c	1
PriceBook2	PriceBook2	ExternalKey__c	14	vw_NETSUITE_PriceBook2	vw_NETSUITE_PriceBook2	'' / ''	1
Create Standard PriceBook	PricebookEntry	ExternalKey__c	15	vw_NETSUITE_StandardProductPriceBook	vw_NETSUITE_StandardProductPriceBook_Create	'' / ''	1
Update Standard PriceBook	PricebookEntry	ExternalKey__c	16	vw_NETSUITE_StandardProductPriceBook	vw_NETSUITE_StandardProductPriceBook_Update	'' / ''	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, 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, PriceBook2, Create Standard PriceBook — 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_NETSUITE_Account	insert + update	vw_NETSUITE_Account:	vw_NETSUITE_SalesPerson:, vw_NETSUITE_User:	—	SF_ERP_Salesforce_Clone_CUSTOMER, SF_ERP_Salesforce_Clone_CUSTOMERADDRESSBOOK
vw_NETSUITE_SalesPerson	insert + update	vw_NETSUITE_SalesPerson:	—	ExternalKey	SF_ERP_Salesforce_Clone_EMPLOYEE
vw_NETSUITE_Account_Child	insert + update	vw_NETSUITE_Account:	vw_NETSUITE_SalesPerson:, vw_NETSUITE_User:	—	SF_ERP_Salesforce_Clone_CUSTOMER, SF_ERP_Salesforce_Clone_CUSTOMERADDRESSBOOK
vw_NETSUITE_Customer	insert + update	vw_NETSUITE_Customer:	vw_NETSUITE_Account:	ExternalKey	SF_ERP_Salesforce_Clone_CUSTOMER
vw_NETSUITE_CustomerToAccountLookup	insert + update	vw_NETSUITE_CustomerToAccountLookup:	vw_NETSUITE_Customer:	—	SF_ERP_Salesforce_Clone_CUSTOMER
vw_NETSUITE_CustomerAddressBook	insert + update	vw_NETSUITE_CustomerAddressBook:	vw_NETSUITE_Account:, vw_NETSUITE_Customer:	ExternalKey	SF_ERP_Salesforce_Clone_CUSTOMERADDRESSBOOK, SF_ERP_Salesforce_Clone_CUSTOMER
vw_NETSUITE_SalesOrder	insert + update	vw_NETSUITE_SalesOrder:	vw_NETSUITE_Account:, vw_NETSUITE_Customer:	ExternalKey	SF_ERP_Salesforce_Clone_SALESORDER, CommercientFlags
vw_NETSUITE_SalesOrderLine	insert + update	vw_NETSUITE_SalesOrderLine:	vw_NETSUITE_SalesOrder:	ExternalKey	SF_ERP_Salesforce_Clone_SALESORDERITEM, SF_ERP_Salesforce_Clone_SALESORDER
vw_NETSUITE_Invoice	insert + update	vw_NETSUITE_Invoice:	vw_NETSUITE_Account:, vw_NETSUITE_Customer:	ExternalKey	SF_ERP_Salesforce_Clone_INVOICE, CommercientFlags
vw_NETSUITE_InvoiceLine	insert + update	vw_NETSUITE_InvoiceLine:	vw_NETSUITE_Invoice:	ExternalKey	SF_ERP_Salesforce_Clone_INVOICEITEM, SF_ERP_Salesforce_Clone_INVOICE
vw_NETSUITE_Contact	insert + update	vw_NETSUITE_Contact:	vw_NETSUITE_Account:, vw_NETSUITE_Customer:	ExternalKey__c	SF_ERP_Salesforce_Clone_CONTACT
vw_NETSUITE_Item	insert + update	vw_NETSUITE_Item:	—	ExternalKey	SF_ERP_Salesforce_Clone_ITEM
vw_NETSUITE_Product	insert + update	vw_NETSUITE_Product:	vw_NETSUITE_Item:	—	SF_ERP_Salesforce_Clone_ITEM
vw_NETSUITE_ProductToItemReverseLookup	insert + update	vw_NETSUITE_ProductToItemReverseLookup:	vw_NETSUITE_Product:	—	SF_ERP_Salesforce_Clone_ITEM
vw_NETSUITE_ItemWarehouse	insert + update	vw_NETSUITE_ItemWarehouse:	vw_NETSUITE_Product:, vw_NETSUITE_Item:	ExternalKey	SF_ERP_Salesforce_Clone_InventoryItem
vw_NETSUITE_StandardProductPriceBook_Create	insert-only	—	vw_NETSUITE_Product:	ExternalKey__c	SF_ERP_Salesforce_Clone_PriceList
vw_NETSUITE_StandardProductPriceBook_Update	insert + update	—	—	ExternalKey__c	SF_ERP_Salesforce_Clone_PriceList

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

• 0 — GET USER
• 1 — Account, NetSuite Salesperson
• 2 — Account-Child
• 3 — Customer
• 4 — Customer To Account Reverse Lookup
• 5 — Customer Address Book
• 6 — SalesOrder
• 7 — salesOrder Line
• 8 — Invoice
• 9 — Invoice Line
• 10 — Contact
• 11 — Item
• 12 — Product
• 13 — ProductToItemReverseLookup
• 14 — Item Warehouse, PriceBook2
• 15 — Create Standard PriceBook
• 16 — Update Standard PriceBook

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_NETSUITE_Account reads vw_NETSUITE_SalesPerson:, vw_NETSUITE_User:
• vw_NETSUITE_Account_Child reads vw_NETSUITE_SalesPerson:, vw_NETSUITE_User:
• vw_NETSUITE_CustomerToAccountLookup reads vw_NETSUITE_Customer:
• vw_NETSUITE_Contact reads vw_NETSUITE_Account:, vw_NETSUITE_Customer:
• vw_NETSUITE_Customer reads vw_NETSUITE_Account:
• vw_NETSUITE_CustomerAddressBook reads vw_NETSUITE_Account:, vw_NETSUITE_Customer:
• vw_NETSUITE_ProductToItemReverseLookup reads vw_NETSUITE_Product:
• vw_NETSUITE_ItemWarehouse reads vw_NETSUITE_Product:, vw_NETSUITE_Item:
• vw_NETSUITE_Invoice reads vw_NETSUITE_Account:, vw_NETSUITE_Customer:
• vw_NETSUITE_InvoiceLine reads vw_NETSUITE_Invoice:
• vw_NETSUITE_StandardProductPriceBook_Create reads vw_NETSUITE_Product:
• vw_NETSUITE_Product reads vw_NETSUITE_Item:
• vw_NETSUITE_SalesOrder reads vw_NETSUITE_Account:, vw_NETSUITE_Customer:
• vw_NETSUITE_SalesOrderLine reads vw_NETSUITE_SalesOrder:

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	internalId → CommercientSF__Commercient_ArCustomerCode__c, entityId → Name, phone → Phone, addr1, addr2, addr3 → BillingStreet, city → BillingCity
NetSuite Salesperson	CommercientSF13__NETSUITE_SalesPerson__c	74	accountNumberField → accountNumberField, defaultAddressField → CommercientSF13__defaultAddressField__c, adpIdField → CommercientSF13__adpIdField__c, altNameField → CommercientSF13__altNameField__c, billPayFieldSpecified → billPayFieldSpecified
Customer	CommercientSF13__NETSUITE_CUSTOMERS__c	145	internalId → CommercientSF13__ExternalKey__c, entityId → Name, SFDCID → Account, customForminternalId → customForminternalIdField, customFormexternalId → customFormexternalIdField
Customer To Account Reverse Lookup	Account	2	internalId → CommercientSF__Commercient_ArCustomerCode__c, SFDCID → CommercientSF13__Customer__c
Customer Address Book	CommercientSF13__NETSUITE_CUSTOMERADDRESSBOOK__c	22	parentId,internalId → CommercientSF13__ExternalKey__c, addressee,entityId → CommercientSF13__Name__c, SFDCID → CommercientSF13__Account__c, SFDCID → CommercientSF13__Customer__c, parentId → CommercientSF13__parentIdField__c
SalesOrder	CommercientSF13__NETSUITE_SALESORDER__c	197	internalId → CommercientSF13__ExternalKey__c, tranId → Name, entityinternalId → Account, entityinternalId → Customer, createdDate → createdDateField
salesOrder Line	CommercientSF13__NETSUITE_SALESORDERITEM__c	93	internalId, line → CommercientSF13__ExternalKey__c, internalId, line, tranId → Name, SFDCID → Salesorder, internalId → internalId, jobinternalId → jobinternalId
Invoice	CommercientSF13__NETSUITE_INVOICE__c	160	internalId → CommercientSF13__ExternalKey__c, tranId → Name, entityinternalId → Account, entityinternalId → Customer, createdDate → createdDateField
Invoice Line	CommercientSF13__NETSUITE_INVOICEITEM__c	73	internalId, line → CommercientSF13__ExternalKey__c, internalId, line, tranId → Name, SFDCID → CommercientSF13__Invoice__c, internalId → internalIdField, jobinternalId → jobinternalIdField
Product	Product2	6	internalId → CommercientSF__ExternalKey__c, itemId → Name, itemId → ProductCode, stockDescription → Description, isInactive → IsActive
ProductToItemReverseLookup	CommercientSF13__NETSUITE_ITEM__c	2	internalId → CommercientSF13__ExternalKey__c, SFDCID → CommercientSF13__Product__c
PriceBook2	PriceBook2	2	ExternalKey__c → ExternalKey__c, Name → Name
Create Standard PriceBook	PricebookEntry	5	Id → ExternalKey__c, SFDCID → Pricebook2ID, SFDCID → Product2ID, value → UnitPrice, IsActive → IsActive
Update Standard PriceBook	PricebookEntry	3	Id → ExternalKey__c, value → UnitPrice

6. Community templates

The catalogue carries 253 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: 253
• Default operations: insert on 253, update on 253, delete on 253
• Marked circular-sync: 2
• Licence groups they span: 12
• Destination objects: Account, CommercientSF13__NETSUITE_ITEM__c, PricebookEntry, Product2, CommercientSF13__NETSUITE_INVOICE__c, CommercientSF13__NETSUITE_CUSTOMERS__c, CommercientSF13__NETSUITE_INVOICEITEM__c, CommercientSF13__NETSUITE_SALESORDER__c, CommercientSF13__NETSUITE_SALESORDERITEM__c, CommercientSF13__NETSUITE_CUSTOMERADDRESSBOOK__c, CommercientSF13__NETSUITE_Warehouse__c, Contact, CommercientSF13__NETSUITE_SalesPerson__c, NETSUITE_RMA_Order_Line__c, CommercientSF13__ACCOUNTMATCHING__c, CommercientSF13__NETSUITE_TERM__c, NETSUITE_RMA_Order__c, Pricebook2, Pricebookentry, CreditMemo__c, 11 more and 2 custom objects
• Object display names: Account, Customer To Account Reverse Lookup, Account-Child, Contact, Customer Address Book, Invoice, Product, Customer, Invoice Line, Item, Item Warehouse, SalesOrder, 54 more and 3 further templates
• Template groups: Account, Product, Salesorder, Invoice, Customer Multi Ship Addresses, CRM Order and Line

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_NETSUITE_User
• vw_NETSUITE_Account
• vw_NETSUITE_CustomerToAccountLookup
• vw_NETSUITE_Contact
• vw_NETSUITE_Customer
• vw_NETSUITE_CustomerAddressBook
• vw_NETSUITE_Item
• vw_NETSUITE_ProductToItemReverseLookup
• vw_NETSUITE_ItemWarehouse
• vw_NETSUITE_Invoice
• vw_NETSUITE_InvoiceLine
• vw_NETSUITE_PriceBook2
• vw_NETSUITE_StandardProductPriceBook
• vw_NETSUITE_Product
• vw_NETSUITE_SalesOrder
• vw_NETSUITE_SalesOrderLine
• vw_NETSUITE_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 NetSuite → 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.