Source ERP · 2 of 105

CRMPro → Salesforce — Acumatica Cloud: 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-salesforce/erps/acumatica-cloud". 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/acumatica-cloud-salesforce/.

CRMPro → Salesforce — Acumatica Cloud: 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/acumatica-cloud (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

GroupBusiness outcomeObjectsSource tables and views
Get UserThe templates push User to Salesforce. New records are created, existing ones updated, and records removed in the ERP are deleted.User—
AccountIn addition to creating the Account record from your ERP customer records, Commercient syncs over the entire Accounting AR Customer record into a Commercient AR Customer object which is a Managed Custom Object (MCO). A lookup field is provided to lookup to the default AR Customer record MCO from the Account record. New records are created, existing ones updated, and records removed in the ERP are deleted.Account, Contact, Commercient Acumatica Customer Managed Custom Object, Commercient Acumatica Employee Managed Custom Objectsales reps, salespeople, customers, customer locations, customer contacts, contacts
AR Invoice PaymentsCommercient Syncs the payment details that are held in the receivables file and held against an invoice in the ERP. The amount received from a customer, the date of payment, the method of payment, whether partial or full payment, etc New records are created and existing ones updated; none are deleted.Commercient Acumatica Payment Managed Custom Object, Commercient Acumatica Payment Detail Managed Custom Objectpayments, payment details
CRM Opportunity and LineERP sales order, sales order detail data becomes Opportunity, Opportunity line item in Salesforce. New records are created and existing ones updated; none are deleted.Opportunity, Opportunity line itemsales orders, sales order details
CRM Quote and LineERP sales order, sales order detail data becomes Quote, Quote line item in Salesforce. New records are created and existing ones updated; none are deleted.Quote, Quote line itemsales orders, sales order details
Customer Multi Ship AddressesIf you are using multiple ship to addresses for a given AR Customer in your ERP system then you will be able to see all the addresses inside the CRM Account screen in a Commercient Multi Ship To Address MCO related list. New records are created and existing ones updated; none are deleted.Commercient Acumatica Contact Managed Custom Objectcontacts, customer contacts
ProductERP stock item data becomes Commercient Stock Item Managed Custom Object, Product in Salesforce. New records are created and existing ones updated; none are deleted.Commercient Stock Item Managed Custom Object, Productstock items
InvoiceBoth Open and Historical invoices are synchronized. Open invoice changes, such as a balance change, or a terms change are reflected in the CRM as they sync based on the frequency of the sync you have chosen (every hour, for example). New records are created and existing ones updated; none are deleted.Commercient Acumatica Sales Invoice Managed Custom Object, Commercient Acumatica Sales Invoice Detail Managed Custom Objectsales invoices, sales invoice lines
PricebookERP stock item data becomes Price book entry in Salesforce. New records are created and existing ones updated; none are deleted.Price book entrystock items
Sales orderCommercient will sync the Sales Orders from the ERP Sales Order Entry module to the Commercient Sales Order Header (MCO) objects in CRM. In the CRM, customer service and sales people can visualize the status of the order such as on hold, backorder, forward order, scheduled for delivery, whether it has shipped, and completion status. New records are created and existing ones updated; none are deleted.Commercient Acumatica Sales Order Managed Custom Object, Commercient Acumatica Sales Order Details Managed Custom Objectsales orders, sales order details

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 nameDestination objectMatching keyRun sequence
AccountAccountCommercient AR customer code1
Acumatica SalespersonCommercient Acumatica Employee Managed Custom ObjectCommercient external key (Acumatica and MYOB package)1
Acumatica Cloud CustomerCommercient Acumatica Customer Managed Custom ObjectCommercient external key (Acumatica and MYOB package)2
Acumatica Cloud AddressCommercient Acumatica Contact Managed Custom ObjectCommercient external key (Acumatica and MYOB package)3
ProductProductCommercient external key (earlier package)4
Acumatica Cloud Item MasterCommercient Stock Item Managed Custom ObjectCommercient external key (Acumatica and MYOB package)5
Acumatica Cloud Sales orderCommercient Acumatica Sales Order Managed Custom ObjectCommercient external key (Acumatica and MYOB package)6
Acumatica Cloud Sales order detailCommercient Acumatica Sales Order Details Managed Custom ObjectCommercient external key (Acumatica and MYOB package)7
Acumatica Cloud Invoice headerCommercient Acumatica Sales Invoice Managed Custom ObjectCommercient external key (Acumatica and MYOB package)8
Acumatica Cloud Invoice detailCommercient Acumatica Sales Invoice Detail Managed Custom ObjectCommercient external key (Acumatica and MYOB package)9
Acumatica Cloud PaymentCommercient Acumatica Payment Managed Custom ObjectCommercient external key (Acumatica and MYOB package)10
Acumatica Cloud Payment detailCommercient Acumatica Payment Detail Managed Custom ObjectCommercient external key (Acumatica and MYOB package)11
Create Standard Price BookPrice book entryExternal key (custom field)12
Update Standard PricebookPrice book entryExternal key (custom field)13
OpportunityOpportunityExternal key (custom field)14
ContactContactCommercient external key (custom field)15
Opportunity line itemOpportunity line itemExternal key (custom field)15
Get UserUserId17
QuoteQuoteExternal key (custom field)22
Quote LineQuote line itemExternal key (custom field)23

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.

ViewChange detectionSource tables
account feedinsert + updatesales reps, salespeople, customers, customer locations, customer contacts
salesperson feedinsert + updatesales reps, salespeople
customer feedinsert + updatecustomers
address feedinsert + updatecontacts, customer contacts
product feedinsert + updatestock items
item master feedinsert + updatestock items
sales order feedinsert + updatesales orders
sales order line feedinsert + updatesales order details
invoice feedinsert + updatesales invoices
invoice line feedinsert + updatesales invoice lines
payment feedinsert + updatepayments
payment detail feedinsert + updatepayment details
price book feed (new entries)insert + updatestock items
price book feed (changes)insert + updatestock items
opportunity feedinsert onlysales orders
contact feedinsert + updatecontacts, customer contacts, sales reps
opportunity line feedinsert + updatesales order details
quote feedinsert + updatesales orders
quote line feedinsert + updatesales order details

4. Order of work

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

  • 1 — Account, Acumatica Salesperson
  • 2 — Acumatica Cloud Customer
  • 3 — Acumatica Cloud Address
  • 4 — Product
  • 5 — Acumatica Cloud Item Master
  • 6 — Acumatica Cloud Sales order
  • 7 — Acumatica Cloud Sales order detail
  • 8 — Acumatica Cloud Invoice header
  • 9 — Acumatica Cloud Invoice detail
  • 10 — Acumatica Cloud Payment
  • 11 — Acumatica Cloud Payment detail
  • 12 — Create Standard Price Book
  • 13 — Update Standard Pricebook
  • 14 — Opportunity
  • 15 — Contact, Opportunity line item
  • 17 — Get User
  • 22 — Quote
  • 23 — Quote Line

Several of these rows share a run sequence value: each template group carries its own numbering, so give the imported processes an order across the whole set rather than taking the template values as one.

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.

  • account feed reads salesperson sync output, user sync output
  • payment feed reads account sync output, customer sync output
  • payment detail feed reads payment sync output
  • contact feed reads account sync output
  • opportunity feed reads account sync output
  • opportunity line feed reads product sync output, opportunity sync output
  • quote feed reads account sync output, opportunity sync output
  • quote line feed reads Salesforce quote sync output (generic name), product sync output
  • customer feed reads account sync output
  • address feed reads account sync output, customer sync output
  • item master feed reads product sync output
  • invoice feed reads account sync output, customer sync output
  • invoice line feed reads invoice sync output, item master sync output
  • price book feed (new entries) reads product sync output, standard price book sync output (generic name); no template in this set writes standard price book sync output (generic name)
  • price book feed (changes) reads product sync output, standard price book sync output (generic name); no template in this set writes standard price book sync output (generic name)
  • sales order feed reads account sync output, customer sync output
  • sales order line feed reads sales order sync output, item master sync output

5. Field mapping

Each template carries its intended mapping in field mapping.

TemplateObjectMapped fieldsFirst ERP → Salesforce pairs
AccountAccount24Customer identifier → Commercient AR customer code, Customer name → Name, Customer identifier → ERP unique identifier (custom field), Display name → Doing business as name (custom field), Email → Account emails (custom field)
Acumatica SalespersonCommercient Acumatica Employee Managed Custom Object5Commission → Commission (custom field), Employee identifier → Commercient employee identifier, Location identifier → Location identifier (custom field), Active → Is active (custom field), Location name → Location name (custom field)
Acumatica Cloud CustomerCommercient Acumatica Customer Managed Custom Object49Customer identifier → Commercient external key (Acumatica and MYOB package), Customer name → Name, Account reference → Account reference, Apply overdue charges → Apply overdue charges, Automatically apply payments → Automatically apply payments
Acumatica Cloud AddressCommercient Acumatica Contact Managed Custom Object67Contact identifier, Type → Commercient external key (Acumatica and MYOB package), Customer identifier → Account, Customer identifier → Commercient Acumatica customer (related record), Display name, Contact identifier, Type → Name, Active → Active (custom field)
ProductProduct6Inventory identifier → Commercient external key (earlier package), Description → Name, Inventory identifier → Product code, Description → Description, Item status → Active
Acumatica Cloud Item MasterCommercient Stock Item Managed Custom Object74Inventory identifier → Commercient external key (Acumatica and MYOB package), the linked Salesforce record → Commercient product (related record), Inventory identifier → Commercient name, Inventory classification code → Commercient inventory classification code, Auto incremental value → Commercient auto incremental value
Acumatica Cloud Sales orderCommercient Acumatica Sales Order Managed Custom Object64Order number → Commercient external key (Acumatica and MYOB package), Customer identifier → Account, Customer identifier → Commercient Acumatica customer (related record), Order number → Name, Approved → Approved (custom field)
Acumatica Cloud Sales order detailCommercient Acumatica Sales Order Details Managed Custom Object46Order number, Line number → Commercient external key (Acumatica and MYOB package), the linked Salesforce record → Commercient Acumatica sales order (related record), the linked Salesforce record → Commercient Acumatica item master (related record), Order number → Order number, account → account
Acumatica Cloud Invoice headerCommercient Acumatica Sales Invoice Managed Custom Object17Reference number → Commercient external key (Acumatica and MYOB package), Customer identifier → Commercient account identifier, Customer identifier → Commercient Acumatica Customer Managed Custom Object, Reference number → Name, Amount → Amount
Acumatica Cloud Invoice detailCommercient Acumatica Sales Invoice Detail Managed Custom Object16Sales invoice number,Line number → Commercient external key (Acumatica and MYOB package), Sales invoice number,Line number → Commercient name, the linked Salesforce record → Commercient Acumatica sales invoice (related record), the linked Salesforce record → Commercient Acumatica item master (related record), Reference number → Commercient reference number
Acumatica Cloud PaymentCommercient Acumatica Payment Managed Custom Object21Reference number → Commercient external key (Acumatica and MYOB package), Customer identifier → Account (custom field), Customer identifier → Commercient Acumatica customer (related record), Reference number → Name, Application date → Application date
Acumatica Cloud Payment detailCommercient Acumatica Payment Detail Managed Custom Object10Payment header reference number,Reference number → Commercient external key (Acumatica and MYOB package), the linked Salesforce record → Commercient Acumatica payment (related record), Payment header reference number,Reference number → Name, Amount paid → Amount paid, Balance write off → Balance write off
Create Standard Price BookPrice book entry5Inventory identifier → External key (custom field), price book lookup → price book lookup, the linked Salesforce record → product lookup, Active → Active, Current standard cost → Unit price
Update Standard PricebookPrice book entry3Inventory identifier → External key (custom field), Active → Active, Current standard cost → Unit price
OpportunityOpportunity8Order number → External key (custom field), Customer identifier → account lookup, Description → Name, Effective date → close date property, Free on board point → Free on board (custom field)
ContactContact20Commercient external key column → Commercient external key (custom field), account lookup → account lookup, Family name → Family name, Given name → Given name, Suffix → Suffix
Opportunity line itemOpportunity line item5Order number, Line number, Line type → External key (custom field), the linked Salesforce record → price book entry lookup, the linked Salesforce record → Opportunity, Unit price → Unit price, Order quantity → Quantity
QuoteQuote17Order number → External key (custom field), Order number → Name, the linked Salesforce record → Opportunity identifier, the linked Salesforce record → account lookup, the linked Salesforce record → price book lookup
Quote LineQuote line item6Order number, Line number, Line type → External key (custom field), returned inventory identifier → product lookup, price book entry lookup → price book entry lookup, Order number → Quote, Order quantity → Quantity

6. Community templates

The catalogue carries 170 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: 170
  • Default operations: insert on 170, update on 170, delete on 170
  • Marked as circular sync: 0
  • Licence groups they span: 12
  • Destination objects: Account, Product, Price book entry, Commercient Acumatica Customer Managed Custom Object, Commercient Acumatica Sales Invoice Managed Custom Object, Commercient Acumatica Sales Invoice Detail Managed Custom Object, Commercient Acumatica Sales Order Managed Custom Object, Commercient Acumatica Sales Order Details Managed Custom Object, Commercient Stock Item Managed Custom Object, Commercient Acumatica Contact Managed Custom Object, Commercient Acumatica Employee Managed Custom Object, Contact, Acumatica item warehouse (custom object), Commercient Account Matching Managed Custom Object, Quote, Commercient Acumatica Payment Detail Managed Custom Object, Commercient Contact Matching Managed Custom Object, Opportunity, Acumatica customer credit card (custom object), Commercient Acumatica Payment Managed Custom Object and 16 more
  • Object display names: Account, Acumatica Cloud Invoice detail, Acumatica Cloud Invoice header, Acumatica Cloud Customer, Acumatica Cloud Item Master, Product, Acumatica Cloud Sales order, Acumatica Cloud Sales order detail, Update Standard Pricebook, Acumatica Cloud Address, Create Standard Price Book, Sync Item to product lookup, 48 more and 2 further templates
  • Template groups: Account, Product, Invoice, Sales order, CRM Quote and Line, Customer Multi Ship Addresses, CRM Opportunity and Line

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/acumatica-cloud.

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 Acumatica Cloud → 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/acumatica-cloud, 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.