Sage 100 2014 to Salesforce (CRMPro)

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

CRMPro → Salesforce — Sage 100 2014: 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-2014 (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

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, Contact, Commercient AR Customer Managed Custom Object, Commercient Salesperson Managed Custom Object	customers, shipping addresses, customer contacts, salespeople
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 Order and Line	ERP AR customer contact, sales order header, sales order detail data becomes Order, Order product in Salesforce. New records are created and existing ones updated; none are deleted.	Order, Order product	sales order headers, customer contacts, 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
Invoice	Both 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 Invoice History Header Managed Custom Object, Commercient Invoice History Detail Managed Custom Object	invoice history headers, customers, open invoices, salespeople, invoice history lines
Sales order	Commercient 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 Sales Order Header Managed Custom Object, Commercient Sales Order Line Managed Custom Object, Commercient Sales Order History Header Managed Custom Object, Commercient Sales Order History Line Managed Custom Object	sales order headers, customers, sales order lines, sales order history headers, sales order history lines

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 name	Destination object	Matching key	Run sequence
GET USER	users	—	0
Sales Person	Commercient Salesperson Managed Custom Object	Commercient external key	1
Account	Account	Commercient AR customer code	2
Contact	Contact	Commercient external key	3
Customer	Commercient AR Customer Managed Custom Object	Commercient external key	3
Address	Commercient Ship-To Address Managed Custom Object	Commercient external key	4
Account customer lookup	Account	Commercient AR customer code	5
Sales order	Commercient Sales Order Header Managed Custom Object	Commercient sales order number	8
Sales order line	Commercient Sales Order Line Managed Custom Object	Commercient external key	9
Sales order History Header	Commercient Sales Order History Header Managed Custom Object	Commercient external key	10
Sales order History Line	Commercient Sales Order History Line Managed Custom Object	Commercient external key	11
Invoice Header	Commercient Invoice History Header Managed Custom Object	Commercient external key	12
Invoice Details	Commercient Invoice History Detail Managed Custom Object	Commercient external key	13
Opportunity Header	Opportunity	External key (custom field)	21
Opportunity Line	Opportunity line item	External key (custom field)	22
Quote header	Quote	External key (custom field)	23
Quote line	Quote line item	External key (custom field)	24
Standard Order	Order	External key (custom field)	45
Standard order line	Order product	External key (custom field)	46
Standard Order Update	Order	External key (custom field)	47
Standard order line update	Order product	External key (custom field)	48

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.

View	Change detection	Source tables
salesperson feed	insert + update	salespeople
account feed	insert only	customers, shipping addresses
contact feed	insert only	customer contacts
customer feed	insert + update	customers
shipping address feed	insert + update	shipping addresses
customer account lookup feed	insert + update	customers
sales order feed	insert + update	sales order headers, customers
sales order line feed	insert + update	sales order lines, sales order headers
sales order history feed	insert + update	sales order history headers, customers
sales order history line feed	insert + update	sales order history lines, sales order history headers, customers
invoice feed	insert + update	invoice history headers, customers, open invoices, salespeople
invoice line feed	insert + update	invoice history lines, invoice history headers, items
opportunity feed	insert + update	sales order headers
opportunity line feed	insert only	sales order lines
quote feed	insert + update	sales order headers
quote line feed	insert only	sales order lines, sales order headers
standard order feed	insert + update	sales order headers, customer contacts
standard order line feed	insert + update	sales order lines
standard order feed (changes)	insert + update	sales order headers, customer contacts
standard order line feed (changes)	insert + update	sales order lines

4. Order of work

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

0 — GET USER
1 — Sales Person
2 — Account
3 — Contact, Customer
4 — Address
5 — Account customer lookup
8 — Sales order
9 — Sales order line
10 — Sales order History Header
11 — Sales order History Line
12 — Invoice Header
13 — Invoice Details
21 — Opportunity Header
22 — Opportunity Line
23 — Quote header
24 — Quote line
45 — Standard Order
46 — Standard order line
47 — Standard Order Update
48 — Standard order line update

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.

customer account lookup feed reads customer sync output
account feed reads user sync output
contact feed reads customer sync output, account sync output
opportunity feed reads customer sync output, account sync output, sales order sync output (generic name), salesperson sync output (generic name); no template in this set writes sales order sync output (generic name)
opportunity line feed reads opportunity sync output (generic name), product sync output, price book sync output; no template in this set writes product sync output, price book sync output
standard order feed reads account sync output, contact sync output, opportunity sync output (generic name), quote sync output (generic name)
standard order line feed reads standard order sync output, product sync output, price book sync output, quote line sync output (generic name); no template in this set writes product sync output, price book sync output
standard order feed (changes) reads account sync output, contact sync output, opportunity sync output (generic name), quote sync output (generic name)
standard order line feed (changes) reads standard order sync output, product sync output, price book sync output, quote line sync output (generic name); no template in this set writes product sync output, price book sync output
quote feed reads customer sync output, account sync output, opportunity sync output (generic name), terms sync output, salesperson sync output (generic name); no template in this set writes terms sync output
quote line feed reads quote sync output (generic name), product sync output, price book sync output; no template in this set writes product sync output, price book sync output
customer feed reads account sync output, salesperson sync output (generic name)
shipping address feed reads account sync output, customer sync output
invoice feed reads customer sync output, account sync output, salesperson sync output (generic name)
invoice line feed reads invoice sync output, inventory item sync output; no template in this set writes inventory item sync output
sales order feed reads customer sync output, account sync output, salesperson sync output (generic name)
sales order line feed reads sales order sync output, inventory item sync output; no template in this set writes inventory item sync output
sales order history feed reads customer sync output, account sync output
sales order history line feed reads sales order history sync output, inventory item sync output; no template in this set writes inventory item sync output

5. Field mapping

Each template carries its intended mapping in field mapping.

Template	Object	Mapped fields	First ERP → Salesforce pairs
Sales Person	Commercient Salesperson Managed Custom Object	24	Salesperson division,Salesperson number → Commercient external key, Salesperson name → Name, Salesperson division → Salesperson division, Salesperson number → Salesperson number, Address line 1 → Address line 1
Address	Commercient Ship-To Address Managed Custom Object	33	AR division number, Customer number, Ship-to code → Commercient external key, AR division number, Customer number, Ship-to code → Name, AR division number, Customer number → Account, AR division number, Customer number → Commercient Sage 100 customer records, AR division number → AR division number
Account customer lookup	Account	2	AR division number, Customer number → Commercient AR customer code, the linked Salesforce record → Commercient Sage customer record
Sales order line	Commercient Sales Order Line Managed Custom Object	64	Sales order number, Line key → Commercient external key, the linked Salesforce record → Commercient Sage 100 open sales order (related record), Sales order number, Line key → Name, Sales order number → Commercient sales order number, Line key → Commercient line key
Sales order History Header	Commercient Sales Order History Header Managed Custom Object	66	Sales order number → Commercient external key, Sales order number → Name, the linked Salesforce record → Account, the linked Salesforce record → Customer, Order status → Order status
Sales order History Line	Commercient Sales Order History Line Managed Custom Object	50	Sales order number, Sequence number → Commercient external key, Sales order number, Sequence number → Name, the linked Salesforce record → Commercient sales order history header, Sequence number → Commercient sequence number, Line key → Commercient line key
Invoice Header	Commercient Invoice History Header Managed Custom Object	88	Invoice number, Header sequence number → Commercient external key, Invoice number, Header sequence number → Name, AR division number, Customer number → Account, AR division number, Customer number → Sage 100 customer record (custom field), Salesperson division, Salesperson number → Salesperson
Invoice Details	Commercient Invoice History Detail Managed Custom Object	60	Invoice number, Header sequence number, Detail sequence number → Commercient external key, Invoice number, Header sequence number, Detail sequence number → Commercient name, the linked Salesforce record → Commercient Sage 100 invoice (related record), the linked Salesforce record → Commercient Sage 100 item (related record), Invoice number → Commercient invoice number
Opportunity Header	Opportunity	7	Sales order number → External key (custom field), Sales order number → Name, the linked Salesforce record → account lookup, Taxable amount → Amount, the linked Salesforce record → price book lookup
Opportunity Line	Opportunity line item	6	Sales order number, Line key → External key (custom field), Quantity ordered → Quantity (custom field), Unit price → Unit price, Item description → Description, Sales order number → Opportunity
Quote header	Quote	22	Sales order number → External key (custom field), Sales order number → Name, Sales order number → Opportunity, Salesperson division,Salesperson number → Sage 100 salesperson object (custom), Terms code → Terms
Quote line	Quote line item	8	Sales order number, Line key → External key (custom field), Sales order number → Quote, Item code → product lookup, Item code → price book entry lookup, Promise date → Service date
Standard Order	Order	27	AR division number,Sales order number → External key (custom field), Customer number → account lookup, Contact code → bill to contact lookup, Contact code → ship to contact lookup, Sales order number → Opportunity
Standard order line	Order product	12	Sales order number, Line key → External key (custom field), Sales order number → Order identifier, Item code → product lookup, Item code → price book entry lookup, Sales order number, Line key → quote line item lookup
Standard Order Update	Order	26	AR division number,Sales order number → External key (custom field), Customer number → account lookup, Contact code → bill to contact lookup, Contact code → ship to contact lookup, Sales order number → Opportunity
Standard order line update	Order product	10	Sales order number, Line key → External key (custom field), Sales order number → Order identifier, Sales order number, Line key → quote line item lookup, Item description → Description, Expiry date → End date

6. Community templates

The catalogue carries 16 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: 16
Default operations: insert on 16, update on 16, delete on 16
Marked as circular sync: 0
Licence groups they span: 9
Destination objects: Account, Commercient AR Customer Managed Custom Object, Commercient Invoice History Detail Managed Custom Object, Commercient Invoice History Header Managed Custom Object, Commercient Sales Order History Line Managed Custom Object, Commercient Sales Order History Header Managed Custom Object, Commercient Salesperson Managed Custom Object, Commercient Sales Order Line Managed Custom Object, Commercient Sales Order Header Managed Custom Object, Commercient Ship-To Address Managed Custom Object, Contact, Opportunity, Opportunity line item, Quote, Quote line item
Object display names: Account, Account customer lookup, Address, Contact, Customer, Invoice Details, Invoice Header, Opportunity Header, Opportunity Line, Quote header, Quote line, Sales Person and 4 more
Template groups: Account, Sales order, CRM Opportunity and Line, CRM Quote and Line, 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/sage-100-2014.

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 2014 → 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-2014, 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.