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

CRMPro → Salesforce — Infor CloudSuite: 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-cloudsuite.md, and that skill’s ERP table is what points at it. What follows is only what the shipped Infor CloudSuite → 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.	Accounts, CommercientSF18__customer_all__c, CommercientSF18__slsman_all__c	SF_ERP_Salesforce_Clone_csi_customer_mst, SF_ERP_Salesforce_Clone_csi_custaddr_mst, SF_ERP_Salesforce_Clone_csi_slsman_mst
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_csi_custaddr_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, existing ones updated, and records removed in the ERP are deleted.	CommercientSF18__co_all__c, CommercientSF18__coitem_all__c	SF_ERP_Salesforce_Clone_csi_co_mst, SF_ERP_Salesforce_Clone_csi_coitem_mst

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_INFORCLOUDSUITE_User	Select 1 = 0	'' / ''	1
InforCloud Salesperson	CommercientSF18__slsman_all__c	CommercientSF18__ExternalKey__c	1	vw_INFORCLOUDSUITE_SalesPerson:	vw_INFORCLOUDSUITE_SalesPerson	CommercientSF18__ / __c	1
Account	Accounts	CommercientSF__Commercient_ArCustomerCode__c	2	vw_INFORCLOUDSUITE_Account:	vw_INFORCLOUDSUITE_Account	'' / ''	1
InforCloud Customer	CommercientSF18__customer_all__c	CommercientSF18__ExternalKey__c	3	vw_INFORCLOUDSUITE_Customer:	vw_INFORCLOUDSUITE_Customer	CommercientSF18__ / __c	1
InforCloud CustomerToAccountLookup	Accounts	CommercientSF__Commercient_ArCustomerCode__c	4	vw_INFORCLOUDSUITE_CustomerToAccountLookup:	vw_INFORCLOUDSUITE_CustomerToAccountLookup	'' / ''	1
InforCloud Address	CommercientSF18__custaddr__c	CommercientSF18__ExternalKey__c	5	vw_INFORCLOUDSUITE_Address:	vw_INFORCLOUDSUITE_Address	CommercientSF18__ / __c	1
InforCloud Salesorder	CommercientSF18__co_all__c	CommercientSF18__ExternalKey__c	6	vw_INFORCLOUDSUITE_Order:	vw_INFORCLOUDSUITE_Order	CommercientSF18__ / __c	1
InforCloud Salesorderline	CommercientSF18__coitem_all__c	CommercientSF18__ExternalKey__c	7	vw_INFORCLOUDSUITE_OrderLine:	vw_INFORCLOUDSUITE_OrderLine	CommercientSF18__ / __c	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 Users, 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_INFORCLOUDSUITE_SalesPerson	insert + update	—	vw_INFORCLOUDSUITE_SalesPerson:	Commercient_ExternalKey__c	SF_ERP_Salesforce_Clone_csi_slsman_mst
vw_INFORCLOUDSUITE_Account	insert + update	—	vw_INFORCLOUDSUITE_User:, vw_INFORCLOUDSUITE_SalesPerson:, vw_INFORCLOUDSUITE_Account:	—	SF_ERP_Salesforce_Clone_csi_customer_mst, SF_ERP_Salesforce_Clone_csi_custaddr_mst
vw_INFORCLOUDSUITE_Customer	insert + update	—	vw_INFORCLOUDSUITE_Account:, vw_INFORCLOUDSUITE_Terms:, vw_INFORCLOUDSUITE_SalesPerson:, vw_INFORCLOUDSUITE_Customer:	ExternalKey	SF_ERP_Salesforce_Clone_csi_customer_mst, SF_ERP_Salesforce_Clone_csi_custaddr_mst
vw_INFORCLOUDSUITE_CustomerToAccountLookup	insert + update	—	vw_INFORCLOUDSUITE_Customer:, vw_INFORCLOUDSUITE_CustomerToAccountLookup:	—	SF_ERP_Salesforce_Clone_csi_customer_mst
vw_INFORCLOUDSUITE_Address	insert + update	—	vw_INFORCLOUDSUITE_Account:, vw_INFORCLOUDSUITE_Customer:, vw_INFORCLOUDSUITE_Address:	Commercient_ExternalKey__c	SF_ERP_Salesforce_Clone_csi_custaddr_mst
vw_INFORCLOUDSUITE_Order	insert-only	—	vw_INFORCLOUDSUITE_Account:, vw_INFORCLOUDSUITE_Customer:, vw_INFORCLOUDSUITE_Order:	ExternalKey	SF_ERP_Salesforce_Clone_csi_co_mst
vw_INFORCLOUDSUITE_OrderLine	insert-only	—	vw_INFORCLOUDSUITE_Order:, vw_INFORCLOUDSUITE_Product:, vw_INFORCLOUDSUITE_Item:, vw_INFORCLOUDSUITE_OrderLine:	ExternalKey	SF_ERP_Salesforce_Clone_csi_coitem_mst

4. Order of work

The templates set Sync_Order to 1, 2, 3, 4, 5, 6, 7. A run processes active rows in ascending Sync_Order, which is the order the templates put them in:

• 1 — Get Users, InforCloud Salesperson
• 2 — Account
• 3 — InforCloud Customer
• 4 — InforCloud CustomerToAccountLookup
• 5 — InforCloud Address
• 6 — InforCloud Salesorder
• 7 — InforCloud Salesorderline

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_INFORCLOUDSUITE_CustomerToAccountLookup reads vw_INFORCLOUDSUITE_Customer:, vw_INFORCLOUDSUITE_CustomerToAccountLookup:; no template in this set writes vw_INFORCLOUDSUITE_Customer:, vw_INFORCLOUDSUITE_CustomerToAccountLookup:
• vw_INFORCLOUDSUITE_Account reads vw_INFORCLOUDSUITE_User:, vw_INFORCLOUDSUITE_SalesPerson:, vw_INFORCLOUDSUITE_Account:; no template in this set writes vw_INFORCLOUDSUITE_SalesPerson:, vw_INFORCLOUDSUITE_Account:
• vw_INFORCLOUDSUITE_Customer reads vw_INFORCLOUDSUITE_Account:, vw_INFORCLOUDSUITE_Terms:, vw_INFORCLOUDSUITE_SalesPerson:, vw_INFORCLOUDSUITE_Customer:; no template in this set writes vw_INFORCLOUDSUITE_Account:, vw_INFORCLOUDSUITE_Terms:, vw_INFORCLOUDSUITE_SalesPerson:, vw_INFORCLOUDSUITE_Customer:
• vw_INFORCLOUDSUITE_Address reads vw_INFORCLOUDSUITE_Account:, vw_INFORCLOUDSUITE_Customer:, vw_INFORCLOUDSUITE_Address:; no template in this set writes vw_INFORCLOUDSUITE_Account:, vw_INFORCLOUDSUITE_Customer:, vw_INFORCLOUDSUITE_Address:
• vw_INFORCLOUDSUITE_Order reads vw_INFORCLOUDSUITE_Account:, vw_INFORCLOUDSUITE_Customer:, vw_INFORCLOUDSUITE_Order:; no template in this set writes vw_INFORCLOUDSUITE_Account:, vw_INFORCLOUDSUITE_Customer:, vw_INFORCLOUDSUITE_Order:
• vw_INFORCLOUDSUITE_OrderLine reads vw_INFORCLOUDSUITE_Order:, vw_INFORCLOUDSUITE_Product:, vw_INFORCLOUDSUITE_Item:, vw_INFORCLOUDSUITE_OrderLine:; no template in this set writes vw_INFORCLOUDSUITE_Order:, vw_INFORCLOUDSUITE_Product:, vw_INFORCLOUDSUITE_Item:, vw_INFORCLOUDSUITE_OrderLine:
• vw_INFORCLOUDSUITE_SalesPerson reads vw_INFORCLOUDSUITE_SalesPerson:; no template in this set writes vw_INFORCLOUDSUITE_SalesPerson:

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
InforCloud Salesperson	CommercientSF18__slsman_all__c	24	Commercient_ExternalKey → Commercient_ExternalKey__c, DL_Delete_Indicator → DL_Delete_Indicator, In_Workflow → CommercientSF18__In_Workflow__c, Note_Exists_Flag → CommercientSF18__Note_Exists_Flag__c, Record_Date → Record_Date
Account	Accounts	15	CommercientSFommercient_ArCustomerCode → CommercientSF__Commercient_ArCustomerCode__c, Customer_Number → Customer_Number, commercientinforcloudsuite__InforCloud_Salesperson → commercientinforcloudsuite__InforCloud_Salesperson, commercientinforcloudsuite__InforCloud_Term → commercientinforcloudsuite__InforCloud_Term, Account_Name → Account_Name
InforCloud Customer	CommercientSF18__customer_all__c	91	Account → Account, Infor_Syteline_SalesPerson → CommercientSF18__Infor_Syteline_SalesPerson__c, active_for_data_integration → CommercientSF18__active_for_data_integration__c, aps_pull_up → CommercientSF18__aps_pull_up__c, avg_bal_os → CommercientSF18__avg_bal_os__c
InforCloud CustomerToAccountLookup	Accounts	2	Commercient_ArCustomer_Code → Commercient_ArCustomer_Code, commercientinforcloudsuite__InforCloud_Customer → commercientinforcloudsuite__InforCloud_Customer
InforCloud Address	CommercientSF18__custaddr__c	46	Commercient_ExternalKey → Commercient_ExternalKey__c, Account → Account, InforCloud_Customer → InforCloud_Customer, Dl_Delete_Indicator → Dl_Delete_Indicator, In_Workflow → CommercientSF18__In_Workflow__c
InforCloud Salesorder	CommercientSF18__co_all__c	50	Account → Account, Infor_Syteline_Customer → Infor_Syteline_Customer, co_num → CommercientSF18__co_num__c, cost → CommercientSF18__cost__c, CreateDate → CommercientSF18__CreateDate__c
InforCloud Salesorderline	CommercientSF18__coitem_all__c	73	Infor_Syteline_Customer_Order → Infor_Syteline_Customer_Order, Infor_Syteline_Item → CommercientSF18__Infor_Syteline_Item__c, co_cust_num → co_cust_num, co_line → CommercientSF18__co_line__c, co_num → CommercientSF18__co_num__c

6. Community templates

The catalogue carries 12 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: 12
• Default operations: insert on 12, update on 12, delete on 12
• Marked circular-sync: 0
• Licence groups they span: 6
• Destination objects: Accounts, CommercientSF18__co_all__c, CommercientSF18__coitem_all__c, CommercientSF18__custaddr__c, CommercientSF18__customer_all__c, CommercientSF18__slsman_all__c
• Object display names: InforCloud Address, InforCloud Customer, InforCloud Salesorder, InforCloud Salesorderline, InforCloud Salesperson, Account, InforCloud CustomerToAccountLookup
• Template groups: Account, 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_INFORCLOUDSUITE_User
• vw_INFORCLOUDSUITE_CustomerToAccountLookup:
• vw_INFORCLOUDSUITE_Account:
• vw_INFORCLOUDSUITE_Customer:
• vw_INFORCLOUDSUITE_Address:
• vw_INFORCLOUDSUITE_Order:
• vw_INFORCLOUDSUITE_OrderLine:
• vw_INFORCLOUDSUITE_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 CloudSuite → 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.