Integration
Sage 100 (US) and Salesforce
Sage 100 (US) to Salesforce, and changes in Salesforce back to Sage 100 (US). Both directions are separate sync products, configured independently, and this page shows what the shipped catalogue sets up for this pair.
- Phase 1 · forward sync
- Phase 2 · write-back
In plain wordsRecords from Sage 100 (US) are pushed into Salesforce, and changes made in Salesforce are carried back to Sage 100 (US). Each direction is its own sync with its own configuration.
This page documents what the shipped catalogue sets up. For the commercial overview of the same pair — editions, licensing and how to buy it — Commercient publishes Sage 100 (US) to Salesforce integration on commercient.com .
Phase 1 — Sage 100 (US) to Salesforce
What you getRecords from Sage 100 (US) become users, accounts, Commercient Terms Code Managed Custom Object, contacts, Commercient AR Customer Managed Custom Object, Commercient Salesperson Managed Custom Object, Commercient Payment History Managed Custom Object, Opportunity, Opportunity line item, Quote, Quote line item, Commercient Ship-To Address Managed Custom Object, Commercient Inventory Item Managed Custom Object, Commercient Item Warehouse Managed Custom Object, Commercient Item Transaction History Managed Custom Object, products, Commercient Invoice History Header Managed Custom Object, Commercient Invoice History Detail Managed Custom Object, Commercient Open Invoice Managed Custom Object, Price book entry, 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 Object in Salesforce. New records are created and existing ones updated.
| Group | Business outcome | Objects | Source tables and views |
|---|---|---|---|
| GET USER | The templates push users to Salesforce. New records are created, existing ones updated, and records removed in the ERP are deleted. | users | — |
| Account | In 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 Object | customers, shipping addresses, terms codes, customer contacts, salespeople |
| AR Invoice Payments | Commercient 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 Object | payment history |
| CRM Opportunity and Line | ERP 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 item | sales order headers, sales order lines |
| CRM Quote and Line | ERP 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 item | sales order headers, sales order lines |
| Customer Multi Ship Addresses | If 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 Object | shipping addresses |
| Product | The 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, Product | items, extended item descriptions, process configuration, item warehouse quantities, item transaction history |
| Invoice History Headers | The 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 Object | invoice history headers |
| Open AR Invoice Header | The 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 Object | invoice history lines, invoice history headers, invoice headers |
| Pricebook | The templates push Price book entry to Salesforce. New records are created and existing ones updated; none are deleted. | Price book entry | items |
| Sales order | The 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 Object | sales order lines, sales order headers, sales order history lines, sales order history headers |
Destination objects
- users
- Account
- Commercient Terms Code Managed Custom Object
- Contact
- Commercient AR Customer Managed Custom Object
- Commercient Salesperson Managed Custom Object
- Commercient Payment History Managed Custom Object
- Opportunity
- Opportunity line item
- Quote
- Quote line item
- Commercient Ship-To Address Managed Custom Object
- Commercient Inventory Item Managed Custom Object
- Commercient Item Warehouse Managed Custom Object
- Commercient Item Transaction History Managed Custom Object
- Product
- Commercient Invoice History Header Managed Custom Object
- Commercient Invoice History Detail Managed Custom Object
- Commercient Open Invoice Managed Custom Object
- Price book entry
- 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 Object
Phase 2 — Salesforce back to Sage 100 (US)
What you getChanges made in Salesforce to Opportunity, Order, Quote, Sales order, AR invoice, Invoice, Work order, Sales Order, accounts, contacts, Customer, products, Common information item, Purchase Order, Shipping address, Return merchandise authorization, Service Order, Vendor, Item, AP invoice are carried back to Sage 100 (US).
| Process | What it delivers | Source → destination | Templates | Operations |
|---|---|---|---|---|
| Create New Sales Order | Salesforce Opportunity to Sage 100 Sales Order | Opportunity, Order, Quote → Order, Sales order | 6 | create / update |
| (unnamed) | Salesforce Opportunity To Update Sage 100 AR Invoice | Opportunity, Opportunity, Quote → AR invoice, Invoice, Sales order | 6 | create / update |
| Create New Sales Invoice | Salesforce Work order To Sage 100 Invoice | Work order, Opportunity, Order → Invoice | 3 | create |
| Delete Sales Invoice | Salesforce Order to Sage 100 Invoice - Delete Invoice | Order, Quote, Opportunity → Invoice | 3 | delete |
| Delete Sales Order | Salesforce Order to Sage 100 Sales Order - Delete Sales Order | Order, Quote, Opportunity → Sales Order | 3 | delete |
| Update Sales Order Header Only | Update Sales order Header from Sage 100 Opportunity | Opportunity, Order, Quote → Sales order, Sales order | 3 | update |
| Create and Update Contact | Sage 100 Account(child) To Sage 100 Contact | Account, Contact → Contact, Contact | 2 | create |
| Create New Customer | Salesforce Account To Update Sage 100 Customer | Account → Customer | 2 | create / update |
| Create new Product | Salesforce Product To Update Product Sage 100 | Product → Common information item | 2 | create / update |
| Create Purchase Order | Salesforce Order to Sage 100 Purchase Order | Order → Purchase Order | 2 | create / update |
| Create New Ship To Address | Salesforce Account(shipping Address) To Sage 100 Shipping address | Account → Shipping address | 1 | create |
| Create Return merchandise authorization | Salesforce Order to Sage 100 Return merchandise authorization | Order → Return merchandise authorization | 1 | create |
| Create Service Order | Salesforce Work order to Sage 100 Service Order | Work order → Service Order | 1 | create |
| Create Vendor | Salesforce Account to Sage 100 Vendor | Account → Vendor | 1 | create |
| Delete Product | Salesforce Product to Sage 100 Item - Delete Item | Product → Item | 1 | delete |
| Delete Purchase Order | Salesforce Order to Sage 100 Purchase Order - Delete Purchase Order | Order → Purchase Order | 1 | delete |
| Delete Ship To Address | Salesforce Account to Sage 100 Ship To Address - Delete Ship To Address | Account → Shipping address | 1 | delete |
| (unnamed) | Salesforce Order to Sage 100 AP Invoice | Order → AP invoice | 1 | create |
| Update Ship To Address | Salesforce Account to Sage 100 Ship To Address - Update Ship To Address | Account → Shipping address | 1 | update |
Objects moved
- Opportunity
- Order
- Quote
- Sales order
- AR invoice
- Invoice
- Work order
- Sales Order
- Account
- Contact
- Customer
- Product
- Common information item
- Purchase Order
- Shipping address
- Return merchandise authorization
- Service Order
- Vendor
- Item
- AP invoice
Setting up Sage 100 (US) and Salesforce from the CLI
One wizard stands the tenant up, and it is the same five steps for every pair: register, capture the server IP, connect the CRM, declare the ERP connector, then import and enable the sync processes. What changes between pairs is the CRM’s connection mode and the ERP’s connector type.
1. Register the tenant
Registration creates the account, emails a verification link, and — once the Data Lake is seeded — prints a once-only bootstrap API key valid for seven days. The three consent flags are the registrant’s own decision, and the server refuses start without all three.
# which instance types sign-up accepts - run this first and use Sage 100 (US)'s code below
$ dlake register erps
# the three consent flags are the registrant’s decision - ask before passing them
$ dlake register start --generate-password \
$ --email <email> --company "<Company Name>" --phone <tel> \
$ --instance-type <code from dlake register erps> \
$ --consent-crm-backup --consent-erp-backup --consent-phone
# after the human clicks the verification link: watch for the seed and catch the key
$ dlake register status --watch
# the bootstrap key expires in 7 days - mint a durable one while it is still valid
$ dlake admin create_api_key --keyName "<tenant>-setup" --expirationDays 90
2. Connect Salesforce and declare Sage 100 (US)
Steps 3 to 5 of the wizard are admin-plane tools, they are safe to re-run, and the server enforces their order — attempt the CRM step before the server IP is captured and it answers 409 naming the step you skipped.
# the authoritative answer to where a registration got to - first call when resuming
$ dlake admin registration_state
# step 3: record the server IP (a prerequisite for the CRM step)
$ dlake admin registration_capture_server_ip --ipAddress <ip>
# step 4: the catalog lists every CRM with its authMode and the fields it needs
$ dlake admin registration_crm_catalog
$ dlake admin registration_crm_select --crmName Salesforce
# an OAuth CRM: the catalog’s callbackMode says which leg this one takes
$ dlake registration oauth --crm Salesforce
# this provider’s flow ends in a PIN, emailed by the complete call itself; the verb reads it hidden (or --pin-stdin)
$ dlake registration pin --crm Salesforce
# the connection is incomplete without this call, however healthy the rest looks
$ dlake registration action --crm Salesforce --action SalesforceSetup
$ dlake admin registration_crm_finalize
# step 5: the catalog lists the connector types and the fields each one needs
$ dlake admin registration_connector_catalog
$ dlake admin registration_connector_submit \
$ --connectorType <type from the catalog> --erpName <Sage 100 (US) code> --fields @fields.json
$ dlake admin registration_connector_provision
$ dlake admin registration_provisioning_status
3. Review and enable the Phase 1 processes
The shipped templates listed above are what crmpro_apply_template imports. Every one of them imports its process inactive, so an imported process does nothing until an operator activates it — read the process and its field mapping first, because an object with no mapped fields pushes nothing and records no error.
# the default-template catalog, and the mapping each template carries
$ dlake admin crmpro_templates --profile <tenant>
# what exists on the tenant now, and the master sync flag
$ dlake admin crmpro_list_processes --profile <tenant>
$ dlake admin crmpro_sync_status --profile <tenant>
# read a process and its field mapping BEFORE activating it
$ dlake admin crmpro_get_process --profile <tenant> --recordId <id>
$ dlake admin crmpro_field_mapping --profile <tenant> --recordId <id>
# turn the forward sync on
$ dlake admin crmpro_set_sync_enabled --profile <tenant> --enabled true
Processes run in a fixed order, and that order is a dependency order: a process that depends on another’s records sees them only once that process has run, so a parent flows on one run and its children on the next. The full order for this pair is on the Phase 1 page.
The wizard in full, including resuming a setup days later: Setting up an integration with dlake · Registering a new Data Lake · CRMPro (forward sync).
0Source on GitHub
This page is generated from the skill pages in the dlake CLI repository. Those pages are the authority; if they disagree with anything here, they are right.
Phase 1 source
dlake-crmpro-salesforce/erps/sage-100-us.md
Phase 2 source
dlake-txdownloaderpro-salesforce/erps/sage-100-us.md
Phase 1, in full
The complete upstream page for Sage 100 (US) into Salesforce, on this site.
Read the full pagePhase 2, in full
The complete upstream page for Salesforce back into Sage 100 (US), on this site.
Read the full pageSage 100 (US) and Salesforce: common questions
Which way does data move between Sage 100 (US) and Salesforce?
Both ways, as two separate syncs. Phase 1 is CRMPro, the forward sync that pushes Sage 100 (US) records into Salesforce. Phase 2 is TxDownloaderPro, the write-back that carries changes made in Salesforce back to Sage 100 (US). They are configured independently, and a tenant can run either on its own.
What do Phase 1 and Phase 2 mean?
They are the two sync products the on-premises agent can run. Phase 1 is CommercientCRMPro, product 11, the forward sync from the source system into the CRM. Phase 2 is CommercientTxDownloaderPro, product 22, the write-back in the other direction. Registering a product says what to run; the Phase 1 and Phase 2 configuration says what it runs on.
What does the forward sync into Salesforce actually create?
The shipped catalogue carries 11 template groups for this pair: GET USER, Account, AR Invoice Payments, CRM Opportunity and Line, CRM Quote and Line, Customer Multi Ship Addresses, Product, Invoice History Headers and 3 more. Each group sets up its own sync process, and the integration page says what each one delivers.
Which Salesforce objects does the forward sync write?
users, Account, Commercient Terms Code Managed Custom Object, Contact, Commercient AR Customer Managed Custom Object, Commercient Salesperson Managed Custom Object, Commercient Payment History Managed Custom Object, Opportunity and 16 more. Those are the kinds of Salesforce record the shipped templates write for a Sage 100 (US) source; nothing else is written unless you add templates of your own.
Does the forward sync delete anything in the CRM?
Each template group carries its own insert, update and delete flags, and the integration page lists what each group does. Read a process with dlake admin crmpro_get_process before activating it.
What does the write-back from Salesforce create in Sage 100 (US)?
The default set ships 19 processes for this pair: Create New Sales Order, (unnamed), Create New Sales Invoice, Delete Sales Invoice, Delete Sales Order, Update Sales Order Header Only, Create and Update Contact, Create New Customer and 11 more. Each one takes a saved query against Salesforce, an inbound mapping document, and writes the result into Sage 100 (US).
View moreShow less
Which objects does the write-back move?
Opportunity, Order, Quote, Sales order, AR invoice, Invoice, Work order, Sales Order and 12 more. Those are the kinds of Salesforce record the shipped processes carry back to Sage 100 (US).
What does "Phase 2 ready" mean?
It means the tenant has at least one TxDownloaderPro process. Creating a process with txdownloaderpro_create_process is what flips a customer to Phase 2 ready; registering the product alone does not, because registering says what to run and the configuration says what it runs on.
How do I see the write-back processes and whether they are failing?
dlake admin txdownloaderpro_list_processes returns every Phase 2 process with its 30-day unresolved-error count, which is the same grid the portal shows. txdownloaderpro_get_process returns one process in its edit shape, including the query and both mapping documents.
How do I stop the two directions looping?
dlake admin txdownloaderpro_circular_sync_check takes a process id and names the CRM objects that also have an active Phase 1 configuration. Those are the objects where a write-back can be picked up again by the forward sync, so check it before activating a process on this pair.
Can an AI agent set this up?
Yes, over the admin control plane or the CLI — the same tools either way. The crmpro_* and txdownloaderpro_* tools cover listing, reading, creating and updating processes. They need a full-scope key that belongs to a user holding the Admin role, and every write is audited.
Where is the authoritative source for this pair?
The skill pages in the dlake CLI repository, which is where this page is generated from. The forward sync page is linked at the foot of the integration page, and the same text is readable in the terminal with dlake skills show.
Related
Every ERP and CRM integration · CRMPro (forward sync) · TxDownloaderPro (writeback sync) · AI agents & MCP · Salesforce integrations on commercient.com
