Source ERP · 6 of 11
CRMPro → MDC — Sage 100 2017: 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-mdc/erps/sage-100-2017". It extends the dlake-crmpro-mdc skill, which holds what is true whatever the source ERP. Both directions for this pair are summarised at /integrations/sage-100-2017-mdc/.
CRMPro → MDC — Sage 100 2017: 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-mdc/erps/sage-100-2017 (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-mdc is the destination skill this page is a child of, and the authority for the MDC 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 |
|---|---|---|---|
| sales order | The templates push sales order to MDC | sales order | sales order headers, customers, shipping addresses |
| sales order detail | The templates push sales order detail to MDC | sales order detail | sales order lines, sales order headers, customers, shipping addresses |
| invoice | The templates push invoice to MDC | invoice | invoice history headers, customers, shipping addresses |
| invoice detail | The templates push invoice detail to MDC | invoice detail | invoice history lines, invoice history headers, customers, shipping addresses |
| quote detail | The templates push quote detail to MDC | quote detail | sales order lines, sales order headers, customers, shipping addresses |
| Sage 100 2017 Sales order | The templates push Commercient Sage 100 2017 sales order object to MDC | Commercient Sage 100 2017 sales order object | sales order headers, customers, shipping addresses |
| Sage 100 2017 Sales order Detail | The templates push Commercient Sage 100 2017 sales order detail object to MDC | Commercient Sage 100 2017 sales order detail object | sales order lines, sales order headers, customers, shipping addresses |
| Sage 100 2017 Invoice | The templates push Commercient Sage 100 2017 invoice object to MDC | Commercient Sage 100 2017 invoice object | invoice history headers, customers, shipping addresses |
| Sage 100 2017 Invoice Detail | The templates push Commercient Sage 100 2017 invoice detail object to MDC | Commercient Sage 100 2017 invoice detail object | invoice history lines, invoice history headers, customers, shipping addresses |
| CRM Quote and Line | The templates push quote to MDC | quote | sales order headers, customers, shipping addresses |
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 |
|---|---|---|---|
| sales order | sales order | Commercient external key | 22 |
| sales order detail | sales order detail | Commercient external key | 23 |
| invoice | invoice | Commercient external key | 24 |
| invoice detail | invoice detail | Commercient external key | 25 |
| quote | quote | Commercient external key | 26 |
| quote detail | quote detail | Commercient external key | 27 |
| Sage 100 2017 Sales order | Commercient Sage 100 2017 sales order object | Commercient external key | 28 |
| Sage 100 2017 Sales order Detail | Commercient Sage 100 2017 sales order detail object | Commercient external key | 29 |
| Sage 100 2017 Invoice | Commercient Sage 100 2017 invoice object | Commercient external key | 30 |
| Sage 100 2017 Invoice Detail | Commercient Sage 100 2017 invoice detail object | Commercient external key | 31 |
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 |
|---|---|---|
| sales order feed (standard objects) | insert only | sales order headers, customers, shipping addresses |
| sales order line feed (standard objects) | insert only | sales order lines, sales order headers, customers, shipping addresses |
| invoice feed (standard objects) | insert + update | invoice history headers, customers, shipping addresses |
| invoice line feed (standard objects) | insert + update | invoice history lines, invoice history headers, customers, shipping addresses |
| quote feed (standard objects) | insert only | sales order headers, customers, shipping addresses |
| quote line feed (standard objects) | insert only | sales order lines, sales order headers, customers, shipping addresses |
| sales order feed (Commercient objects) | insert only | sales order headers, customers, shipping addresses |
| sales order line feed (Commercient objects) | insert only | sales order lines, sales order headers, customers, shipping addresses |
| invoice feed | insert + update | invoice history headers, customers, shipping addresses |
| invoice line feed (Commercient objects) | insert + update | invoice history lines, invoice history headers, customers, shipping addresses |
4. Order of work
The templates set run sequence from 22 to 31. A run processes active rows in ascending run sequence, which is the order the templates put them in:
- 22 — sales order
- 23 — sales order detail
- 24 — invoice
- 25 — invoice detail
- 26 — quote
- 27 — quote detail
- 28 — Sage 100 2017 Sales order
- 29 — Sage 100 2017 Sales order Detail
- 30 — Sage 100 2017 Invoice
- 31 — Sage 100 2017 Invoice Detail
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.
- sales order feed (standard objects) reads AR customer, CRM account sync output (alternative generic name), sales order sync output (standard objects); no template in this set writes AR customer, CRM account sync output (alternative generic name), sales order sync output (standard objects)
- sales order line feed (standard objects) reads CRM account sync output (alternative generic name), Sage 100 product sync output, sales order sync output (standard objects), sales order line sync output (standard objects); no template in this set writes CRM account sync output (alternative generic name), Sage 100 product sync output, sales order sync output (standard objects), sales order line sync output (standard objects)
- invoice feed (standard objects) reads AR customer, CRM account sync output (alternative generic name), invoice sync output (standard objects); no template in this set writes AR customer, CRM account sync output (alternative generic name), invoice sync output (standard objects)
- invoice line feed (standard objects) reads invoice sync output (standard objects), CRM account sync output (alternative generic name), Sage 100 product sync output, invoice line sync output (standard objects); no template in this set writes invoice sync output (standard objects), CRM account sync output (alternative generic name), Sage 100 product sync output, invoice line sync output (standard objects)
- quote line feed (standard objects) reads CRM account sync output (alternative generic name), Sage 100 product sync output, quote sync output (standard objects), quote line sync output (standard objects); no template in this set writes CRM account sync output (alternative generic name), Sage 100 product sync output, quote sync output (standard objects), quote line sync output (standard objects)
- sales order feed (Commercient objects) reads AR customer, CRM account sync output (alternative generic name), sales order sync output (Commercient objects); no template in this set writes AR customer, CRM account sync output (alternative generic name), sales order sync output (Commercient objects)
- sales order line feed (Commercient objects) reads CRM account sync output (alternative generic name), Sage 100 product sync output, sales order sync output (standard objects), sales order line sync output (Commercient objects); no template in this set writes CRM account sync output (alternative generic name), Sage 100 product sync output, sales order sync output (standard objects), sales order line sync output (Commercient objects)
- invoice feed reads AR customer, CRM account sync output (alternative generic name), invoice sync output; no template in this set writes AR customer, CRM account sync output (alternative generic name), invoice sync output
- invoice line feed (Commercient objects) reads invoice sync output (standard objects), CRM account sync output (alternative generic name), Sage 100 product sync output, invoice line sync output (Commercient objects); no template in this set writes invoice sync output (standard objects), CRM account sync output (alternative generic name), Sage 100 product sync output, invoice line sync output (Commercient objects)
- quote feed (standard objects) reads AR customer, CRM account sync output (alternative generic name), quote sync output (standard objects); no template in this set writes AR customer, CRM account sync output (alternative generic name), quote sync output (standard objects)
5. Field mapping
Each template carries its intended mapping in field mapping.
| Template | Object | Mapped fields | First ERP → MDC pairs |
|---|---|---|---|
| sales order | sales order | 20 | Sales order number → Commercient external key, Sales order number → name, Address line 1 → Bill to street 1, Address line 2 → Bill to street 2, Address line 3 → Bill to street 3 |
| sales order detail | sales order detail | 12 | Sales order number, Line key → Commercient external key, Ship to address line 1 → Ship to street 1, Ship to address line 2 → Ship to street 2, Ship to address line 3 → Ship to street 3, Shipping city → Ship to city |
| invoice | invoice | 20 | Address line 1 → Bill to street 1, Address line 2 → Bill to street 2, Address line 3 → Bill to street 3, City → Bill to city, State → Bill to state or province |
| invoice detail | invoice detail | 12 | Invoice number, Header sequence number, Detail sequence number → Commercient external key, Ship to address line 1 → Ship to street 1, Ship to address line 2 → Ship to street 2, Ship to address line 3 → Ship to street 3, Shipping city → Ship to city |
| quote | quote | 20 | Sales order number → Commercient external key, Sales order number → name, Address line 1 → Bill to street 1, Address line 2 → Bill to street 2, Address line 3 → Bill to street 3 |
| quote detail | quote detail | 12 | Sales order number, Line key → Commercient external key, Ship to address line 1 → Ship to street 1, Ship to address line 2 → Ship to street 2, Ship to address line 3 → Ship to street 3, Shipping city → Ship to city |
| Sage 100 2017 Sales order | Commercient Sage 100 2017 sales order object | 4 | Sales order number → external key property, Sales order number → name, AR division number, Customer number → customer account lookup, Commercient Price List → price list lookup |
| Sage 100 2017 Sales order Detail | Commercient Sage 100 2017 sales order detail object | 5 | Sales order number, Line key → Commercient external key, Sales order number, Line key → name, Sales order number → sales order lookup, Item code → product lookup, Unit → unit of measure lookup |
| Sage 100 2017 Invoice | Commercient Sage 100 2017 invoice object | 4 | Invoice number, Header sequence number → external key property, Invoice number, Header sequence number → Name, AR division number, Customer number → customer account lookup, Commercient Price List → price list lookup |
| Sage 100 2017 Invoice Detail | Commercient Sage 100 2017 invoice detail object | 5 | Invoice number, Header sequence number, Detail sequence number → external key property, Invoice number, Header sequence number, Detail sequence number → name, the linked Salesforce record → invoice lookup, Item code → product lookup, unit of measure → unit of measure lookup |
6. Verifying
The detail of this section is part of the operational skill. Whitelisted customers fetch it with
dlake admin get_skill dlake-crmpro-mdc/erps/sage-100-2017.
7. 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 2017 → MDC templates set up. dlake-crmpro-mdc is the destination skill this page sits under: its own text is the authority for the MDC 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-mdc/erps/sage-100-2017, 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.
