CRMPro → Salesforce — Infor SyteLine V9: what the shipped templates set up

CRMPro → Salesforce — Infor SyteLine V9: 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/infor-syteline-v9.md, and that skill’s ERP table is what points at it. What follows is only what the shipped Infor SyteLine V9 → 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, Contact, CommercientSF18__customer_all__c, CommercientSF18__slsman_all__c	SF_ERP_Salesforce_Clone_customer_all, SF_ERP_Salesforce_Clone_custaddr, SF_ERP_Salesforce_Clone_customer_contact_mst, SF_ERP_Salesforce_Clone_contact_mst, SF_ERP_Salesforce_Clone_slsman_all
CRM Opportunity and Line	The templates push Opportunity, OpportunityLineItem to Salesforce. New records are created and existing ones updated; none are deleted.	Opportunity, OpportunityLineItem	SF_ERP_Salesforce_Clone_co_all, CommercientFlags, SF_ERP_Salesforce_Clone_coitem_all
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.	CommercientSF18__custaddr__c	SF_ERP_Salesforce_Clone_custaddr, SF_ERP_Salesforce_Clone_customer_all
Product	ERP ITEM_ALL, ITEMPRICE_MST, ITEMWHSE_ALL data becomes CommercientSF18__item_all__c, CommercientSF18__itemwhse_all__c, Product2 in Salesforce. New records are created and existing ones updated; none are deleted.	CommercientSF18__item_all__c, CommercientSF18__itemwhse_all__c, Product2	SF_ERP_Salesforce_Clone_item_all, SF_ERP_Salesforce_Clone_itemwhse_all
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.	CommercientSF18__inv_hdr_all__c, CommercientSF18__inv_item_all__c	SF_ERP_Salesforce_Clone_inv_hdr_all, SF_ERP_Salesforce_Clone_inv_item_all
Pricebook	ERP ITEMPRICE_MST data becomes PricebookEntry, PriceBookEntry in Salesforce. New records are created and existing ones updated; none are deleted.	PricebookEntry, PriceBookEntry	SF_ERP_Salesforce_Clone_itemprice_all, SF_ERP_Salesforce_Clone_itemprice_mst
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.	CommercientSF18__co_all__c, CommercientSF18__coitem_all__c	SF_ERP_Salesforce_Clone_co_all, SF_ERP_Salesforce_Clone_coitem_all

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	User	—	0	vw_INFORSYTELINEV9_GetUser	SELECT 1=0	'' / ''	1
SYNC SALESPERSON	CommercientSF18__slsman_all__c	CommercientSF18__ExternalKey__c	1	vw_INFORSYTELINEV9_Salesperson	vw_INFORSYTELINEV9_Salesperson	CommercientSF18__ / __c	—
SYNC ACCOUNT	Account	CommercientSF__Commercient_ArCustomerCode__c	2	vw_INFORSYTELINEV9_Account	vw_INFORSYTELINEV9_Account	'' / ''	—
SYNC SHIPTOACCOUNT	Account	CommercientSF__Commercient_ArCustomerCode__c	3	vw_INFORSYTELINEV9_ShipToAccount	vw_INFORSYTELINEV9_ShipToAccount	'' / ''	—
SYNC CUSTOMER	CommercientSF18__customer_all__c	CommercientSF18__ExternalKey__c	4	vw_INFORSYTELINEV9_Customer	vw_INFORSYTELINEV9_Customer	CommercientSF18__ / __c	—
SYNC CUSTOMERTOACCOUNTLOOKUP	Account	CommercientSF__Commercient_ArCustomerCode__c	5	vw_INFORSYTELINEV9_CustomerToAccountLookup	vw_INFORSYTELINEV9_CustomerToAccountLookup	'' / ''	—
SYNC CONTACT	Contact	ExternalKey__c	5	vw_INFORSYTELINEV9_Contact	vw_INFORSYTELINEV9_Contact	'' / ''	1
SYNC ADDRESS	CommercientSF18__custaddr__c	CommercientSF18__ExternalKey__c	6	vw_INFORSYTELINEV9_Address	vw_INFORSYTELINEV9_Address	CommercientSF18__ / __c	—
SYNC PRODUCT	Product2	CommercientSF__ExternalKey__c	7	vw_INFORSYTELINEV9_Product	vw_INFORSYTELINEV9_Product	'' / ''	—
SYNC ITEM	CommercientSF18__item_all__c	CommercientSF18__ExternalKey__c	8	vw_INFORSYTELINEV9_Item	vw_INFORSYTELINEV9_Item	CommercientSF18__ / __c	—
SYNC ITEMTOPRODUCTLOOKUP	Product2	CommercientSF__ExternalKey__c	9	vw_INFORSYTELINEV9_ItemToProductLookup	vw_INFORSYTELINEV9_ItemToProductLookup	'' / ''	—
SYNC ITEMWAREHOUSE	CommercientSF18__itemwhse_all__c	CommercientSF18__ExternalKey__c	10	vw_INFORSYTELINEV9_ItemWarehouse	vw_INFORSYTELINEV9_ItemWarehouse	CommercientSF18__ / __c	—
SYNC STANDARDPRICEBOOK	PricebookEntry	ExternalKey__c	11	vw_INFORSYTELINEV9_StandardPriceBook	vw_INFORSYTELINEV9_StandardPriceBook	'' / ''	—
SYNC STANDARDPRICEBOOK UPDATE	PriceBookEntry	ExternalKey__c	12	vw_INFORSYTELINEV9_StandardPriceBook	vw_INFORSYTELINEV9_StandardPriceBook_Update	'' / ''	—
SYNC CUSTOMERORDER	CommercientSF18__co_all__c	CommercientSF18__ExternalKey__c	13	vw_INFORSYTELINEV9_CustomerOrder	vw_INFORSYTELINEV9_CustomerOrder	CommercientSF18__ / __c	—
Estimate	Opportunity	ExternalKey__c	14	vw_INFORSYTELINEV9_Estimate	vw_INFORSYTELINEV9_Estimate	'' / ''	—
SYNC CUSTOMERORDERLINE	CommercientSF18__coitem_all__c	CommercientSF18__ExternalKey__c	14	vw_INFORSYTELINEV9_CustomerOrderLine	vw_INFORSYTELINEV9_CustomerOrderLine	CommercientSF18__ / __c	—
EstimateLine	OpportunityLineItem	ExternalKey__c	15	vw_INFORSYTELINEV9_EstimateLine	vw_INFORSYTELINEV9_EstimateLine	'' / ''	—
SYNC INVOICEHEADER	CommercientSF18__inv_hdr_all__c	CommercientSF18__ExternalKey__c	15	vw_INFORSYTELINEV9_InvoiceHeader	vw_INFORSYTELINEV9_InvoiceHeader	CommercientSF18__ / __c	—
SYNC INVOICELINEITEM	CommercientSF18__inv_item_all__c	CommercientSF18__ExternalKey__c	16	vw_INFORSYTELINEV9_InvoiceLineItem	vw_INFORSYTELINEV9_InvoiceLineItem	CommercientSF18__ / __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 SYNC STANDARDPRICEBOOK; IsAccountMatching is set on SYNC ACCOUNT, SYNC SHIPTOACCOUNT. Text columns a template does not use are inserted as '' rather than left NULL. Get_SOQL_Query carries a query on Get User, SYNC STANDARDPRICEBOOK — 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	Source tables
vw_INFORSYTELINEV9_Salesperson	insert + update	vw_INFORSYTELINEV9_Salesperson:	—	SF_ERP_Salesforce_Clone_slsman_all
vw_INFORSYTELINEV9_Account	insert + update	vw_INFORSYTELINEV9_Account:	vw_INFORSYTELINEV9_GetUser:	SF_ERP_Salesforce_Clone_customer_all, SF_ERP_Salesforce_Clone_custaddr
vw_INFORSYTELINEV9_ShipToAccount	insert + update	vw_INFORSYTELINEV9_ShipToAccount:	vw_INFORSYTELINEV9_GetUser:, vw_INFORSYTELINEV9_Account:	SF_ERP_Salesforce_Clone_customer_all, SF_ERP_Salesforce_Clone_custaddr
vw_INFORSYTELINEV9_Customer	insert + update	vw_INFORSYTELINEV9_Customer:	vw_INFORSYTELINEV9_Account:	SF_ERP_Salesforce_Clone_customer_all, SF_ERP_Salesforce_Clone_custaddr
vw_INFORSYTELINEV9_CustomerToAccountLookup	insert + update	vw_INFORSYTELINEV9_CustomerToAccountLookup:	vw_INFORSYTELINEV9_Customer:	SF_ERP_Salesforce_Clone_customer_all
vw_INFORSYTELINEV9_Contact	insert + update	vw_INFORSYTELINEV9_Contact:	vw_INFORSYTELINEV9_ShipToAccount:	SF_ERP_Salesforce_Clone_customer_contact_mst, SF_ERP_Salesforce_Clone_contact_mst
vw_INFORSYTELINEV9_Address	insert + update	vw_INFORSYTELINEV9_Address:	vw_INFORSYTELINEV9_Account:, vw_INFORSYTELINEV9_Customer:	SF_ERP_Salesforce_Clone_custaddr, SF_ERP_Salesforce_Clone_customer_all
vw_INFORSYTELINEV9_Product	insert + update	vw_INFORSYTELINEV9_Product:	—	SF_ERP_Salesforce_Clone_item_all
vw_INFORSYTELINEV9_Item	insert + update	vw_INFORSYTELINEV9_Item:	vw_INFORSYTELINEV9_Product:	SF_ERP_Salesforce_Clone_item_all
vw_INFORSYTELINEV9_ItemToProductLookup	insert + update	vw_INFORSYTELINEV9_ItemToProductLookup:	vw_INFORSYTELINEV9_Item:	SF_ERP_Salesforce_Clone_item_all
vw_INFORSYTELINEV9_ItemWarehouse	insert + update	vw_INFORSYTELINEV9_ItemWarehouse:	vw_INFORSYTELINEV9_Product:, vw_INFORSYTELINEV9_Item:	SF_ERP_Salesforce_Clone_itemwhse_all
vw_INFORSYTELINEV9_StandardPriceBook	insert + update	vw_INFORSYTELINEV9_StandardPriceBook:	vw_INFORSYTELINEV9_Product:	SF_ERP_Salesforce_Clone_itemprice_all
vw_INFORSYTELINEV9_StandardPriceBook_Update	insert + update	vw_INFORSYTELINEV9_StandardPriceBook:	vw_INFORSYTELINEV9_Product:	SF_ERP_Salesforce_Clone_itemprice_mst
vw_INFORSYTELINEV9_CustomerOrder	insert + update	vw_INFORSYTELINEV9_CustomerOrder:	vw_INFORSYTELINEV9_Account:, vw_INFORSYTELINEV9_Customer:	SF_ERP_Salesforce_Clone_co_all
vw_INFORSYTELINEV9_Estimate	insert + update	vw_INFORSYTELINEV9_Estimate:	vw_INFORSYTELINEV9_Account:, vw_INFORSYTELINEV9_Customer:, vw_INFORSYTELINEV9_StandardPriceBook:	SF_ERP_Salesforce_Clone_co_all, CommercientFlags
vw_INFORSYTELINEV9_CustomerOrderLine	insert + update	vw_INFORSYTELINEV9_CustomerOrderLine:	vw_INFORSYTELINEV9_CustomerOrder:, vw_INFORSYTELINEV9_Item:	SF_ERP_Salesforce_Clone_coitem_all
vw_INFORSYTELINEV9_EstimateLine	insert + update	vw_INFORSYTELINEV9_EstimateLine:	vw_INFORSYTELINEV9_Estimate:, vw_INFORSYTELINEV9_Product:	SF_ERP_Salesforce_Clone_coitem_all
vw_INFORSYTELINEV9_InvoiceHeader	insert + update	vw_INFORSYTELINEV9_InvoiceHeader:	vw_INFORSYTELINEV9_Account:, vw_INFORSYTELINEV9_Customer:	SF_ERP_Salesforce_Clone_inv_hdr_all
vw_INFORSYTELINEV9_InvoiceLineItem	insert + update	vw_INFORSYTELINEV9_InvoiceLineItem:	vw_INFORSYTELINEV9_InvoiceHeader:, vw_INFORSYTELINEV9_Item:	SF_ERP_Salesforce_Clone_inv_item_all

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 — SYNC SALESPERSON
• 2 — SYNC ACCOUNT
• 3 — SYNC SHIPTOACCOUNT
• 4 — SYNC CUSTOMER
• 5 — SYNC CUSTOMERTOACCOUNTLOOKUP, SYNC CONTACT
• 6 — SYNC ADDRESS
• 7 — SYNC PRODUCT
• 8 — SYNC ITEM
• 9 — SYNC ITEMTOPRODUCTLOOKUP
• 10 — SYNC ITEMWAREHOUSE
• 11 — SYNC STANDARDPRICEBOOK
• 12 — SYNC STANDARDPRICEBOOK UPDATE
• 13 — SYNC CUSTOMERORDER
• 14 — Estimate, SYNC CUSTOMERORDERLINE
• 15 — EstimateLine, SYNC INVOICEHEADER
• 16 — SYNC INVOICELINEITEM

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_INFORSYTELINEV9_Account reads vw_INFORSYTELINEV9_GetUser:
• vw_INFORSYTELINEV9_ShipToAccount reads vw_INFORSYTELINEV9_GetUser:, vw_INFORSYTELINEV9_Account:
• vw_INFORSYTELINEV9_CustomerToAccountLookup reads vw_INFORSYTELINEV9_Customer:
• vw_INFORSYTELINEV9_Contact reads vw_INFORSYTELINEV9_ShipToAccount:
• vw_INFORSYTELINEV9_Estimate reads vw_INFORSYTELINEV9_Account:, vw_INFORSYTELINEV9_Customer:, vw_INFORSYTELINEV9_StandardPriceBook:
• vw_INFORSYTELINEV9_EstimateLine reads vw_INFORSYTELINEV9_Estimate:, vw_INFORSYTELINEV9_Product:
• vw_INFORSYTELINEV9_Customer reads vw_INFORSYTELINEV9_Account:
• vw_INFORSYTELINEV9_Address reads vw_INFORSYTELINEV9_Account:, vw_INFORSYTELINEV9_Customer:
• vw_INFORSYTELINEV9_Item reads vw_INFORSYTELINEV9_Product:
• vw_INFORSYTELINEV9_ItemWarehouse reads vw_INFORSYTELINEV9_Product:, vw_INFORSYTELINEV9_Item:
• vw_INFORSYTELINEV9_InvoiceHeader reads vw_INFORSYTELINEV9_Account:, vw_INFORSYTELINEV9_Customer:
• vw_INFORSYTELINEV9_InvoiceLineItem reads vw_INFORSYTELINEV9_InvoiceHeader:, vw_INFORSYTELINEV9_Item:
• vw_INFORSYTELINEV9_StandardPriceBook reads vw_INFORSYTELINEV9_Product:
• vw_INFORSYTELINEV9_StandardPriceBook_Update reads vw_INFORSYTELINEV9_Product:
• vw_INFORSYTELINEV9_ItemToProductLookup reads vw_INFORSYTELINEV9_Item:
• vw_INFORSYTELINEV9_CustomerOrder reads vw_INFORSYTELINEV9_Account:, vw_INFORSYTELINEV9_Customer:
• vw_INFORSYTELINEV9_CustomerOrderLine reads vw_INFORSYTELINEV9_CustomerOrder:, vw_INFORSYTELINEV9_Item:

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
SYNC SALESPERSON	CommercientSF18__slsman_all__c	13	site_ref, slsman → CommercientSF18__ExternalKey__c, site_ref, slsman → Name, site_ref → CommercientSF18__site_ref__c, slsman → CommercientSF18__slsman__c, outside → CommercientSF18__outside__c
SYNC ACCOUNT	Account	12	site_ref,cust_num,cust_seq → CommercientSF__Commercient_ArCustomerCode__c, name → Name, city → BillingCity, state → BillingState, country → BillingCountry
SYNC SHIPTOACCOUNT	Account	13	site_ref,cust_num,cust_seq → CommercientSF__Commercient_ArCustomerCode__c, BillingCustAddress.name → Name, BillingCustAddress.city → BillingCity, BillingCustAddress.state → BillingState, BillingCustAddress.country → BillingCountry
SYNC CUSTOMER	CommercientSF18__customer_all__c	110	site_ref, cust_num, cust_seq → CommercientSF18__ExternalKey__c, name → CommercientSF18__Name__c, site_ref → CommercientSF18__site_ref__c, cust_num → CommercientSF18__cust_num__c, cust_seq → CommercientSF18__cust_seq__c
SYNC CUSTOMERTOACCOUNTLOOKUP	Account	2	site_ref, cust_num, cust_seq → CommercientSF__Commercient_ArCustomerCode__c, SFDCID → CommercientSF18__Infor_Syteline_Customer__c
SYNC CONTACT	Contact	13	firstname → firstname, lastname → lastname, Phone → Phone, Email → Email, Title → Title
SYNC ADDRESS	CommercientSF18__custaddr__c	45	site_ref,cust_num,cust_seq → CommercientSF18__ExternalKey__c, name → CommercientSF18__Name__c, city → CommercientSF18__city__c, state → CommercientSF18__state__c, zip → CommercientSF18__zip__c
SYNC PRODUCT	Product2	4	site_ref, item → CommercientSF__ExternalKey__c, site_ref, item → Name, site_ref, item → ProductCode, description → Description
SYNC ITEM	CommercientSF18__item_all__c	71	site_ref, item → CommercientSF18__ExternalKey__c, item → Name, site_ref → CommercientSF18__site_ref__c, item → CommercientSF18__item__c, description → CommercientSF18__description__c
SYNC ITEMTOPRODUCTLOOKUP	Product2	2	site_ref, item → CommercientSF__ExternalKey__c, SFDCID → CommercientSF18__Infor_Syteline_Item__c
SYNC ITEMWAREHOUSE	CommercientSF18__itemwhse_all__c	53	site_ref,item,whse → CommercientSF18__ExternalKey__c, site_ref,item,whse → CommercientSF18__Name__c, site_ref → CommercientSF18__site_ref__c, whse → CommercientSF18__whse__c, qty_on_hand → CommercientSF18__qty_on_hand__c
SYNC STANDARDPRICEBOOK	PricebookEntry	5	site_ref, item, curr_code → ExternalKey__c, SFDCID → Pricebook2Id, SFDCID → Product2ID, IsActive → IsActive, unit_price1 → UnitPrice
SYNC STANDARDPRICEBOOK UPDATE	PriceBookEntry	3	site_ref, item, curr_code → ExternalKey__c, IsActive → IsActive, unit_price1 → UnitPrice
SYNC CUSTOMERORDER	CommercientSF18__co_all__c	54	site_ref,co_num → CommercientSF18__ExternalKey__c, site_ref,co_num → CommercientSF18__Name__c, site_ref → CommercientSF18__site_ref__c, type → CommercientSF18__type__c, co_num → CommercientSF18__co_num__c
Estimate	Opportunity	7	co_num → ExternalKey__c, co_num → Name, price → Amount, close_date → CloseDate, StageName → StageName
SYNC CUSTOMERORDERLINE	CommercientSF18__coitem_all__c	80	site_ref, co_num, co_line, co_release → CommercientSF18__ExternalKey__c, site_ref, co_num, co_line, co_release → CommercientSF18__Name__c, site_ref → CommercientSF18__site_ref__c, co_num → CommercientSF18__co_num__c, co_line → CommercientSF18__co_line__c
EstimateLine	OpportunityLineItem	5	co_num, co_line, co_release → ExternalKey__c, item → Product2Id, qty_ordered → Quantity, price → UnitPrice, co_num → OpportunityId
SYNC INVOICEHEADER	CommercientSF18__inv_hdr_all__c	33	site_ref, inv_num, inv_seq → CommercientSF18__ExternalKey__c, site_ref, inv_num, inv_seq → CommercientSF18__Name__c, site_ref → CommercientSF18__site_ref__c, inv_num → CommercientSF18__inv_num__c, inv_seq → CommercientSF18__inv_seq__c
SYNC INVOICELINEITEM	CommercientSF18__inv_item_all__c	23	site_ref,inv_num,inv_seq,inv_line,co_num,co_line,co_release → CommercientSF18__ExternalKey__c, site_ref,inv_num,inv_seq,inv_line,co_num,co_line,co_release → CommercientSF18__Name__c, site_ref → CommercientSF18__site_ref__c, inv_num → CommercientSF18__inv_num__c, inv_seq → CommercientSF18__inv_seq__c

6. Community templates

The catalogue carries 90 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: 90
• Default operations: insert on 90, update on 90, delete on 90
• Marked circular-sync: 5
• Licence groups they span: 12
• Destination objects: Account, Product2, CommercientSF18__coitem_all__c, PriceBookEntry, CommercientSF18__co_all__c, CommercientSF18__custaddr__c, CommercientSF18__customer_all__c, CommercientSF18__inv_hdr_all__c, CommercientSF18__inv_item_all__c, CommercientSF18__item_all__c, CommercientSF18__itemwhse_all__c, CommercientSF18__slsman_all__c, Contact, PricebookEntry, CommercientSF18__ACCOUNTMATCHING__c, Credit_Memo__c, Infor_Syteline_Contract_Price__c, Item_Customer_Price__c, Job_Master__c, Opportunity, 5 more and 6 custom objects
• Object display names: SYNC ADDRESS, SYNC CUSTOMER, SYNC CUSTOMERORDER, SYNC CUSTOMERORDERLINE, SYNC CUSTOMERTOACCOUNTLOOKUP, SYNC INVOICEHEADER, SYNC INVOICELINEITEM, SYNC ITEM, SYNC ITEMTOPRODUCTLOOKUP, SYNC ITEMWAREHOUSE, SYNC PRODUCT, SYNC SALESPERSON, 25 more and 5 further templates
• Template groups: Product, Account, Salesorder, Invoice, Customer Multi Ship Addresses, CRM Opportunity and Line, Purchase Order

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_INFORSYTELINEV9_GetUser
• vw_INFORSYTELINEV9_Account
• vw_INFORSYTELINEV9_ShipToAccount
• vw_INFORSYTELINEV9_CustomerToAccountLookup
• vw_INFORSYTELINEV9_Contact
• vw_INFORSYTELINEV9_Estimate
• vw_INFORSYTELINEV9_EstimateLine
• vw_INFORSYTELINEV9_Customer
• vw_INFORSYTELINEV9_Address
• vw_INFORSYTELINEV9_Item
• vw_INFORSYTELINEV9_ItemWarehouse
• vw_INFORSYTELINEV9_InvoiceHeader
• vw_INFORSYTELINEV9_InvoiceLineItem
• vw_INFORSYTELINEV9_StandardPriceBook
• vw_INFORSYTELINEV9_Product
• vw_INFORSYTELINEV9_ItemToProductLookup
• vw_INFORSYTELINEV9_CustomerOrder
• vw_INFORSYTELINEV9_CustomerOrderLine
• vw_INFORSYTELINEV9_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 Infor SyteLine V9 → 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.