CRMPro → Salesforce — Infor SyteLine V7 and V8: what the shipped templates set up

CRMPro → Salesforce — Infor SyteLine V7 and V8: 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-v7-and-v8.md, and that skill’s ERP table is what points at it. What follows is only what the shipped Infor SyteLine V7 and V8 → 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 Users	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_contact_all, SF_ERP_Salesforce_Clone_customer_contact_all, SF_ERP_Salesforce_Clone_slsman_all
CRM Opportunity and Line	ERP CO_ALL, COITEM_ALL data becomes Opportunity, OpportunityLineItem in 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, existing ones updated, and records removed in the ERP are deleted.	CommercientSF18__custaddr__c	SF_ERP_Salesforce_Clone_custaddr_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, CommercientFlags, SF_ERP_Salesforce_Clone_inv_item_all
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, CommercientFlags, 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 Users	User	CommercientSF6__SalespersonCode__c	1	vw_INFORSYTELINE_User	Select 1 = 0	'' / ''	1
SalesPerson	CommercientSF18__slsman_all__c	CommercientSF18__ExternalKey__c	1	vw_INFORSYTELINE_SalesPerson	vw_INFORSYTELINE_SalesPerson	CommercientSF18__ / __c	—
account	account	CommercientSF__Commercient_ArCustomerCode__c	2	vw_INFORSYTELINE_SFAccount	vw_INFORSYTELINE_CRM_Account	'' / ''	—
Customer	CommercientSF18__customer_all__c	CommercientSF18__ExternalKey__c	3	vw_INFORSYTELINE_Customer	vw_INFORSYTELINE_Customer	CommercientSF18__ / __c	—
Contact	Contact	ExternalKey__c	4	vw_INFORSYTELINE_Contact	vw_INFORSYTELINE_Contact	'' / ''	1
CustomerOrder	CommercientSF18__co_all__c	CommercientSF18__ExternalKey__c	4	vw_INFORSYTELINE_CustomerOrder	vw_INFORSYTELINE_CustomerOrder	CommercientSF18__ / __c	—
CustomerOrderLine	CommercientSF18__coitem_all__c	CommercientSF18__ExternalKey__c	5	vw_INFORSYTELINE_CustomerOrderLine	vw_INFORSYTELINE_CustomerOrderLine	CommercientSF18__ / __c	—
InvoiceHeader	CommercientSF18__inv_hdr_all__c	CommercientSF18__ExternalKey__c	6	vw_INFORSYTELINE_InvoiceHeader	vw_INFORSYTELINE_InvoiceHeader	CommercientSF18__ / __c	—
InvoiceLineItem	CommercientSF18__inv_item_all__c	CommercientSF18__ExternalKey__c	7	vw_INFORSYTELINE_InvoiceLineItem	vw_INFORSYTELINE_InvoiceLineItem	CommercientSF18__ / __c	—
Estimate	Opportunity	ExternalKey__c	8	vwEstimate	vw_INFORSYTELINE_Estimate	'' / ''	—
EstimateLine	OpportunityLineItem	ExternalKey__c	9	vwEstimateLine	vw_INFORSYTELINE_EstimateLine	'' / ''	—
Customer Address	CommercientSF18__custaddr__c	CommercientSF18__ExternalKey__c	9	vw_INFORSYTELINE_Address	vw_INFORSYTELINE_CustomerAddress	CommercientSF18__ / __c	1

Is_Active is inserted as 1 on Contact, Customer Address and as 0 on the rest, so some of these processes start active on import. Across the set they insert Is_Create_Entity 0, Is_Create_Fields 0, Sync_Batch_Size 200. 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 Users — 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_INFORSYTELINE_SalesPerson	insert + update	vw_INFORSYTELINE_SalesPerson:	—	—	SF_ERP_Salesforce_Clone_slsman_all
vw_INFORSYTELINE_CRM_Account	insert + update	—	vw_INFORSYTELINE_User:, vw_INFORSYTELINE_SalesPerson:, vw_SFAccount:	—	SF_ERP_Salesforce_Clone_customer_all, SF_ERP_Salesforce_Clone_custaddr
vw_INFORSYTELINE_Customer	insert-only	vw_INFORSYTELINE_Customer:	vw_INFORSYTELINE_SFAccount:, vw_INFORSYTELINE_SalesPerson:	—	SF_ERP_Salesforce_Clone_customer_all, SF_ERP_Salesforce_Clone_custaddr
vw_INFORSYTELINE_Contact	insert + update	vw_INFORSYTELINE_Contact:	vw_INFORSYTELINE_SFAccount:	—	SF_ERP_Salesforce_Clone_contact_all, SF_ERP_Salesforce_Clone_customer_contact_all
vw_INFORSYTELINE_CustomerOrder	insert + update	vw_INFORSYTELINE_CustomerOrder:	vw_INFORSYTELINE_SFAccount:, vw_INFORSYTELINE_Customer:, vw_INFORSYTELINE_SalesPerson:	—	SF_ERP_Salesforce_Clone_co_all, CommercientFlags
vw_INFORSYTELINE_CustomerOrderLine	insert + update	vw_INFORSYTELINE_CustomerOrderLine:	vw_INFORSYTELINE_CustomerOrder:	—	SF_ERP_Salesforce_Clone_coitem_all, CommercientFlags
vw_INFORSYTELINE_InvoiceHeader	insert + update	vw_INFORSYTELINE_InvoiceHeader:	vw_INFORSYTELINE_SFAccount:, vw_INFORSYTELINE_Customer:, vw_INFORSYTELINE_SalesPerson:	—	SF_ERP_Salesforce_Clone_inv_hdr_all, CommercientFlags
vw_INFORSYTELINE_InvoiceLineItem	insert + update	vw_INFORSYTELINE_InvoiceLineItem:	vw_INFORSYTELINE_InvoiceHeader:	—	SF_ERP_Salesforce_Clone_inv_item_all, CommercientFlags
vw_INFORSYTELINE_Estimate	insert + update	vwEstimate:	vw_SFAccount:, vwCustomer:	—	SF_ERP_Salesforce_Clone_co_all, CommercientFlags
vw_INFORSYTELINE_EstimateLine	insert + update	vwEstimateLine:	vwEstimate:	—	SF_ERP_Salesforce_Clone_coitem_all, CommercientFlags
vw_INFORSYTELINE_CustomerAddress	insert + update	vw_INFORSYTELINE_Address:	vw_INFORSYTELINE_SFAccount:	ExternalKey	SF_ERP_Salesforce_Clone_custaddr_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 1 to 9. A run processes active rows in ascending Sync_Order, which is the order the templates put them in:

• 1 — Get Users, SalesPerson
• 2 — account
• 3 — Customer
• 4 — Contact, CustomerOrder
• 5 — CustomerOrderLine
• 6 — InvoiceHeader
• 7 — InvoiceLineItem
• 8 — Estimate
• 9 — EstimateLine, Customer Address

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_INFORSYTELINE_CRM_Account reads vw_INFORSYTELINE_User:, vw_INFORSYTELINE_SalesPerson:, vw_SFAccount:; no template in this set writes vw_SFAccount:
• vw_INFORSYTELINE_Contact reads vw_INFORSYTELINE_SFAccount:
• vw_INFORSYTELINE_Estimate reads vw_SFAccount:, vwCustomer:; no template in this set writes vw_SFAccount:, vwCustomer:
• vw_INFORSYTELINE_EstimateLine reads vwEstimate:
• vw_INFORSYTELINE_Customer reads vw_INFORSYTELINE_SFAccount:, vw_INFORSYTELINE_SalesPerson:
• vw_INFORSYTELINE_CustomerAddress reads vw_INFORSYTELINE_SFAccount:
• vw_INFORSYTELINE_InvoiceHeader reads vw_INFORSYTELINE_SFAccount:, vw_INFORSYTELINE_Customer:, vw_INFORSYTELINE_SalesPerson:
• vw_INFORSYTELINE_InvoiceLineItem reads vw_INFORSYTELINE_InvoiceHeader:
• vw_INFORSYTELINE_CustomerOrder reads vw_INFORSYTELINE_SFAccount:, vw_INFORSYTELINE_Customer:, vw_INFORSYTELINE_SalesPerson:
• vw_INFORSYTELINE_CustomerOrderLine reads vw_INFORSYTELINE_CustomerOrder:

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
SalesPerson	CommercientSF18__slsman_all__c	11	site_ref,slsman → ExternalKey, site_ref → site_ref, slsman → slsman, outside → outside, ref_num → ref_num
account	account	13	site_ref, cust_num → CommercientSF__Commercient_ArCustomerCode__c, city → BillingCity, state → BillingState, country → BillingCountry, city → ShippingCity
Customer	CommercientSF18__customer_all__c	93	site_ref,cust_num → CommercientSF18__ExternalKey__c, name → Name, cust_num → cust_num, site_ref → site_ref, cust_seq → cust_seq
Contact	Contact	13	FirstName → FirstName, LastName → LastName, Email → Email, Phone → Phone, Fax → Fax
CustomerOrder	CommercientSF18__co_all__c	4	site_ref,co_num → ExternalKey, slsman → CommercientSF18__Infor_Syteline_SalesPerson__c, cust_num → Infor_Syteline_Customer, site_ref,cust_num → Account
CustomerOrderLine	CommercientSF18__coitem_all__c	3	site_ref, co_num, co_line, co_release → CommercientSF18__ExternalKey__c, SFDCID → CommercientSF18__Infor_Syteline_Customer_Order__c, site_ref, co_num, co_line, co_release → Name
InvoiceHeader	CommercientSF18__inv_hdr_all__c	31	site_ref,inv_num → CommercientSF18__ExternalKey__c, site_ref,inv_num → Name, site_ref → site_ref, inv_num → inv_num, inv_seq → inv_seq
InvoiceLineItem	CommercientSF18__inv_item_all__c	21	site_ref,inv_num,co_line,co_release → CommercientSF18__ExternalKey__c, site_ref,inv_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
Estimate	Opportunity	6	co_num → ExternalKey__c, co_num → Name, price → Amount, order_date → CloseDate, StageName → StageName
EstimateLine	OpportunityLineItem	7	co_num, co_line, co_release → ExternalKey__c, item → ProductCode, qty_ordered → Quantity, price → UnitPrice, disc → Discount
Customer Address	CommercientSF18__custaddr__c	43	Account → Account, cust_num → CommercientSF18__cust_num__c, cust_seq → CommercientSF18__cust_seq__c, city → CommercientSF18__city__c, state → CommercientSF18__state__c

6. Community templates

The catalogue carries 58 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: 58
• Default operations: insert on 58, update on 58, delete on 58
• Marked circular-sync: 0
• Licence groups they span: 10
• Destination objects: Account, CommercientSF18__co_all__c, CommercientSF18__coitem_all__c, CommercientSF18__customer_all__c, CommercientSF18__inv_hdr_all__c, CommercientSF18__inv_item_all__c, CommercientSF18__slsman_all__c, Contact, Opportunity, OpportunityLineItem, Product2, account, AccountContactRelation, CommercientSF18__custaddr__c, CommercientSF18__item_all__c and 2 custom objects
• Object display names: Customer, CustomerOrder, CustomerOrderLine, Estimate, EstimateLine, InvoiceHeader, InvoiceLineItem, SalesPerson, account, Account, AccountContactRelation, Child Account and 9 more
• Template groups: Account, Product, CRM Opportunity and Line, Invoice, Salesorder, 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_INFORSYTELINE_User
• vw_INFORSYTELINE_SFAccount
• vw_INFORSYTELINE_Contact
• vwEstimate
• vwEstimateLine
• vw_INFORSYTELINE_Customer
• vw_INFORSYTELINE_Address
• vw_INFORSYTELINE_InvoiceHeader
• vw_INFORSYTELINE_InvoiceLineItem
• vw_INFORSYTELINE_CustomerOrder
• vw_INFORSYTELINE_CustomerOrderLine
• vw_INFORSYTELINE_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 V7 and V8 → 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.