Source ERP · 53 of 105

CRMPro → Salesforce — Macola Progression: what the template catalogue carries

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/macola-progression". 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/macola-progression-salesforce/.

CRMPro → Salesforce — Macola Progression: what the template catalogue carries

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/macola-progression (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. The catalogue ships no Standard template for this pair. Its templates are community templates, authored in a tenant and imported the same way as any other, so what follows is what that set amounts to — how many templates, which operations they default to, which destination objects they write and which groups they fall in. This page grows as the catalogue does.

1. Community templates

The catalogue carries 46 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.

  • Templates: 46
  • Default operations: insert on 46, update on 46, delete on 46
  • Marked as circular sync: 0
  • Licence groups they span: 10
  • Destination objects: Content document, Account, Macola 10 Quote Detail (custom object), Macola 10 Quote Header (custom object), Macola 10 Sales Order Detail (custom object), Macola 10 Sales Order Header (custom object), Macola 10 Sales Order History Detail (custom object), Macola 10 Sales Order History Header (custom object), Opportunity, Product and 8 custom objects
  • Object display names: Document Sync - Macola Progression quote sync output (generic name), Document Sync - Macola Progression Sales Order, Document Sync - Macola Progression Sales Order History, Get Account, Sync Macola Progression quote sync output (generic name) Detail, Sync Macola Progression quote sync output (generic name) Header, Sync Macola Progression Sales Order Detail, Sync Macola Progression Sales Order Header, Sync Macola Progression Sales Order History Detail, Sync Macola Progression Sales Order History Header, Sync opportunity sync output (generic name), Account and 12 more
  • Template groups: Sales order, Account, Opportunity, CRM Opportunity and Line, Product, Invoice

2. 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/macola-progression.

3. 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 Macola Progression → Salesforce template catalogue carries. 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/macola-progression, 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.