CRMPro → Zoho CRM — GlobalShop: what the shipped templates set up

CRMPro → Zoho CRM — GlobalShop: 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/globalshop (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

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.

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.

4. Order of work

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

• 0 — Users
• 1 — Global Shop Term
• 2 — Global Shop Salesperson
• 3 — Account
• 4 — Global Shop Customer, Contacts
• 5 — Global Shop Ship to
• 6 — Products
• 7 — Global Shop Item
• 8 — Global Shop Sales order, Global Shop Item list
• 9 — Global Shop Sales order line
• 10 — Global Shop Invoice
• 11 — Global Shop invoice 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.

• terms feed reads terms sync output; no template in this set writes terms sync output
• salesperson feed reads salesperson sync output; no template in this set writes salesperson sync output
• account feed reads account sync output; no template in this set writes account sync output
• customer feed reads account sync output, customer sync output; no template in this set writes account sync output, customer sync output
• contact feed reads account sync output, contact sync output; no template in this set writes account sync output, contact sync output
• shipping address feed reads account sync output, customer sync output, shipping address sync output; no template in this set writes account sync output, customer sync output, shipping address sync output
• product feed reads item sync output, product sync output; no template in this set writes item sync output, product sync output
• item feed reads product sync output, item sync output; no template in this set writes product sync output, item sync output
• sales order feed reads account sync output, customer sync output, sales order sync output; no template in this set writes account sync output, customer sync output, sales order sync output
• item list feed reads product sync output, item sync output, item list sync output; no template in this set writes product sync output, item sync output, item list sync output
• sales order line feed reads sales order sync output, product sync output, item sync output, sales order line sync output; no template in this set writes sales order sync output, product sync output, item sync output, sales order line sync output
• invoice feed reads account sync output, customer sync output, invoice sync output; no template in this set writes account sync output, customer sync output, invoice sync output
• invoice line feed reads invoice sync output, product sync output, item sync output, invoice line sync output; no template in this set writes invoice sync output, product sync output, item sync output, invoice line sync output

5. Field mapping

Each template carries its intended mapping in field mapping.

6. 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/globalshop.

7. 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 GlobalShop → 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/globalshop, 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.