CRMPro → Salesforce — Exact MAX: what the shipped templates set up

CRMPro → Salesforce — Exact MAX: 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-salesforce/erps/exact-max (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, then come back here for what this source’s own templates set. This page grows as the catalogue does.

1. What the templates deliver

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.

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.

4. Order of work

The templates set run sequence from 1 to 22. A run processes active rows in ascending run sequence, which is the order the templates put them in:

• 1 — Sales Person
• 4 — Account
• 5 — Customer Master
• 6 — Customer Reverse Lookup Account
• 7 — Shipping Master
• 8 — Commodity Codes
• 9 — Part Master
• 10 — Sales Order Header
• 11 — Sales Order Line
• 12 — Invoice Header
• 13 — Invoice Line
• 14 — Product
• 15 — Product Reverse Lookup
• 16 — Create Standard Price Book
• 17 — Get User
• 19 — Part Stock
• 20 — Update Standard Pricebook
• 21 — Part Sales
• 22 — Product Structure

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 account lookup sync output (generic name) reads customer sync output (generic name)
• account feed reads salesperson sync output (generic name), user sync output
• customer feed reads salesperson sync output (generic name), account sync output (generic name)
• shipping address feed reads customer sync output (generic name), account sync output (generic name)
• part master feed reads commodity code sync output (generic name)
• product reverse lookup feed (generic name) reads product record sync output (generic name)
• part stock feed reads part master sync output (generic name)
• part sales feed reads part master sync output (generic name), product record sync output (generic name)
• invoice feed reads account sync output (generic name), customer sync output (generic name), salesperson sync output (generic name)
• invoice line feed reads invoice sync output (generic name), part master sync output (generic name)
• standard price book feed (new entries) reads product record sync output (generic name)
• standard price book feed (changes) reads product record sync output (generic name)
• product feed reads part master sync output (generic name)
• product structure feed reads part master sync output (generic name), product record sync output (generic name)
• sales order feed reads account sync output (generic name), customer sync output (generic name), salesperson sync output (generic name)
• sales order line feed reads sales order sync output (generic name), part master sync output (generic name)

5. Field mapping

Each template carries its intended mapping in field mapping.

6. Community templates

The catalogue carries 44 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: 44
• Default operations: insert on 44, update on 44, delete on 44
• Marked as circular sync: 0
• Licence groups they span: 8
• Destination objects: Account, Commercient Part Master Managed Custom Object, Commercient Sales Order Detail Managed Custom Object, Commercient Commodity Codes Managed Custom Object, Commercient Exact Max Customer Master Managed Custom Object, Commercient Invoice Line Managed Custom Object, Commercient Invoice Master Managed Custom Object, Commercient Part Sales Managed Custom Object, Commercient Sales Rep Master Managed Custom Object, Commercient Shipping Master Managed Custom Object, Commercient Sales Order Master Managed Custom Object, Price book entry, Product, account, Commercient Code Master Managed Custom Object, Commercient Matching Managed Custom Object, Commercient Part Stock Managed Custom Object, Commercient Product Structure Managed Custom Object, Customer Part Data (custom object), 3 more and 2 custom objects
• Object display names: Account, Commodity Codes, Create Standard Price Book, Customer Master, Invoice Header, Invoice Line, Part Master, Part Sales, Product, Product Reverse Lookup, Sales Order Header, Sales Order Line, 15 more and 2 further templates
• Template groups: Account, Product, Sales order, Invoice, Customer Multi Ship Addresses

7. 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/exact-max.

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 Exact MAX → Salesforce templates set up. 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/exact-max, 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.