Source ERP · 73 of 105
CRMPro → Salesforce — Sage 100 2016: 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/sage-100-2016". 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/sage-100-2016-salesforce/.
CRMPro → Salesforce — Sage 100 2016: 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/sage-100-2016 (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 |
|---|---|---|---|
| GET USER | The templates push users to Salesforce | users | — |
| 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, Commercient AR Customer Managed Custom Object, Commercient Salesperson Managed Custom Object | customers, shipping addresses, salespeople |
| 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 Ship-To Address Managed Custom Object | shipping addresses |
| Invoice | Both Open and Historical invoices are synchronized | Commercient Invoice History Header Managed Custom Object, Commercient Invoice History Detail Managed Custom Object, Commercient Payment History Managed Custom Object | invoice history headers, open invoices, salespeople, invoice history lines, items |
| 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 Sales Order Line Managed Custom Object, Commercient Sales Order Header Managed Custom Object | sales order lines, sales order headers |
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 USER | users | — | 0 |
| Sage 100 2016 Sales Person | Commercient Salesperson Managed Custom Object | Commercient external key | 2 |
| Sage 100 2016 Account | Account | Commercient AR customer code | 3 |
| Sage 100 2016 Customer | Commercient AR Customer Managed Custom Object | Commercient external key | 4 |
| Sage 100 2016 Shipping address | Commercient Ship-To Address Managed Custom Object | Commercient external key | 5 |
| Sage 100 2016 Sales order header | Commercient Sales Order Header Managed Custom Object | Commercient sales order number | 6 |
| Sage 100 2016 Sales order detail | Commercient Sales Order Line Managed Custom Object | Commercient external key | 7 |
| Sage 100 2016 Invoice history header | Commercient Invoice History Header Managed Custom Object | Commercient external key | 8 |
| Sage 100 2016 Invoice history detail | Commercient Invoice History Detail Managed Custom Object | Commercient external key | 9 |
| Sage 100 2016 Invoice payment | Commercient Payment History Managed Custom Object | Commercient external key | 10 |
| Sage 100 2016 Customer Reverse Lookup | Account | Commercient AR customer code | 11 |
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 | salespeople |
| account feed | insert + update | customers, shipping addresses |
| customer feed | insert + update | customers, salespeople |
| shipping address feed | insert + update | shipping addresses |
| sales order feed | insert + update | sales order headers |
| sales order line feed | insert + update | sales order lines, sales order headers |
| invoice history feed | insert + update | invoice history headers, open invoices, salespeople |
| invoice history line feed | insert + update | invoice history lines, items |
| payment history feed | insert + update | payment history, invoice history headers |
| customer account lookup feed | insert + update | customers |
4. Order of work
The templates set run sequence from 0 to 11. A run processes active rows in ascending run sequence, which is the order the templates put them in:
- 0 — GET USER
- 2 — Sage 100 2016 Sales Person
- 3 — Sage 100 2016 Account
- 4 — Sage 100 2016 Customer
- 5 — Sage 100 2016 Shipping address
- 6 — Sage 100 2016 Sales order header
- 7 — Sage 100 2016 Sales order detail
- 8 — Sage 100 2016 Invoice history header
- 9 — Sage 100 2016 Invoice history detail
- 10 — Sage 100 2016 Invoice payment
- 11 — Sage 100 2016 Customer Reverse Lookup
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.
- account feed reads user sync output
- customer account lookup feed reads AR customer sync output (generic name)
- customer feed reads Salesforce account sync output (generic name), salesperson sync output (generic name)
- shipping address feed reads Salesforce account sync output (generic name), AR customer sync output (generic name), salesperson sync output (generic name)
- invoice history feed reads Salesforce account sync output (generic name), AR customer sync output (generic name), salesperson sync output (generic name), shipping address sync output (generic name)
- invoice history line feed reads invoice history sync output (generic name)
- payment history feed reads invoice history sync output (generic name)
- sales order line feed reads sales order sync output (generic name)
- sales order feed reads Salesforce account sync output (generic name), AR customer sync output (generic name), salesperson sync output (generic name)
5. Field mapping
Each template carries its intended mapping in field mapping.
| Template | Object | Mapped fields | First ERP → Salesforce pairs |
|---|---|---|---|
| Sage 100 2016 Sales Person | Commercient Salesperson Managed Custom Object | 26 | Salesperson division,Salesperson number → Commercient external key, Salesperson name → Commercient name, Salesperson division → Commercient salesperson division, Salesperson number → Commercient salesperson number, Address line 1 → Commercient address line 1 |
| Sage 100 2016 Account | Account | 22 | AR division number, Customer number → Commercient AR customer code, Customer name → Name, Address line 1 → Billing address line 1, Address line 2 → Billing address line 2, Address line 3 → Billing address line 3 |
| Sage 100 2016 Customer | Commercient AR Customer Managed Custom Object | 79 | Customer number → Commercient external key, Customer name → Commercient name, Customer number → Commercient customer number, Customer name → Commercient customer name, AR division number → Commercient AR division number |
| Sage 100 2016 Shipping address | Commercient Ship-To Address Managed Custom Object | 34 | AR division number,Customer number,Ship-to code → Commercient external key, AR division number,Customer number,Ship-to code → Commercient name, AR division number → Commercient AR division number, Customer number → Commercient customer number, Ship-to code → Commercient ship to code |
| Sage 100 2016 Sales order header | Commercient Sales Order Header Managed Custom Object | 106 | Sales order number → Commercient sales order number, Order date → Commercient order date, Order type → Commercient order type, Order status → Commercient order status, Master repeating order number → Commercient master repeating order number |
| Sage 100 2016 Sales order detail | Commercient Sales Order Line Managed Custom Object | 65 | Sales order number,Line key → Commercient external key, Order type → Commercient order type, Sales order number → Commercient sales order number, Line key → Commercient line key, Line sequence number → Commercient line sequence number |
| Sage 100 2016 Invoice history header | Commercient Invoice History Header Managed Custom Object | 124 | Invoice number, Header sequence number → Commercient external key, Invoice number, Header sequence number → Commercient name, Invoice number → Commercient invoice number, Header sequence number → Commercient header sequence number, Module code → Commercient module code |
| Sage 100 2016 Invoice history detail | Commercient Invoice History Detail Managed Custom Object | 59 | Invoice number, Header sequence number, Detail sequence number → Commercient external key, Invoice number → Commercient invoice number, Header sequence number → Commercient header sequence number, Detail sequence number → Commercient detail sequence number, Item code → Commercient item code |
| Sage 100 2016 Invoice payment | Commercient Payment History Managed Custom Object | 33 | AR division number → Commercient AR division number, Customer number → Commercient customer number, Invoice number → Commercient invoice number, Invoice type → Commercient invoice type, Invoice header sequence number → Commercient invoice header sequence number |
| Sage 100 2016 Customer Reverse Lookup | Account | 2 | AR division number,Customer number → Commercient AR customer code, the linked Salesforce record → Commercient Sage customer record |
6. Community templates
The catalogue carries 244 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: 244
- Default operations: insert on 244, update on 244, delete on 244
- Marked as circular sync: 2
- Licence groups they span: 14
- Destination objects: Account, Commercient Inventory Item Managed Custom Object, Commercient Sales Order Line Managed Custom Object, Commercient Invoice History Detail Managed Custom Object, Commercient Invoice History Header Managed Custom Object, Commercient Payment History Managed Custom Object, Commercient Sales Order Header Managed Custom Object, Commercient AR Customer Managed Custom Object, Commercient Purchase Order Header Managed Custom Object, Commercient Vendor Managed Custom Object, Commercient Item Warehouse Managed Custom Object, Commercient Purchase Order Line Managed Custom Object, Commercient Ship-To Address Managed Custom Object, Commercient Salesperson Managed Custom Object, Commercient general ledger Account Managed Custom Object, Product, Content document, Account, Commercient Sales Order History Line Managed Custom Object, Commercient Sales Order History Header Managed Custom Object, 16 more and 14 custom objects
- Object display names: Sync Item, Sync Item warehouse, Sync Account, Sync Customer, Sync Invoice history detail, Sync Invoice history header, Sync sales order detail, Sync Transaction payment history, Sync general ledger account, Sync Purchase order detail, Sync Purchase order header, Sync Sales order header, 49 more and 42 further templates
- Template groups: Account, Product, Invoice History Headers, Sales order, Purchase Order, Customer Multi Ship Addresses, Invoice, File or Document Sync
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/sage-100-2016.
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 Sage 100 2016 → 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/sage-100-2016, 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.
