Source ERP · 78 of 105

CRMPro → Salesforce — Sage 100 (US): 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/sage-100-us". 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/sage-100-us-salesforce/.

CRMPro → Salesforce — Sage 100 (US): 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/sage-100-us (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 users to Salesforce. New records are created, existing ones updated, and records removed in the ERP are deleted.users—
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 and existing ones updated; none are deleted.Account, Commercient Terms Code Managed Custom Object, Contact, Commercient AR Customer Managed Custom Object, Commercient Salesperson Managed Custom Objectcustomers, shipping addresses, terms codes, customer contacts, salespeople
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 Payment History Managed Custom Objectpayment history
CRM Opportunity and LineERP sales order header, 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 order headers, sales order lines
CRM Quote and LineERP sales order header, 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 order headers, sales order lines
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 Ship-To Address Managed Custom Objectshipping addresses
ProductThe templates push Commercient Inventory Item Managed Custom Object, Commercient Item Warehouse Managed Custom Object, Commercient Item Transaction History Managed Custom Object to Salesforce. New records are created and existing ones updated; none are deleted.Commercient Inventory Item Managed Custom Object, Commercient Item Warehouse Managed Custom Object, Commercient Item Transaction History Managed Custom Object, Productitems, extended item descriptions, process configuration, item warehouse quantities, item transaction history
Invoice History HeadersThe Invoices from the ERP invoice module are synchronized to the Commercient Invoice Header (MCO) object in CRM. Customer service and sales people can visualize the status of the Invoice such as open, closed, as well as the balance remaining and the due date. New records are created and existing ones updated; none are deleted.Commercient Invoice History Header Managed Custom Objectinvoice history headers
Open AR Invoice HeaderThe detail lines on open invoices are visible too so that you are aware of what items you are awaiting payment on from your customer. New records are created and existing ones updated; none are deleted.Commercient Invoice History Detail Managed Custom Object, Commercient Open Invoice Managed Custom Objectinvoice history lines, invoice history headers, invoice headers
PricebookThe templates push Price book entry to Salesforce. New records are created and existing ones updated; none are deleted.Price book entryitems
Sales orderThe templates push Commercient Sales Order Line Managed Custom Object, Commercient Sales Order History Line Managed Custom Object, Commercient Sales Order Header Managed Custom Object to Salesforce. New records are created and existing ones updated; none are deleted.Commercient Sales Order Line Managed Custom Object, Commercient Sales Order History Line Managed Custom Object, Commercient Sales Order Header Managed Custom Object, Commercient Sales Order History Header Managed Custom Objectsales order lines, sales order headers, sales order history lines, sales order history headers

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
GET USERusers—0
AR termsCommercient Terms Code Managed Custom ObjectCommercient external key1
Sales PersonCommercient Salesperson Managed Custom ObjectCommercient external key2
AccountAccountCommercient AR customer code3
CustomerCommercient AR Customer Managed Custom ObjectCommercient external key4
Ship to addressCommercient Ship-To Address Managed Custom ObjectCommercient external key5
Account customer lookupAccountCommercient AR customer code6
Inventory itemCommercient Inventory Item Managed Custom ObjectCommercient external keys7
ProductProductCommercient external key (earlier package)8
Item product Reverse lookupCommercient Inventory Item Managed Custom ObjectCommercient external keys9
Sales orderCommercient Sales Order Header Managed Custom ObjectCommercient sales order number10
Sales order lineCommercient Sales Order Line Managed Custom ObjectCommercient external key11
Sales order History HeaderCommercient Sales Order History Header Managed Custom ObjectCommercient external key12
Sales order History LineCommercient Sales Order History Line Managed Custom ObjectCommercient external key13
Open InvoiceCommercient Open Invoice Managed Custom ObjectCommercient external key14
Invoice HeaderCommercient Invoice History Header Managed Custom ObjectCommercient external key15
Invoice DetailsCommercient Invoice History Detail Managed Custom ObjectCommercient external key16
Transcation Payment HistoryCommercient Payment History Managed Custom ObjectCommercient external key17
Item WarehouseCommercient Item Warehouse Managed Custom ObjectCommercient external key18
Create Standard Price BookPrice book entryExternal key (custom field)19
Update Standard Price BookPrice book entryExternal key (custom field)20
ContactContactCommercient external key21
Item Transaction HistoryCommercient Item Transaction History Managed Custom ObjectCommercient external key22
Opportunity HeaderOpportunityExternal key (custom field)23
Opportunity LineOpportunity line itemExternal key (custom field)24
Quote headerQuoteExternal key (custom field)25
Quote lineQuote line itemExternal key (custom field)26

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
terms code feedinsert + updateterms codes
salesperson feedinsert + updatesalespeople
account feedinsert + updatecustomers, shipping addresses
customer feedinsert onlycustomers
shipping address feedinsert + updateshipping addresses
customer account lookup feedinsert + updatecustomers
inventory item feedinsert + updateitems, extended item descriptions
product feedinsert + updateitems
product item reverse lookup feedinsert + updateitems, process configuration
sales order feedinsert + updatesales order headers
sales order line feedinsert + updatesales order lines, sales order headers
sales order history feedinsert + updatesales order history headers
sales order history line feedinsert + updatesales order history lines, sales order history headers
open invoice feedinsert + updateinvoice headers
invoice history feedinsert + updateinvoice history headers
invoice history line feedinsert + updateinvoice history lines, invoice history headers
payment history feedinsert + updatepayment history
item warehouse feedinsert + updateitem warehouse quantities
price book feed (new entries)insert onlyitems
price book feed (changes)insert onlyitems
contact feedinsert + updatecustomer contacts
item transaction history feedinsert + updateitem transaction history
Sage 100 US opportunity feedinsert + updatesales order headers
quote line feedinsert onlysales order lines, sales order headers
quote feedinsert + updatesales order headers
quote line feedinsert onlysales order lines, sales order headers

4. Order of work

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

  • 0 — GET USER
  • 1 — AR terms
  • 2 — Sales Person
  • 3 — Account
  • 4 — Customer
  • 5 — Ship to address
  • 6 — Account customer lookup
  • 7 — Inventory item
  • 8 — Product
  • 9 — Item product Reverse lookup
  • 10 — Sales order
  • 11 — Sales order line
  • 12 — Sales order History Header
  • 13 — Sales order History Line
  • 14 — Open Invoice
  • 15 — Invoice Header
  • 16 — Invoice Details
  • 17 — Transcation Payment History
  • 18 — Item Warehouse
  • 19 — Create Standard Price Book
  • 20 — Update Standard Price Book
  • 21 — Contact
  • 22 — Item Transaction History
  • 23 — Opportunity Header
  • 24 — Opportunity Line
  • 25 — Quote header
  • 26 — Quote line

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
  • customer account lookup feed reads customer sync output
  • payment history feed reads account sync output, customer sync output, invoice history sync output
  • contact feed reads account sync output, customer sync output
  • Sage 100 US opportunity feed reads customer sync output, account sync output, salesperson sync output
  • quote line feed reads quote sync output (generic name), product sync output, quote line sync output (generic name)
  • quote feed reads customer sync output, account sync output, opportunity sync output (generic name), salesperson sync output
  • quote line feed reads quote sync output (generic name), product sync output
  • customer feed reads account sync output, salesperson sync output
  • shipping address feed reads account sync output, customer sync output, salesperson sync output
  • product item reverse lookup feed reads product sync output
  • item warehouse feed reads product sync output, inventory item sync output
  • item transaction history feed reads account sync output, customer sync output, shipping address sync output, product sync output, inventory item sync output
  • invoice history feed reads account sync output, customer sync output, salesperson sync output
  • invoice history line feed reads invoice history sync output, account sync output, customer sync output, salesperson sync output, inventory item sync output
  • open invoice feed reads account sync output, customer sync output, salesperson sync output
  • price book feed (new entries) reads product sync output
  • price book feed (changes) reads product sync output
  • product feed reads inventory item sync output
  • sales order line feed reads sales order sync output, account sync output, customer sync output, salesperson sync output
  • sales order history line feed reads sales order history sync output, inventory item sync output, account sync output, customer sync output, salesperson sync output
  • sales order feed reads account sync output, customer sync output, salesperson sync output
  • sales order history feed reads account sync output, customer sync output, salesperson sync output, Sage 100 UK account sync output; no template in this set writes Sage 100 UK account sync output

5. Field mapping

Each template carries its intended mapping in field mapping.

TemplateObjectMapped fieldsFirst ERP → Salesforce pairs
AR termsCommercient Terms Code Managed Custom Object2Terms code → Commercient external key, Terms code description → Name
Sales PersonCommercient Salesperson Managed Custom Object2Salesperson division, Salesperson number → Commercient external key, Salesperson name → Name
AccountAccount15AR division number, Customer number → Commercient AR customer code, Customer name, Shipping name → Name, Salesperson division, Salesperson number → Commercient Salesperson Managed Custom Object, Telephone number → Phone, Address line 1, Address line 2, Address line 3 → Billing street
CustomerCommercient AR Customer Managed Custom Object96AR division number, Customer number → Commercient external key, Customer name → Name, the linked Salesforce record → Account, the linked Salesforce record → Salesperson, AR division number → AR division number
Ship to addressCommercient Ship-To Address Managed Custom Object5AR division number, Customer number, returned shipping address code → Commercient external key, Shipping name → Name, AR division number, Customer number → Account, AR division number, Customer number → Sage 100 customer records (custom field), Salesperson number → Salesperson
Account customer lookupAccount2AR division number, Customer number → Commercient AR customer code, the linked Salesforce record → Commercient Sage customer record
Inventory itemCommercient Inventory Item Managed Custom Object2Item code → Commercient external keys, Item code → Name
ProductProduct6Item code → Commercient external key (earlier package), Item code → Name, Item code → Product code, Item description → Description, Inactive item → Active
Item product Reverse lookupCommercient Inventory Item Managed Custom Object2Item code → Commercient external keys, the linked Salesforce record → Commercient product
Sales orderCommercient Sales Order Header Managed Custom Object112AR division number, returned sales order number → Commercient sales order number, returned sales order number → Name, AR division number, Customer number → Account, AR division number, Customer number → Sage 100 customer record (custom field), Salesperson division, Salesperson number → Salesperson
Sales order lineCommercient Sales Order Line Managed Custom Object4returned sales order number, Line key → Commercient external key, the linked Salesforce record → Commercient Sage 100 open sales order (related record), the linked Salesforce record → Account, returned sales order number, Line key → Name
Sales order History HeaderCommercient Sales Order History Header Managed Custom Object97AR division number,returned sales order number → Commercient external key, returned sales order number → Name, AR division number,Customer number → Account, AR division number,Customer number → Customer, Salesperson division,Salesperson number → Sage 100 salesperson (custom field)
Sales order History LineCommercient Sales Order History Line Managed Custom Object4returned sales order number, Sequence number → Commercient external key, returned sales order number, Sequence number → Commercient name, the linked Salesforce record → Commercient sales order history header, the linked Salesforce record → Commercient inventory item (related record)
Open InvoiceCommercient Open Invoice Managed Custom Object5Invoice number,Invoice type → Commercient external key, Invoice number,Invoice type → Name, AR division number,Customer number → Account, AR division number,Customer number → Sage 100 customer records (custom field), Salesperson division,Salesperson number → Sage 100 salesperson (custom field)
Invoice HeaderCommercient Invoice History Header Managed Custom Object5Invoice number, Header sequence number → Commercient external key, Invoice number → Name, AR division number, Customer number → Account, AR division number, Customer number → Sage 100 customer records (custom field), Salesperson division, Salesperson number → Sage 100 salesperson (custom field)
Invoice DetailsCommercient Invoice History Detail Managed Custom Object6Invoice number, Header sequence number, Detail sequence number → Commercient external key, Invoice number, Detail sequence number → Name, AR division number, Customer number → Account, AR division number, Customer number → Sage 100 customer records (custom field), Invoice number, Header sequence number → Invoice
Transcation Payment HistoryCommercient Payment History Managed Custom Object5Invoice number → Name, the linked Salesforce record → Account, the linked Salesforce record → Sage 100 customer record (custom field), the linked Salesforce record → Invoice
Item WarehouseCommercient Item Warehouse Managed Custom Object4Item code, Warehouse code → Commercient external key, Item code, Warehouse code → Name, the linked Salesforce record → Commercient product, the linked Salesforce record → Commercient inventory item
Create Standard Price BookPrice book entry5Item code → External key (custom field), Standard unit price → Unit price, the linked Salesforce record → price book lookup, the linked Salesforce record → product lookup
Update Standard Price BookPrice book entry3Item code → External key (custom field), Standard unit price → Unit price
ContactContact13AR division number, Customer number, Contact code → Commercient external key, the linked Salesforce record → account lookup, Contact name → Family name, Email address → Email, Telephone number 1 → Phone
Item Transaction HistoryCommercient Item Transaction History Managed Custom Object7AR division number,Customer number → Account (custom field), AR division number,Customer number → Sage 100 customer records (custom field), AR division number,Customer number,returned shipping address code → Sage 100 shipping address (custom field), Item code → Product, Item code → Sage 100 inventory item (custom field)
Opportunity HeaderOpportunity7returned sales order number → External key (custom field), returned sales order number → Name, the linked Salesforce record → account lookup, Taxable amount → Amount, the linked Salesforce record → price book lookup
Opportunity LineOpportunity line item8returned sales order number, Line key → External key (custom field), the linked Salesforce record → Quote, the linked Salesforce record → product lookup, the linked Salesforce record → price book entry lookup, Promise date → Service date
Quote headerQuote22returned sales order number → External key (custom field), returned sales order number → Name, returned sales order number → Opportunity, Salesperson division,Salesperson number → Sage 100 salesperson object (custom), Bill to name → Billing name
Quote lineQuote line item8returned sales order number, Line key → External key (custom field), the linked Salesforce record → Quote, the linked Salesforce record → product lookup, the linked Salesforce record → price book entry lookup, Promise date → Service date

6. Community templates

The catalogue carries 1310 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: 1310
  • Default operations: insert on 1310, update on 1310, delete on 1310
  • Marked as circular sync: 4
  • Licence groups they span: 17
  • Destination objects: Account, Commercient Inventory Item Managed Custom Object, Price book entry, Commercient AR Customer Managed Custom Object, Product, Commercient Sales Order Header Managed Custom Object, Commercient Invoice History Detail Managed Custom Object, Commercient Invoice History Header Managed Custom Object, Commercient Sales Order Line Managed Custom Object, Commercient Ship-To Address Managed Custom Object, Commercient Salesperson Managed Custom Object, Commercient Sales Order History Header Managed Custom Object, Commercient Item Warehouse Managed Custom Object, Commercient Sales Order History Line Managed Custom Object, Commercient Terms Code Managed Custom Object, Commercient Open Invoice Managed Custom Object, Contact, Commercient Payment History Managed Custom Object, account, 72 more and 48 custom objects
  • Object display names: Account, Customer, Account customer lookup, Item product Reverse lookup, Product, Sales order, Sales order line, Sales Person, Sales order History Header, Invoice Details, Invoice Header, Ship to address, 144 more and 55 further templates
  • Template groups: Account, Product, Sales order, Invoice, CRM Quote and Line, CRM Opportunity and Line, Customer Multi Ship Addresses, Invoice History Headers, Purchase Order, Pricebook, CRM Order 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/sage-100-us.

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 100 (US) → 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/sage-100-us, 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.