Source ERP · 15 of 27

CRMPro → Zoho CRM — Sage 100 Contractor 2018: 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-zohocrm/erps/sage-100-contractor-2018". It extends the dlake-crmpro-zohocrm skill, which holds what is true whatever the source ERP. Both directions for this pair are summarised at /integrations/sage-100-contractor-2018-zoho-crm/.

CRMPro → Zoho CRM — Sage 100 Contractor 2018: 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-zohocrm/erps/sage-100-contractor-2018 (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-zohocrm is the destination skill this page is a child of, and the authority for the Zoho CRM 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
Sage Sales PersonThe templates push Commercient Sage 100 Contractor Salesperson object to Zoho CRM.Commercient Sage 100 Contractor Salesperson objectemployees
AccountsThe templates push Accounts to Zoho CRM.Accountsclients
Sage CustomerThe templates push Commercient Sage 100 Contractor Customer object to Zoho CRM.Commercient Sage 100 Contractor Customer objectclients
Sage JobThe templates push Commercient Sage 100 Contractor Job object to Zoho CRM.Commercient Sage 100 Contractor Job objectjobs
ProductsThe templates push Products to Zoho CRM.Productsparts
ContactsThe templates push Contacts to Zoho CRM.Contactsclient contacts
Sage PartsThe templates push Commercient Sage 100 Contractor Parts object to Zoho CRM.Commercient Sage 100 Contractor Parts objectparts
Sage Inventory HistoryThe templates push Commercient Sage 100 Contractor Inventory History object to Zoho CRM.Commercient Sage 100 Contractor Inventory History objectinventory history
Sage AR InvoiceThe templates push Commercient Sage 100 Contractor AR Invoice object to Zoho CRM.Commercient Sage 100 Contractor AR Invoice objectAR invoices, jobs
Sage AR invoice lineThe templates push Commercient Sage 100 Contractor AR Invoice Line object to Zoho CRM.Commercient Sage 100 Contractor AR Invoice Line objectAR invoice lines
Sage AR PaymentsThe templates push Commercient Sage 100 Contractor AR Payment object to Zoho CRM.Commercient Sage 100 Contractor AR Payment objectAR payments
QuoteThe templates push Quotes to Zoho CRM.Quotesservice invoice lines, parts, service invoices, jobs, clients, x
Sales orderThe templates push Sales orders to Zoho CRM.Sales ordersservice invoice lines, parts, service invoices, jobs, clients, x
InvoiceThe templates push Invoices to Zoho CRM.Invoicesservice invoice lines, parts, service invoices, jobs, clients, x
CRM OwnershipThe templates push users to Zoho CRM.users—

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
UsersusersCommercient external key column1
Sage Sales PersonCommercient Sage 100 Contractor Salesperson objectCommercient external key column2
AccountsAccountsCommercient AR customer code (Zoho field)3
Sage CustomerCommercient Sage 100 Contractor Customer objectCommercient external key column4
Sage JobCommercient Sage 100 Contractor Job objectCommercient external key column5
ProductsProductsCommercient external key column6
ContactsContactsCommercient external key column7
Sage PartsCommercient Sage 100 Contractor Parts objectCommercient external key column8
Sage Inventory HistoryCommercient Sage 100 Contractor Inventory History objectCommercient external key column9
Sage AR InvoiceCommercient Sage 100 Contractor AR Invoice objectCommercient external key column10
Sage AR invoice lineCommercient Sage 100 Contractor AR Invoice Line objectCommercient external key column11
Sage AR PaymentsCommercient Sage 100 Contractor AR Payment objectCommercient external key column12
QuoteQuotesCommercient external key column13
Sales orderSales ordersCommercient external key column14
InvoiceInvoicesCommercient external key column15

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
salesperson feedinsert onlyemployees
account feedinsert onlyclients
customer feedinsert onlyclients
job feedinsert onlyjobs
product feedinsert onlyparts
contact feedinsert + updateclient contacts
parts feedinsert onlyparts
inventory history feedinsert onlyinventory history
AR invoice feedinsert onlyAR invoices, jobs
AR invoice line feedinsert onlyAR invoice lines
AR payment feedinsert onlyAR payments
quote feedinsert onlyservice invoice lines, parts, service invoices, jobs, clients
sales order feedinsert onlyservice invoice lines, parts, service invoices, jobs, clients
invoice feedinsert onlyservice invoice lines, parts, service invoices, jobs, clients

4. Order of work

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

  • 1 — Users
  • 2 — Sage Sales Person
  • 3 — Accounts
  • 4 — Sage Customer
  • 5 — Sage Job
  • 6 — Products
  • 7 — Contacts
  • 8 — Sage Parts
  • 9 — Sage Inventory History
  • 10 — Sage AR Invoice
  • 11 — Sage AR invoice line
  • 12 — Sage AR Payments
  • 13 — Quote
  • 14 — Sales order
  • 15 — Invoice

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.

  • salesperson feed reads salesperson sync output; no template in this set writes salesperson sync output
  • account feed reads salesperson sync output, account sync output, user sync output (generic name); no template in this set writes salesperson sync output, account sync output, user sync output (generic name)
  • customer feed reads account sync output, salesperson sync output, customer sync output; no template in this set writes account sync output, salesperson sync output, customer sync output
  • job feed reads account sync output, customer sync output, salesperson sync output, job sync output; no template in this set writes account sync output, customer sync output, salesperson sync output, job sync output
  • product feed reads product sync output; no template in this set writes product sync output
  • contact feed reads account sync output, contact sync output; no template in this set writes account sync output, contact sync output
  • parts feed reads product sync output, parts sync output; no template in this set writes product sync output, parts sync output
  • inventory history feed reads product sync output, parts sync output, inventory history sync output; no template in this set writes product sync output, parts sync output, inventory history sync output
  • AR invoice feed reads account sync output, customer sync output, job sync output, AR invoice sync output; no template in this set writes account sync output, customer sync output, job sync output, AR invoice sync output
  • AR invoice line feed reads AR invoice sync output, product sync output, parts sync output, AR invoice line sync output; no template in this set writes AR invoice sync output, product sync output, parts sync output, AR invoice line sync output
  • AR payment feed reads AR invoice sync output, AR payment sync output; no template in this set writes AR invoice sync output, AR payment sync output
  • quote feed reads product sync output, account sync output, salesperson sync output, quote sync output; no template in this set writes product sync output, account sync output, salesperson sync output, quote sync output
  • sales order feed reads product sync output, account sync output, salesperson sync output, quote sync output, sales order sync output; no template in this set writes product sync output, account sync output, salesperson sync output, quote sync output
  • invoice feed reads product sync output, account sync output, salesperson sync output, sales order sync output, invoice sync output; no template in this set writes product sync output, account sync output, salesperson sync output, sales order sync output

5. Field mapping

Each template carries its intended mapping in field mapping.

TemplateObjectMapped fieldsFirst ERP → Zoho CRM pairs
Usersusers1Commercient external key column → Commercient external key column
Sage Sales PersonCommercient Sage 100 Contractor Salesperson object79Record number → Commercient external key (custom field), Employee first name, Employee last name → Name, Aatrix electronic Affordable Care Act form consent → Aatrix electronic Affordable Care Act form consent (custom field), Aatrix electronic wage statement consent → Aatrix electronic wage statement consent (custom field), Electronic funds transfer status → Account status (custom field)
AccountsAccounts16Record number → Commercient AR customer code (Zoho field), Client name → Account name, Street address line 1, Street address line 2 → Billing street (Zoho field), City name → Billing city (Zoho field), State → Billing state
Sage CustomerCommercient Sage 100 Contractor Customer object108Record number → Commercient external key (custom field), Client name → Name, Street address line 1 → Address 1, Street address line 2 → Address 2, Region → Area
Sage JobCommercient Sage 100 Contractor Job object76Record number → Commercient external key (custom field), Job name → Name, Client number → Accounts, Client number → Sage 100 Contractor customer (related record), Sales employee → Sage 100 Contractor sales rep (related record)
ProductsProducts7Record number → Commercient external key column, Part name → Product name (Zoho field), Record number → ERP product code, Note text → Description, Inactive → Product active (Zoho field)
ContactsContacts9Record number,Line number → Commercient external key column, Contact name → Last name, Contact name → First name, Email → Email, Phone number → Home phone
Sage PartsCommercient Sage 100 Contractor Parts object38Record number → Commercient external key (custom field), Part name → Name, Alpha part number → Alpha part number (Zoho field), Average cost → Average cost (Zoho field), Part billing amount → Billing amount (Zoho field)
Sage Inventory HistoryCommercient Sage 100 Contractor Inventory History object20Record number → Commercient external key (custom field), Record number → Name, Entry date → Entry date (custom field), Ledger record → Ledger reference number (custom field), Location number → Location (custom field)
Sage AR InvoiceCommercient Sage 100 Contractor AR Invoice object51Record number → Commercient external key (custom field), Record number, Invoice number → Custom module name (custom field), Record number, Invoice number → Name, Invoice balance → Balance, Purchase order → Client PO (Zoho field)
Sage AR invoice lineCommercient Sage 100 Contractor AR Invoice Line object27Record number, Line number → Commercient external key (custom field), Record number, Line number → Name, Ledger account → Account, Alpha part number → Alpha part number (custom field), Cost code → Cost code (custom field)
Sage AR PaymentsCommercient Sage 100 Contractor AR Payment object13Amount → Amount paid, Applied credit → Credit taken (Zoho field), Check date → Date, Payment description → Description, Discount taken → Discount taken (Zoho field)
QuoteQuotes16Record number → Commercient external key (custom field), the linked Salesforce record → Account name, Record number → Name, Record number → returned quote number, Inserted date → ERP created date (custom field)
Sales orderSales orders17Record number → Commercient external key (custom field), the linked Salesforce record → Account name, the linked Salesforce record → quote name lookup, Record number → Name, Record number → Sales order number (Zoho field)
InvoiceInvoices16Record number → Commercient external key (custom field), the linked Salesforce record → Account name, the linked Salesforce record → Sales order (single record), Record number → Name, Record number → Invoice number (Zoho field)

6. Community templates

The catalogue carries 14 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: 14
  • Default operations: insert on 14, update on 14, delete on 14
  • Marked as circular sync: 0
  • Licence groups they span: 5
  • Destination objects: Accounts, Contacts, Invoices, Products, Quotes, Commercient Sage 100 Contractor AR Payment object, Commercient Sage 100 Contractor AR Invoice object, Commercient Sage 100 Contractor AR Invoice Line object, Commercient Sage 100 Contractor Customer object, Commercient Sage 100 Contractor Inventory History object, Commercient Sage 100 Contractor Job object, Commercient Sage 100 Contractor Parts object, Commercient Sage 100 Contractor Salesperson object, Sales orders
  • Object display names: Accounts, Contacts, Invoice, Products, Quote, Sage AR Invoice, Sage AR invoice line, Sage AR Payments, Sage Customer, Sage Inventory History, Sage Job, Sage Parts and 2 more
  • Template groups: Account, CRM Order and Line, CRM Quote 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-zohocrm/erps/sage-100-contractor-2018.

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 Contractor 2018 → Zoho CRM templates set up. dlake-crmpro-zohocrm is the destination skill this page sits under: its own text is the authority for the Zoho CRM 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-zohocrm/erps/sage-100-contractor-2018, 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.