Source ERP · 80 of 89
CRMPro → HubSpot — Sage X3: 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-hubspot/erps/sage-x3". It extends the dlake-crmpro-hubspot skill, which holds what is true whatever the source ERP. Both directions for this pair are summarised at /integrations/sage-x3-hubspot/.
CRMPro → HubSpot — Sage X3: 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-hubspot/erps/sage-x3 (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-hubspot is the destination skill this page is a child of, and the authority for the HubSpot 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 |
|---|---|---|---|
| create customer | ERP customers, business partner addresses data becomes company in HubSpot | company | customers, business partner addresses |
| create item | The templates push products to HubSpot | products | item master records, price lists |
| create order | The templates push deal to HubSpot | deal | sales order headers, customers |
| create order detail | The templates push line item to HubSpot | line item | sales order line prices, sales order line quantities |
| create invoice | The templates push deal to HubSpot | deal | sales invoices, customers |
| create invoice detail | The templates push line item to HubSpot | line item | sales invoice lines |
| create quote | The templates push deal to HubSpot | deal | sales quotes, customers |
| create quote detail | The templates push line item to HubSpot | line item | sales quote 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 | Run sequence |
|---|---|---|
| create customer | company | 5 |
| create item | products | 10 |
| create order | deal | 11 |
| create order detail | line item | 12 |
| create invoice | deal | 13 |
| create invoice detail | line item | 14 |
| create quote | deal | 15 |
| create quote detail | line item | 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 |
|---|---|---|
| new customer feed | insert only | customers, business partner addresses |
| new item feed | insert only | item master records, price lists |
| new order deal feed | insert only | sales order headers, customers |
| new order line item feed | insert only | sales order line prices, sales order line quantities |
| new invoice deal feed | insert only | sales invoices, customers |
| new invoice line item feed | insert only | sales invoice lines |
| new quote deal feed | insert only | sales quotes, customers |
| new quote line item feed | insert only | sales quote lines |
4. Order of work
The templates set run sequence to 5, 10, 11, 12, 13, 14, 15, 16. A run processes active rows in ascending run sequence, which is the order the templates put them in:
- 5 — create customer
- 10 — create item
- 11 — create order
- 12 — create order detail
- 13 — create invoice
- 14 — create invoice detail
- 15 — create quote
- 16 — create quote 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.
- new order deal feed reads new customer sync output, Order; no template in this set writes Order
- new order line item feed reads new item sync output, Order; no template in this set writes Order
- new invoice deal feed reads new customer sync output, invoice record sync output (generic name); no template in this set writes invoice record sync output (generic name)
- new invoice line item feed reads new item sync output, invoice record sync output (generic name); no template in this set writes invoice record sync output (generic name)
- new quote deal feed reads new customer sync output, quote sync output (generic name); no template in this set writes quote sync output (generic name)
- new quote line item feed reads new item sync output, quote sync output (generic name); no template in this set writes quote sync output (generic name)
5. Field mapping
Each template carries its intended mapping in field mapping.
| Template | Object | Mapped fields | First ERP → HubSpot pairs |
|---|---|---|---|
| create customer | company | 9 | Business partner customer number → Commercient AR customer code, Business partner customer name → name, Business partner address line 1 → address, Business partner address line 2 → address line 2 property, Business partner city → city property |
| create item | products | 4 | Item reference → stock keeping unit property, Item description 1,Item description 2 → name, Item description 1,Item description 2,Item description 3 → description, Base price → price |
| create order | deal | 9 | Order amount including tax → amount, Ship date → close date property, Creation date → create date property, Sales order header number, Business partner customer name → deal name property, Bill to customer number → company association |
| create order detail | line item | 5 | Item reference → product lookup property, Item reference → name, Net price → price, Line quantity → quantity, Sales order header number → deal association |
| create invoice | deal | 9 | Invoice amount including tax → amount, First due date → close date property, Creation date → create date property, Document number, Business partner customer name → deal name property, the linked Salesforce record → company association |
| create invoice detail | line item | 6 | Net price → price, Line quantity → quantity, Item reference → product lookup property, Item reference → name, Document number → deal association |
| create quote | deal | 9 | Quote amount including tax → amount, Quote order date → close date property, Quote date → create date property, Sales quote number, Business partner customer name → deal name property, Sold to customer number → company association |
| create quote detail | line item | 6 | Net price → price, Line quantity → quantity, Item reference → product lookup property, Item reference → name, Sales quote number → deal association |
6. Community templates
The catalogue carries 33 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: 33
- Default operations: insert on 33, update on 33, delete on 33
- Marked as circular sync: 0
- Licence groups they span: 5
- Destination objects: line item, deal, company, contact, products, Commercient Data Matching object, Deals, invoice and a custom object
- Object display names: create invoice, upsert contact, upsert customer, create customer, create invoice detail, create order, create order detail, upsert invoice, upsert invoice detail, create invoice deal, create invoice deal detail, 7 more and 2 further templates
- Template groups: Account, CRM Opportunity and Line, Invoice, Product
7. Verifying
The detail of this section is part of the operational skill. Whitelisted customers fetch it with
dlake admin get_skill dlake-crmpro-hubspot/erps/sage-x3.
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 X3 → HubSpot templates set up. dlake-crmpro-hubspot is the destination skill this page sits under: its own text is the authority for the HubSpot 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-hubspot/erps/sage-x3, 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.
