Source ERP · 2 of 7
CRMPro → Magento — Microsoft Dynamics GP 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-magento/erps/microsoft-dynamics-gp-2017". It extends the dlake-crmpro-magento skill, which holds what is true whatever the source ERP. Both directions for this pair are summarised at /integrations/microsoft-dynamics-gp-2017-magento/.
CRMPro → Magento — Microsoft Dynamics GP 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-magento/erps/microsoft-dynamics-gp-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-magento is the destination skill this page is a child of, and the authority for the Magento 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 |
|---|---|---|---|
| Magento customer | ERP country code, customer master, internet address data becomes customers in Magento | customers | customers, internet addresses, customer addresses, matched customer feed, country code, countries and regions |
| Magento customer update | ERP country code, customer master, countries and regions data becomes customers in Magento | customers | customers, customer addresses, matched customer feed, country, country code, countries and regions |
| Magento product | ERP item master, item quantity, item currency data becomes products in Magento | products | items, item quantities, item price lists, item currencies |
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 |
|---|---|---|---|
| Magento customer | customers | external key column | 1 |
| Magento customer update | customers | external key column | 2 |
| Magento product | products | external key column | 3 |
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 |
|---|---|---|
| customer feed | insert only | customers, internet addresses, customer addresses, matched customer feed, country code |
| customer update feed | insert only | customers, customer addresses, matched customer feed, country, country code |
| product feed | insert + update | items, item quantities, item price lists, item currencies |
4. Order of work
The templates set run sequence to 1, 2, 3. A run processes active rows in ascending run sequence, which is the order the templates put them in:
- 1 — Magento customer
- 2 — Magento customer update
- 3 — Magento product
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.
- customer feed reads retrieved customer sync output (generic name); no template in this set writes retrieved customer sync output (generic name)
- customer update feed reads retrieved customer sync output (generic name); no template in this set writes retrieved customer sync output (generic name)
- product feed reads retrieved product sync output (generic name); no template in this set writes retrieved product sync output (generic name)
5. Field mapping
Each template carries its intended mapping in field mapping.
| Template | Object | Mapped fields | First ERP → Magento pairs |
|---|---|---|---|
| Magento customer | customers | 35 | email → email, Contact person → Contact person, Given name → Given name, Family name → Family name, Commercient identifier (custom attribute) → Commercient identifier (custom attribute) |
| Magento customer update | customers | 10 | email → email, Given name → Given name, Family name → Family name, Commercient identifier (custom attribute) → Commercient identifier (custom attribute), Customer number (custom attribute) → Customer number (custom attribute) |
| Magento product | products | 46 | sku → sku, Weight → Weight, Commercient identifier (custom attribute) → Commercient identifier (custom attribute), →, Description (custom attribute) → Description (custom attribute) |
6. Community templates
The catalogue carries 4 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: 4
- Default operations: insert on 4, update on 4, delete on 4
- Marked as circular sync: 0
- Licence groups they span: 1
- Destination objects: customers, products, Update Price
- Object display names: Magento customer, Magento customer update, Magento product, Magento update price
7. Verifying
The detail of this section is part of the operational skill. Whitelisted customers fetch it with
dlake admin get_skill dlake-crmpro-magento/erps/microsoft-dynamics-gp-2017.
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 Microsoft Dynamics GP 2017 → Magento templates set up. dlake-crmpro-magento is the destination skill this page sits under: its own text is the authority for the Magento 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-magento/erps/microsoft-dynamics-gp-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.
