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

CRMPro → Salesforce — Infor Visual 9: 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-visual-9.md, and that skill’s ERP table is what points at it. What follows is only what the shipped Infor Visual 9 → 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	—
Infor Visual Receivable	ERP RECEIVABLE data becomes CommercientSF18__InforVisual_RECEIVABLE__c in Salesforce. New records are created, existing ones updated, and records removed in the ERP are deleted.	CommercientSF18__InforVisual_RECEIVABLE__c	SF_ERP_Salesforce_Clone_RECEIVABLE, CommercientFlags
Infor Visual Receivable Line	ERP RECEIVABLE_LINE data becomes CommercientSF18__InforVisual_RECEIVABLE_LINE__c in Salesforce. New records are created, existing ones updated, and records removed in the ERP are deleted.	CommercientSF18__InforVisual_RECEIVABLE_LINE__c	SF_ERP_Salesforce_Clone_RECEIVABLE_LINE
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__InforVisual_CUSTOMER__c, CommercientSF18__InforVisual_SALES_REP__c	SF_ERP_Salesforce_Clone_CUSTOMER, SF_ERP_Salesforce_Clone_CUST_ADDRESS, SF_ERP_Salesforce_Clone_CONTACT, SF_ERP_Salesforce_Clone_SALES_REP
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__InforVisual_ADDRESS__c	SF_ERP_Salesforce_Clone_CUST_ADDRESS
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__InforVisual_CUSTOMER_ORDER__c, CommercientSF18__InforVisual_CUST_ORDER_LINE__c	SF_ERP_Salesforce_Clone_CUSTOMER_ORDER, CommercientFlags, SF_ERP_Salesforce_Clone_CUST_ORDER_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
Get Users	User	CommercientSF6__SalespersonCode__c	0	vw_EPICOR10_User	Select 1 = 0	'' / ''	1
Infor Visual SalesPerson	CommercientSF18__InforVisual_SALES_REP__c	CommercientSF18__ExternalKey__c	2	vw_INFORVISUAL9_SalesPerson:	vw_INFORVISUAL9_SalesPerson	CommercientSF18__ / __c	1
Account	Account	CommercientSF__Commercient_ArCustomerCode__c	3	vw_INFORVISUAL9_Account:	vw_INFORVISUAL9_Account	'' / ''	1
Infor Visual Customer	CommercientSF18__InforVisual_CUSTOMER__c	CommercientSF18__ExternalKey__c	4	vw_INFORVISUAL9_Customer:	vw_INFORVISUAL9_Customer	CommercientSF18__ / __c	1
Customer Reverse Lookup Account	Account	CommercientSF__Commercient_ArCustomerCode__c	5	vw_INFORVISUAL9_CustomerToAccountLookup:	vw_INFORVISUAL9_CustomerToAccountLookup	'' / ''	1
Infor Visual Customer Address	CommercientSF18__InforVisual_ADDRESS__c	CommercientSF18__ExternalKey__c	6	vw_INFORVISUAL9_CustomerAddress:	vw_INFORVISUAL9_CustomerAddress	CommercientSF18__ / __c	1
Infor Visual Order	CommercientSF18__InforVisual_CUSTOMER_ORDER__c	CommercientSF18__ExternalKey__c	9	vw_INFORVISUAL9_Order:	vw_INFORVISUAL9_Order	CommercientSF18__ / __c	1
Infor Visual Order Line	CommercientSF18__InforVisual_CUST_ORDER_LINE__c	CommercientSF18__ExternalKey__c	10	vw_INFORVISUAL9_OrderLine:	vw_INFORVISUAL9_OrderLine	CommercientSF18__ / __c	1
Infor Visual Receivable	CommercientSF18__InforVisual_RECEIVABLE__c	CommercientSF18__ExternalKey__c	11	vw_INFORVISUAL9_Receivable:	vw_INFORVISUAL9_Receivable	CommercientSF18__ / __c	1
Infor Visual Receivable Line	CommercientSF18__InforVisual_RECEIVABLE_LINE__c	CommercientSF18__ExternalKey__c	12	vw_INFORVISUAL9_ReceivableLine:	vw_INFORVISUAL9_ReceivableLine	CommercientSF18__ / __c	1
Contact	Contact	ExternalKey__c	15	vw_INFORVISUAL9_Contact:	vw_INFORVISUAL9_Contact	'' / ''	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, Contact — 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_INFORVISUAL9_SalesPerson	insert + update	—	vw_INFORVISUAL9_SalesPerson:	ExternalKey	SF_ERP_Salesforce_Clone_SALES_REP
vw_INFORVISUAL9_Account	insert + update	—	vw_INFORVISUAL9_SalesPerson:, vw_EPICOR10_User:, vw_INFORVISUAL9_Account:	CommercientSF__Commercient_ArCustomerCode__c	SF_ERP_Salesforce_Clone_CUSTOMER, SF_ERP_Salesforce_Clone_CUST_ADDRESS
vw_INFORVISUAL9_Customer	insert + update	—	vw_INFORVISUAL9_Account:, vw_INFORVISUAL9_Customer:	ExternalKey	SF_ERP_Salesforce_Clone_CUSTOMER
vw_INFORVISUAL9_CustomerToAccountLookup	insert + update	—	vw_INFORVISUAL9_Customer:, vw_INFORVISUAL9_CustomerToAccountLookup:	—	SF_ERP_Salesforce_Clone_CUSTOMER
vw_INFORVISUAL9_CustomerAddress	insert + update	—	vw_INFORVISUAL9_Account:, vw_INFORVISUAL9_Customer:, vw_INFORVISUAL9_CustomerAddress:	ExternalKey	SF_ERP_Salesforce_Clone_CUST_ADDRESS
vw_INFORVISUAL9_Order	insert + update	—	vw_INFORVISUAL9_Account:, vw_INFORVISUAL9_Customer:, vw_INFORVISUAL9_Order:	ExternalKey	SF_ERP_Salesforce_Clone_CUSTOMER_ORDER, CommercientFlags
vw_INFORVISUAL9_OrderLine	insert + update	—	vw_INFORVISUAL9_Order:, vw_INFORVISUAL9_OrderLine:	ExternalKey	SF_ERP_Salesforce_Clone_CUST_ORDER_LINE
vw_INFORVISUAL9_Receivable	insert + update	—	vw_INFORVISUAL9_Account:, vw_INFORVISUAL9_Customer:, vw_INFORVISUAL9_Receivable:	ExternalKey	SF_ERP_Salesforce_Clone_RECEIVABLE, CommercientFlags
vw_INFORVISUAL9_ReceivableLine	insert + update	—	vw_INFORVISUAL9_Receivable:, vw_INFORVISUAL9_OrderLine:, vw_INFORVISUAL9_ReceivableLine:	ExternalKey	SF_ERP_Salesforce_Clone_RECEIVABLE_LINE
vw_INFORVISUAL9_Contact	insert-only	—	vw_INFORVISUAL9_Account:, vw_INFORVISUAL9_Contact:	ExternalKey__c	SF_ERP_Salesforce_Clone_CONTACT

4. Order of work

The templates set Sync_Order from 0 to 15. A run processes active rows in ascending Sync_Order, which is the order the templates put them in:

• 0 — Get Users
• 2 — Infor Visual SalesPerson
• 3 — Account
• 4 — Infor Visual Customer
• 5 — Customer Reverse Lookup Account
• 6 — Infor Visual Customer Address
• 9 — Infor Visual Order
• 10 — Infor Visual Order Line
• 11 — Infor Visual Receivable
• 12 — Infor Visual Receivable Line
• 15 — Contact

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_INFORVISUAL9_Receivable reads vw_INFORVISUAL9_Account:, vw_INFORVISUAL9_Customer:, vw_INFORVISUAL9_Receivable:; no template in this set writes vw_INFORVISUAL9_Account:, vw_INFORVISUAL9_Customer:, vw_INFORVISUAL9_Receivable:
• vw_INFORVISUAL9_ReceivableLine reads vw_INFORVISUAL9_Receivable:, vw_INFORVISUAL9_OrderLine:, vw_INFORVISUAL9_ReceivableLine:; no template in this set writes vw_INFORVISUAL9_Receivable:, vw_INFORVISUAL9_OrderLine:, vw_INFORVISUAL9_ReceivableLine:
• vw_INFORVISUAL9_Account reads vw_INFORVISUAL9_SalesPerson:, vw_EPICOR10_User:, vw_INFORVISUAL9_Account:; no template in this set writes vw_INFORVISUAL9_SalesPerson:, vw_INFORVISUAL9_Account:
• vw_INFORVISUAL9_CustomerToAccountLookup reads vw_INFORVISUAL9_Customer:, vw_INFORVISUAL9_CustomerToAccountLookup:; no template in this set writes vw_INFORVISUAL9_Customer:, vw_INFORVISUAL9_CustomerToAccountLookup:
• vw_INFORVISUAL9_Contact reads vw_INFORVISUAL9_Account:, vw_INFORVISUAL9_Contact:; no template in this set writes vw_INFORVISUAL9_Account:, vw_INFORVISUAL9_Contact:
• vw_INFORVISUAL9_Customer reads vw_INFORVISUAL9_Account:, vw_INFORVISUAL9_Customer:; no template in this set writes vw_INFORVISUAL9_Account:, vw_INFORVISUAL9_Customer:
• vw_INFORVISUAL9_CustomerAddress reads vw_INFORVISUAL9_Account:, vw_INFORVISUAL9_Customer:, vw_INFORVISUAL9_CustomerAddress:; no template in this set writes vw_INFORVISUAL9_Account:, vw_INFORVISUAL9_Customer:, vw_INFORVISUAL9_CustomerAddress:
• vw_INFORVISUAL9_Order reads vw_INFORVISUAL9_Account:, vw_INFORVISUAL9_Customer:, vw_INFORVISUAL9_Order:; no template in this set writes vw_INFORVISUAL9_Account:, vw_INFORVISUAL9_Customer:, vw_INFORVISUAL9_Order:
• vw_INFORVISUAL9_OrderLine reads vw_INFORVISUAL9_Order:, vw_INFORVISUAL9_OrderLine:; no template in this set writes vw_INFORVISUAL9_Order:, vw_INFORVISUAL9_OrderLine:
• vw_INFORVISUAL9_SalesPerson reads vw_INFORVISUAL9_SalesPerson:; no template in this set writes vw_INFORVISUAL9_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
Infor Visual SalesPerson	CommercientSF18__InforVisual_SALES_REP__c	7	Def_Commission_Percentage → def_commission_percentage__c, Earning_Code_Id → Earning_Code_Id, Employee_Id → CommercientSF18__Employee_Id__c, Name1 → name1__c, Pay_Method → CommercientSF18__Pay_Method__c
Account	Account	10	CommercientSFommercient_ArCustomerCode → CommercientSF__Commercient_ArCustomerCode__c, Phone → Phone, BillingStreet → BillingStreet, BillingCity → BillingCity, BillingState → BillingState
Infor Visual Customer	CommercientSF18__InforVisual_CUSTOMER__c	133	Account → Account, Accept_830 → Accept_830, Accept_862 → Accept_862, Accept_Early → Accept_Early, Active_Flag → CommercientSF18__Active_Flag__c
Customer Reverse Lookup Account	Account	2	CommercientSFommercient_ArCustomerCode → CommercientSF__Commercient_ArCustomerCode__c, InforVisual_Customer → InforVisual_Customer__c
Infor Visual Customer Address	CommercientSF18__InforVisual_ADDRESS__c	81	Account → Account, Customer → CommercientSF18__Customer__c, Active_Flag → active_flag__c, Accept_830 → Accept_830, Accept_862 → Accept_862
Infor Visual Order	CommercientSF18__InforVisual_CUSTOMER_ORDER__c	114	Account → Account, Customer → CommercientSF18__Customer__c, CommercientSF18_Grand_Total → CommercientSF18_Grand_Total__c, CommercientSF18_Line_Description__fulllength → CommercientSF18_Line_Description__fulllength__c, Accept_Early → Accept_Early
Infor Visual Order Line	CommercientSF18__InforVisual_CUST_ORDER_LINE__c	95	InforVisual_Order → CommercientSF18__InforVisual_Order__c, Accept_Early → Accept_Early, Acknowledge_Id → acknowledge_id__c, Allocated_Qty → Allocated_Qty, Back_Order_Flag → back_order_flag__c
Infor Visual Receivable	CommercientSF18__InforVisual_RECEIVABLE__c	48	Account → Account, Customer → CommercientSF18__Customer__c, Buy_Rate → CommercientSF18__Buy_Rate__c, Comm_Paid_Amount → CommercientSF18__Comm_Paid_Amount__c, Create_Date → CommercientSF18__Create_Date__c
Infor Visual Receivable Line	CommercientSF18__InforVisual_RECEIVABLE_LINE__c	29	Receivable → Receivable, Order_Line → order_line__c, Amount → CommercientSF18__Amount__c, Commission_Pct → Commission_Pct, Cust_Order_Id → CommercientSF18__Cust_Order_Id__c
Contact	Contact	12	LastName → LastName, FirstName → FirstName, Email → Email, Phone → Phone, Mobile → mobile__c

6. Community templates

The catalogue carries 112 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: 112
• Default operations: insert on 112, update on 112, delete on 112
• Marked circular-sync: 0
• Licence groups they span: 13
• Destination objects: Account, Product2, PriceBookEntry, CommercientSF18__InforVisual_CUST_ORDER_LINE__c, CommercientSF18__InforVisual_ADDRESS__c, CommercientSF18__InforVisual_CUSTOMER__c, CommercientSF18__InforVisual_CUSTOMER_ORDER__c, CommercientSF18__InforVisual_RECEIVABLE__c, CommercientSF18__InforVisual_RECEIVABLE_LINE__c, CommercientSF18__InforVisual_PART__c, CommercientSF18__InforVisual_SALES_REP__c, CommercientSF18__InforVisual_TERMS__c, Contact, CommercientSF18__InforVisual_PART_WAREHOUSE__c, Opportunity, User, CommercientSF18__InforVisual_QUOTE__c, CommercientSF18__InforVisual_QUOTE_LINE__c, CommercientSF18_InforVisual_CashReceipt__c, OpportunityLineItem, 4 more and 2 custom objects
• Object display names: Account, Customer Reverse Lookup Account, Infor Visual Customer, Infor Visual Receivable, Infor Visual Receivable Line, Infor Visual SalesPerson, Infor Visual Terms, Contact, Infor Visual Customer Address, Infor Visual Order Line, SYNC ITEM, SYNC ITEM TO PRODUCT LOOKUP, 32 more and a further template
• Template groups: Account, Product, Salesorder, Customer Multi Ship Addresses, CRM Opportunity and Line, Opportunity, CRM Quote 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_EPICOR10_User
• vw_INFORVISUAL9_Receivable:
• vw_INFORVISUAL9_ReceivableLine:
• vw_INFORVISUAL9_Account:
• vw_INFORVISUAL9_CustomerToAccountLookup:
• vw_INFORVISUAL9_Contact:
• vw_INFORVISUAL9_Customer:
• vw_INFORVISUAL9_CustomerAddress:
• vw_INFORVISUAL9_Order:
• vw_INFORVISUAL9_OrderLine:
• vw_INFORVISUAL9_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 Visual 9 → 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.