Source ERP · 7 of 11
CRMPro → MDC — Sage 100 (US): 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-us". 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-us-mdc/.
CRMPro → MDC — Sage 100 (US): 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-us (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 |
|---|---|---|---|
| CRM Unit of measure schedule | The templates push unit of measure schedule to MDC | unit of measure schedule | — |
| CRM unit of measure | The templates push uom to MDC | uom | — |
| CRM Price level | The templates push price level to MDC | price level | items |
| CRM Product | The templates push product to MDC | product | items |
| CRM sales order | The templates push sales order to MDC | sales order | sales order history lines, e, items, sales order headers, customers |
| CRM sales order detail | The templates push sales order detail to MDC | sales order detail | sales order history lines, sales order headers |
| CRM invoice | The templates push invoice to MDC | invoice | invoice history lines, e, items, invoice history headers, customers |
| CRM invoice detail | The templates push invoice detail to MDC | invoice detail | invoice history lines, invoice history 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 |
|---|---|---|---|
| CRM Unit of measure schedule | unit of measure schedule | name | 20 |
| CRM unit of measure | uom | name | 21 |
| CRM Price level | price level | Commercient external key | 22 |
| CRM Product | product | Commercient external key | 23 |
| CRM sales order | sales order | Commercient external key | 24 |
| CRM sales order detail | sales order detail | Commercient external key | 25 |
| CRM invoice | invoice | Commercient external key | 26 |
| CRM invoice detail | invoice detail | Commercient external key | 27 |
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 |
|---|---|---|
| CRM unit of measure schedule feed | — | — |
| CRM unit of measure feed | — | — |
| price level feed | — | items |
| product feed | insert + update | items |
| sales order feed (standard objects) | insert + update | sales order history lines, e, items, sales order headers |
| sales order line feed (standard objects) | insert + update | sales order history lines, sales order headers |
| invoice feed (standard objects) | insert + update | invoice history lines, e, items, invoice history headers |
| invoice line feed (standard objects) | insert + update | invoice history lines, invoice history headers |
4. Order of work
The templates set run sequence to 20, 21, 22, 23, 24, 25, 26, 27. A run processes active rows in ascending run sequence, which is the order the templates put them in:
- 20 — CRM Unit of measure schedule
- 21 — CRM unit of measure
- 22 — CRM Price level
- 23 — CRM Product
- 24 — CRM sales order
- 25 — CRM sales order detail
- 26 — CRM invoice
- 27 — CRM 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.
- price level feed reads CRM price book sync output (generic name); no template in this set writes CRM price book sync output (generic name)
- product feed reads product sync output; no template in this set writes product sync output
- sales order feed (standard objects) reads CRM price book sync output (generic name), CRM account sync output (generic name), customer sync output, sales order sync output (standard objects); no template in this set writes CRM price book sync output (generic name), CRM account sync output (generic name), customer sync output, sales order sync output (standard objects)
- sales order line feed (standard objects) reads sales order sync output (standard objects), product sync output, sales order line sync output (standard objects); no template in this set writes sales order sync output (standard objects), product sync output, sales order line sync output (standard objects)
- invoice feed (standard objects) reads CRM price book sync output (generic name), CRM account sync output (generic name), customer sync output, invoice sync output (standard objects); no template in this set writes CRM price book sync output (generic name), CRM account sync output (generic name), customer sync output, invoice sync output (standard objects)
- invoice line feed (standard objects) reads invoice sync output (standard objects), product sync output, invoice line sync output (standard objects); no template in this set writes invoice sync output (standard objects), product sync output, invoice line sync output (standard objects)
5. Field mapping
Each template carries its intended mapping in field mapping.
| Template | Object | Mapped fields | First ERP → MDC pairs |
|---|---|---|---|
| CRM Unit of measure schedule | unit of measure schedule | 2 | name → name, Base unit name → Base unit name |
| CRM unit of measure | uom | 2 | name → name, unit of measure schedule lookup → unit of measure schedule lookup |
| CRM Price level | price level | 3 | Item code → Commercient external key, Item code → Name, Item description → Description |
| CRM Product | product | 6 | Item code → name, Item code → Product number, Item code → Commercient external key, Item description → description, the linked default unit of measure schedule → default unit of measure schedule lookup |
| CRM sales order | sales order | 20 | returned sales order number → Commercient external key, Bill to name → Name, Bill to address line 1 → Bill to street 1, Bill to address line 2 → Bill to street 2, Bill to address line 3 → Bill to street 3 |
| CRM sales order detail | sales order detail | 13 | returned sales order number, Sequence number → Commercient external key, Shipping name → Ship to name, 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 |
| CRM invoice | invoice | 20 | Bill to address line 1 → Bill to street 1, Bill to address line 2 → Bill to street 2, Bill to address line 3 → Bill to street 3, Bill to address city → Bill to city, Bill to address state → Bill to state or province |
| CRM invoice detail | invoice detail | 14 | Invoice number, Header sequence number, Detail sequence number → Commercient external key, Shipping name → name, 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 |
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-us.
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 (US) → 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-us, 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.
