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

CRMPro → Salesforce — Infor A+: 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-a.md, and that skill’s ERP table is what points at it. What follows is only what the shipped Infor A+ → 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
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, CommercientSF18__CUSMS__c, CommercientSF18__REPMS__c	SF_ERP_Salesforce_Clone_CUSMS, SF_ERP_Salesforce_Clone_ADDR, SF_ERP_Salesforce_Clone_REPMS
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__ADDR__c	SF_ERP_Salesforce_Clone_ADDR
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__ORHED__c, CommercientSF18__ORDET__c, CommercientSF18__HSHED__c, CommercientSF18__HSDET__c	SF_ERP_Salesforce_Clone_ORHED, SF_ERP_Salesforce_Clone_ORDET, SF_ERP_Salesforce_Clone_HSHED, SF_ERP_Salesforce_Clone_HSDET

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
Salesperson	CommercientSF18__REPMS__c	CommercientSF18__ExternalKey__c	1	vw_INFORA_Salesperson	vw_INFORA_Salesperson	CommercientSF18__ / __c	1
Account	Account	CommercientSF__Commercient_ArCustomerCode__c	2	vw_INFORA_Account	vw_INFORA_Account	'' / ''	1
Customer	CommercientSF18__CUSMS__c	CommercientSF18__ExternalKey__c	3	vw_INFORA_Customer	vw_INFORA_Customer	CommercientSF18__ / __c	1
Account To Customer Reverse Lookup	Account	CommercientSF__Commercient_ArCustomerCode__c	4	vw_INFORA_CustomerToAccountLookup	vw_INFORA_CustomerToAccountLookup	'' / ''	1
Ship To Address	CommercientSF18__ADDR__c	CommercientSF18__ExternalKey__c	5	vw_INFORA_ShipToAddress	vw_INFORA_ShipToAddress	CommercientSF18__ / __c	1
Open Order Header	CommercientSF18__ORHED__c	CommercientSF18__ExternalKey__c	9	vw_INFORA_OpenOrderHeader	vw_INFORA_OpenOrderHeader	CommercientSF18__ / __c	1
Open Order Detail	CommercientSF18__ORDET__c	CommercientSF18__ExternalKey__c	10	vw_INFORA_OpenOrderDetail	vw_INFORA_OpenOrderDetail	CommercientSF18__ / __c	1
Order History Header	CommercientSF18__HSHED__c	CommercientSF18__ExternalKey__c	11	vw_INFORA_OrderHistoryHeader	vw_INFORA_OrderHistoryHeader	CommercientSF18__ / __c	1
Order History Detail	CommercientSF18__HSDET__c	CommercientSF18__ExternalKey__c	12	vw_INFORA_OrderHistoryDetail	vw_INFORA_OrderHistoryDetail	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.

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_INFORA_Salesperson	insert + update	vw_INFORA_Salesperson:	—	—	SF_ERP_Salesforce_Clone_REPMS
vw_INFORA_Account	insert + update	vw_INFORA_Account:	vw_INFORA_Salesperson:	—	SF_ERP_Salesforce_Clone_CUSMS, SF_ERP_Salesforce_Clone_ADDR
vw_INFORA_Customer	insert + update	vw_INFORA_Customer:	vw_INFORA_Account:, vw_INFORA_Salesperson:	ExternalKey	SF_ERP_Salesforce_Clone_CUSMS
vw_INFORA_CustomerToAccountLookup	insert + update	vw_INFORA_CustomerToAccountLookup:	vw_INFORA_Customer:, vw_INFORA_Account:	—	SF_ERP_Salesforce_Clone_CUSMS
vw_INFORA_ShipToAddress	insert + update	vw_INFORA_ShipToAddress:	vw_INFORA_Account:, vw_INFORA_Customer:	ExternalKey	SF_ERP_Salesforce_Clone_ADDR
vw_INFORA_OpenOrderHeader	insert + update	vw_INFORA_OpenOrderHeader:	vw_INFORA_Account:, vw_INFORA_Salesperson:, vw_INFORA_Customer:	ExternalKey	SF_ERP_Salesforce_Clone_ORHED
vw_INFORA_OpenOrderDetail	insert + update	vw_INFORA_OpenOrderDetail:	vw_INFORA_Product:, vw_INFORA_ItemMaster:, vw_INFORA_OpenOrderHeader:	ExternalKey	SF_ERP_Salesforce_Clone_ORDET
vw_INFORA_OrderHistoryHeader	insert + update	vw_INFORA_OrderHistoryHeader:	vw_INFORA_Account:, vw_INFORA_Salesperson:, vw_INFORA_Customer:	ExternalKey	SF_ERP_Salesforce_Clone_HSHED
vw_INFORA_OrderHistoryDetail	insert + update	vw_INFORA_OrderHistoryDetail:	vw_INFORA_Product:, vw_INFORA_ItemMaster:, vw_INFORA_OrderHistoryHeader:	ExternalKey	SF_ERP_Salesforce_Clone_HSDET

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

• 1 — Salesperson
• 2 — Account
• 3 — Customer
• 4 — Account To Customer Reverse Lookup
• 5 — Ship To Address
• 9 — Open Order Header
• 10 — Open Order Detail
• 11 — Order History Header
• 12 — Order History Detail

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_INFORA_Account reads vw_INFORA_Salesperson:
• vw_INFORA_CustomerToAccountLookup reads vw_INFORA_Customer:, vw_INFORA_Account:
• vw_INFORA_Customer reads vw_INFORA_Account:, vw_INFORA_Salesperson:
• vw_INFORA_ShipToAddress reads vw_INFORA_Account:, vw_INFORA_Customer:
• vw_INFORA_OpenOrderHeader reads vw_INFORA_Account:, vw_INFORA_Salesperson:, vw_INFORA_Customer:
• vw_INFORA_OpenOrderDetail reads vw_INFORA_Product:, vw_INFORA_ItemMaster:, vw_INFORA_OpenOrderHeader:; no template in this set writes vw_INFORA_Product:, vw_INFORA_ItemMaster:
• vw_INFORA_OrderHistoryHeader reads vw_INFORA_Account:, vw_INFORA_Salesperson:, vw_INFORA_Customer:
• vw_INFORA_OrderHistoryDetail reads vw_INFORA_Product:, vw_INFORA_ItemMaster:, vw_INFORA_OrderHistoryHeader:; no template in this set writes vw_INFORA_Product:, vw_INFORA_ItemMaster:

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__REPMS__c	29	SMCONO → CommercientSF18__smcono__c, SMRP1 → CommercientSF18__smrp1__c, SMRPNM → CommercientSF18__smrpnm__c, SMSLMD → CommercientSF18__smslmd__c, SMSLYD → CommercientSF18__smslyd__c
Account	Account	14	CommercientSFommercient_ArCustomerCode → CommercientSF__Commercient_ArCustomerCode__c, Phone → Phone, Type → Type, BillingStreet → BillingStreet, BillingCity → BillingCity
Customer	CommercientSF18__CUSMS__c	212	Account → Account, INFORA_SalesRep_Master → CommercientSF18__INFORA_SalesRep_Master__c, CMCONO → CMCONO, CMCSNO → CMCSNO, CMCSNM → CMCSNM
Account To Customer Reverse Lookup	Account	2	CommercientSFommercient_ArCustomerCode → CommercientSF__Commercient_ArCustomerCode__c, CommercientSF18__INFORA_Customer_Master → CommercientSF18__INFORA_Customer_Master__c
Ship To Address	CommercientSF18__ADDR__c	86	Account → Account, INFORA_Customer_Master → INFORA_Customer_Master, SACONO → SACONO, SACSNO → SACSNO, SASHP → CommercientSF18__SASHP__c
Open Order Header	CommercientSF18__ORHED__c	300	Account → Account, INFORA_SalesRep_Master → CommercientSF18__INFORA_SalesRep_Master__c, INFORA_Customer_Master → INFORA_Customer_Master, OHCSNO → OHCSNO, OHCONO → OHCONO
Open Order Detail	CommercientSF18__ORDET__c	174	Product → Product, INFORA_Item_Master → CommercientSF18__INFORA_Item_Master__c, INFORA_Open_Order_Header → CommercientSF18__INFORA_Open_Order_Header__c, ODCSNO → ODCSNO, ODCONO → ODCONO
Order History Header	CommercientSF18__HSHED__c	252	Account → Account, INFORA_SalesRep_Master → CommercientSF18__INFORA_SalesRep_Master__c, INFORA_Customer_Master → INFORA_Customer_Master, OAHSSQ → CommercientSF18__OAHSSQ__c, OACSNO → OACSNO
Order History Detail	CommercientSF18__HSDET__c	151	Product → CommercientSF18__product__c, INFORA_Item_Master → CommercientSF18__infora_item_master__c, INFORA_Order_History_Header → CommercientSF18__infora_order_history_header__c, OBCONO → CommercientSF18__obcono__c, OBCSNO → CommercientSF18__obcsno__c

6. Community templates

The catalogue carries 47 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: 47
• Default operations: insert on 47, update on 47, delete on 47
• Marked circular-sync: 0
• Licence groups they span: 9
• Destination objects: Account, Product2, Pricebookentry, CommercientSF18__ADDR__c, CommercientSF18__CUSMS__c, CommercientSF18__HSDET__c, CommercientSF18__HSHED__c, CommercientSF18__ORDET__c, CommercientSF18__ORHED__c, CommercientSF18__REPMS__c, Opportunity, OpportunityLineItem, Pricebook2, User and 3 custom objects
• Object display names: Account, Account To Customer Reverse Lookup, Customer, Item Master, Open Order Detail, Order History Detail, Order History Header, Product, Product To Item Reverse Lookup, Salesperson, Ship To Address, Open Order Header, 8 more and 3 further templates
• Template groups: Product, Account, Salesorder, CRM Opportunity and Line, 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_INFORA_Account
• vw_INFORA_CustomerToAccountLookup
• vw_INFORA_Customer
• vw_INFORA_ShipToAddress
• vw_INFORA_OpenOrderHeader
• vw_INFORA_OpenOrderDetail
• vw_INFORA_OrderHistoryHeader
• vw_INFORA_OrderHistoryDetail
• vw_INFORA_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 A+ → 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.