Source ERP · 45 of 105
CRMPro → Salesforce — Infor Visual 7.1.2: what the shipped templates set up
This is the capability summary the dlake CLI repository publishes; whitelisted customers fetch the operational skill with "dlake admin get_skill dlake-crmpro-salesforce/erps/infor-visual-7-1-2". It extends the dlake-crmpro-salesforce skill, which holds what is true whatever the source ERP. Both directions for this pair are summarised at /integrations/infor-visual-7-1-2-salesforce/.
CRMPro → Salesforce — Infor Visual 7.1.2: what the shipped templates set up
This is a capability summary, not an operating guide. To receive the operational skill you must be a
registered, whitelisted Commercient customer. Whitelisted customers fetch it with
dlake admin get_skill dlake-crmpro-salesforce/erps/infor-visual-7-1-2 (or list_skills) against
the Commercient admin plane. Existing customers who need access or help: contact
support@commercient.com. New customers: contact sales@commercient.com to become a customer and be
whitelisted.
dlake-crmpro is the parent skill and the authority for everything general: the CRMPro tools, process configuration and field list, the sync history, how source data is selected, and what a run that finds nothing does. 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 grows as the catalogue does.
1. What the templates deliver
| Group | Business outcome | Objects | Source tables and views |
|---|---|---|---|
| Infor Visual Receivable | ERP receivable data becomes Commercient Infor Visual Receivable Managed Custom Object in Salesforce | Commercient Infor Visual Receivable Managed Custom Object | receivables |
| Infor Visual Receivable Line | ERP receivable line data becomes Commercient Infor Visual Receivable Line Managed Custom Object in Salesforce | Commercient Infor Visual Receivable Line Managed Custom Object | receivable lines |
| Get Users(Owner) | The templates push User to Salesforce | 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) | Account, Contact, Commercient Infor Visual Customer Managed Custom Object, Commercient Infor Visual Sales Rep Managed Custom Object | customers, customer contacts, sales reps |
| 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 | Commercient Infor Visual Address Managed Custom Object | customer addresses |
| Sales order | Commercient will sync the Sales Orders from the ERP Sales Order Entry module to the Commercient Sales Order Header (MCO) objects in CRM | Commercient Infor Visual Customer Order Managed Custom Object, Commercient Infor Visual Customer Order Line Managed Custom Object | customer orders, customer order lines |
2. The process rows the templates create
Each template’s setup writes one process configuration row. These are the values it sets; a column the inserts never set is not listed.
| Display name | Destination object | Matching key | Run sequence |
|---|---|---|---|
| Get Users(Owner) | User | Commercient salesperson code | 1 |
| Infor Visual Salesperson | Commercient Infor Visual Sales Rep Managed Custom Object | Commercient external key (Infor package) | 2 |
| Account | Account | Commercient AR customer code | 3 |
| Infor Visual Customer | Commercient Infor Visual Customer Managed Custom Object | Commercient external key (Infor package) | 4 |
| Customer Reverse Lookup Account | Account | Commercient AR customer code | 5 |
| Infor Visual Customer Address | Commercient Infor Visual Address Managed Custom Object | Commercient external key (Infor package) | 6 |
| Infor Visual Order | Commercient Infor Visual Customer Order Managed Custom Object | Commercient external key (Infor package) | 9 |
| Infor Visual Order Line | Commercient Infor Visual Customer Order Line Managed Custom Object | Commercient external key (Infor package) | 10 |
| Infor Visual Receivable | Commercient Infor Visual Receivable Managed Custom Object | Commercient external key (Infor package) | 11 |
| Infor Visual Receivable Line | Commercient Infor Visual Receivable Line Managed Custom Object | Commercient external key (Infor package) | 12 |
| Contact | Contact | External key (custom field) | 16 |
Every one of these inserts the active setting as 0, so an imported process is inactive until an operator activates it.
3. The views
“Change detection” names which of the three kinds dlake-crmpro defines the view’s own filter makes it; where a view’s shape is not one of those three the column is left empty and the view’s own filter is the authority.
| View | Change detection | Source tables |
|---|---|---|
| salesperson feed | insert + update | sales reps |
| account feed | insert + update | customers |
| customer feed | insert + update | customers |
| customer account lookup feed | insert + update | customers |
| customer address feed | insert + update | customer addresses |
| order feed | insert + update | customer orders |
| order line feed | insert + update | customer order lines |
| receivable feed | insert + update | receivables |
| receivable line feed | insert + update | receivable lines |
| contact feed | insert + update | customer contacts, customers |
4. Order of work
The templates set run sequence from 1 to 16. A run processes active rows in ascending run sequence, which is the order the templates put them in:
- 1 — Get Users(Owner)
- 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
- 16 — Contact
These views read another process’s sync output, which is what makes the order a dependency order: the row appears in the view only once the process that writes that sync output has run, so a parent flows on one run and its children on the next.
- receivable feed reads account sync output, customer sync output
- receivable line feed reads receivable sync output, order line sync output
- account feed reads user sync output
- customer account lookup feed reads customer sync output
- contact feed reads account sync output, customer sync output, user sync output
- customer feed reads account sync output, salesperson sync output, terms sync output; no template in this set writes terms sync output
- customer address feed reads account sync output, customer sync output
- order feed reads account sync output, customer sync output
- order line feed reads order sync output, product sync output, part sync output; no template in this set writes product sync output, part sync output
5. Field mapping
Each template carries its intended mapping in field mapping.
| Template | Object | Mapped fields | First ERP → Salesforce pairs |
|---|---|---|---|
| Infor Visual Salesperson | Commercient Infor Visual Sales Rep Managed Custom Object | 7 | Default commission percentage → Default commission percentage (custom field), Earning code identifier → Earning code identifier, Employee identifier → Commercient employee identifier, Name 1 → Name 1 (custom field), Pay method → Commercient pay method |
| Account | Account | 2 | Commercient AR customer code column → Commercient AR customer code, owner lookup → owner lookup |
| Infor Visual Customer | Commercient Infor Visual Customer Managed Custom Object | 122 | Account → Account, Sales rep → Commercient sales rep (related record), linked Infor Visual terms → Commercient Infor Visual terms (related record), Accept 830 → Accept 830, Accept 862 → Accept 862 |
| Customer Reverse Lookup Account | Account | 2 | Commercient AR customer code column → Commercient AR customer code, linked Infor Visual customer (reverse lookup) → Commercient Infor Visual Customer Managed Custom Object |
| Infor Visual Customer Address | Commercient Infor Visual Address Managed Custom Object | 78 | Account → Account, Customer → Commercient customer (related record), Accept 830 → Accept 830, Accept 862 → Accept 862, Address line 1 → Commercient address line 1 |
| Infor Visual Order | Commercient Infor Visual Customer Order Managed Custom Object | 106 | Account → Account, Customer → Commercient customer (related record), Accept early → Accept early, Create date → Commercient create date, Desired ship date → Commercient desired ship date |
| Infor Visual Order Line | Commercient Infor Visual Customer Order Line Managed Custom Object | 91 | linked Infor Visual order → Commercient Infor Visual order (related record), Part → Commercient part (related record), Product → Product (custom field), Accept early → Accept early, Acknowledgement identifier → Commercient acknowledgement identifier |
| Infor Visual Receivable | Commercient Infor Visual Receivable Managed Custom Object | 44 | Account → Account, Customer → Commercient customer (related record), Buy rate → Commercient buy rate, Commission paid amount → Commercient commission paid amount, Create date → Commercient create date |
| Infor Visual Receivable Line | Commercient Infor Visual Receivable Line Managed Custom Object | 24 | Receivable → Receivable, Amount → Commercient amount, Commission percent → Commission percent, Customer order identifier → Commercient customer order identifier, Customer order line number → Commercient customer order line number |
| Contact | Contact | 10 | account lookup → account lookup, linked Infor Visual customer → Infor Visual customer (custom field), owner lookup → owner lookup, Family name → Family name, Given name → Given name |
6. Community templates
The catalogue carries 20 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: 20
- Default operations: insert on 20, update on 20, delete on 20
- Marked as circular sync: 0
- Licence groups they span: 12
- Destination objects: Account, Product, Commercient Infor Visual Quote Price (Zoho package object), Commercient Contact Matching Managed Custom Object, Commercient Infor Visual Address Managed Custom Object, Commercient Infor Visual Customer Order Line Managed Custom Object, Commercient Infor Visual Customer Managed Custom Object, Commercient Infor Visual Customer Order Managed Custom Object, Commercient Infor Visual Part Managed Custom Object, Commercient Infor Visual Part Warehouse Managed Custom Object, Commercient Infor Visual Quote Managed Custom Object, Commercient Infor Visual Quote Line Managed Custom Object, Commercient Infor Visual Receivable Managed Custom Object, Commercient Infor Visual Receivable Line Managed Custom Object, Commercient Infor Visual Sales Rep Managed Custom Object, Commercient Infor Visual terms (related record), Contact and a custom object
- Object display names: Account, Contact, Customer Reverse Lookup Account, Infor Visual Customer, Infor Visual Customer Address, Infor Visual Order, Infor Visual Order Line, Infor Visual Part, Infor Visual Quote, Infor Visual Quote Line, Infor Visual Quote Price, Infor Visual Receivable, 6 more and 2 further templates
- Template groups: Account, Product, Opportunity, Sales order, CRM Quote and Line, Customer Multi Ship Addresses
7. Verifying
The detail of this section is part of the operational skill. Whitelisted customers fetch it with
dlake admin get_skill dlake-crmpro-salesforce/erps/infor-visual-7-1-2.
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 7.1.2 → 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 source data, 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.
How to get started
- Already a customer: the operational skill tells you how to connect, choose what to sync and run it.
Fetch it with
dlake admin get_skill dlake-crmpro-salesforce/erps/infor-visual-7-1-2, or ask support@commercient.com. - New to Commercient: contact sales@commercient.com. Becoming a customer includes registration and whitelisting, after which the operational skills and tools are available to you.
