CRMPro → HubSpot — Epicor BisTrack: what the shipped templates set up

CRMPro → HubSpot — Epicor BisTrack: what the shipped templates set up

Keep this skill current. dlake ships updates often and this text is embedded in the CLI you have installed. Before relying on it, compare dlake --version with npm view @commercient/dlake version; if they differ, run npm install -g @commercient/dlake@latest and then dlake skills install, which overwrites the installed skill files with the current text.

dlake-crmpro is the parent skill and the authority for everything general: the crmpro_* tools, CRM_Configuration and CRM_FieldList, TimeStampRepository, the three kinds of source view, the NULL-cursor rule and the silent zero-record run. Read it first; this page does not repeat it. dlake-crmpro-hubspot is the destination skill this page is a child of, and the authority for the HubSpot conventions that hold across every ERP: read it first, then come back here for what this source’s own templates set. This page is dlake-crmpro-hubspot/erps/epicor-bistrack.md, and that skill’s ERP table is what points at it. What follows is only what the shipped Epicor BisTrack → HubSpot templates themselves set, read from their Insert_Query, CreateViewQuery and MappingJson. This page grows as the catalogue does.

1. What the templates deliver

Group	Business outcome	Objects	Source tables and views
create contact	ERP SF_ERP_Salesforce_Clone_CustomerContact, SF_ERP_Salesforce_Clone_Customer, SF_ERP_Salesforce_Clone_SalesRep data becomes contact in HubSpot. New records are created and existing ones updated; none are deleted.	contact	SF_ERP_Salesforce_Clone_CustomerContact, SF_ERP_Salesforce_Clone_Customer, SF_ERP_Salesforce_Clone_SalesRep
create company	ERP SF_ERP_Salesforce_Clone_Customer data becomes company in HubSpot. New records are created, existing ones updated, and records removed in the ERP are deleted.	company	SF_ERP_Salesforce_Clone_Customer
create product	ERP SF_ERP_Salesforce_Clone_Product data becomes product in HubSpot. New records are created, existing ones updated, and records removed in the ERP are deleted.	product	SF_ERP_Salesforce_Clone_Product

2. The process rows the templates create

Each template’s Insert_Query writes one CRM_Configuration row. These are the values it sets; a column the inserts never set is not listed.

Display name	CRM_Object_API_Name	Sync_Order	TimeStamp_Prefix	SQL_Query target	field prefix / postfix	Sync_Operation_Type
create contact	contact	5	HUBSPOT_NEW_CONTACT	vw_HUBSPOT_NEW_CONTACT	'' / ''	2
create customer	company	5	HUBSPOT_NEW_CUSTOMER	vw_HUBSPOT_NEW_CUSTOMER	'' / ''	2
create product	product	10	HUBSPOT_NEW_ITEM	vw_HUBSPOT_NEW_ITEM	'' / ''	2

Every one of these inserts Is_Active as 0, so an imported process is inactive until an operator activates it. Across the set they insert Is_Create_Entity 0, Is_Create_Fields 0, Is_Active_Get_Records 0, Is_Active_Delete_Records 0, IsAccountMatching '', Sync_Batch_Size 200. Text columns a template does not use are inserted as '' rather than left NULL.

3. The views

Each template creates its view with CreateViewQuery, in the gateway dbo schema. “Change detection” names which of the three kinds dlake-crmpro defines the view’s own WHERE makes it; where a view’s shape is not one of those three the column is left empty and the view’s own WHERE is the authority.

View	Change detection	Repository key	Reads other prefixes	Identity column	Source tables
vw_HUBSPOT_NEW_CONTACT	insert-only	HUBSPOT_NEW_CONTACT::	HUBSPOT_NEW_OWNER::, HUBSPOT_NEW_CUSTOMER::	RecordKey, externalkey	SF_ERP_Salesforce_Clone_CustomerContact, SF_ERP_Salesforce_Clone_Customer, SF_ERP_Salesforce_Clone_SalesRep
vw_HUBSPOT_NEW_CUSTOMER	insert-only	HUBSPOT_NEW_CUSTOMER::	—	RecordKey	SF_ERP_Salesforce_Clone_Customer
vw_HUBSPOT_NEW_ITEM	insert-only	HUBSPOT_NEW_ITEM::	—	RecordKey, externalkey	SF_ERP_Salesforce_Clone_Product

The repository key these templates build is <TimeStamp_Prefix>::<key>. The literal in the view and the TimeStamp_Prefix on the configuration row have to be the same string, case included.

4. Order of work

The templates set Sync_Order to 5, 10. A run processes active rows in ascending Sync_Order, which is the order the templates put them in:

• 5 — create contact, create customer
• 10 — create product

Several of these rows share a Sync_Order 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 repository prefix, which is what makes the order a dependency order: the row appears in the view only once the process that writes that prefix has run, so a parent flows on one run and its children on the next.

• vw_HUBSPOT_NEW_CONTACT reads HUBSPOT_NEW_OWNER::, HUBSPOT_NEW_CUSTOMER::; no template in this set writes HUBSPOT_NEW_OWNER::

5. Field mapping

CRM_FieldList carries one row per pushed column, with Object_Name equal to the CRM_Object_API_Name value — as dlake-crmpro puts it, an object with no CRM_FieldList rows pushes nothing and records no error. Each template carries its intended mapping in MappingJson. Read that with dlake admin crmpro_templates, then check crmpro_field_mapping on the created process before activating it.

Template	Object	Mapped fields	First ERP → HubSpot pairs
create contact	contact	14	CustomerContactID → externalkey, AddressID → addressid, Deleted → deleted, Email → email, Fax → fax
create customer	company	9	CustomerID → arcustomercode, Name → name, Address1 → address, Address2 → address2, City → city
create product	product	4	ProductCode → hs_sku, ShortDescription,ProductCode → name, Description → description, StandardSellPrice → price

6. Community templates

The catalogue carries 19 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: 19
• Default operations: insert on 19, update on 19, delete on 19
• Marked circular-sync: 0
• Licence groups they span: 5
• Destination objects: deal, line_item, company, contact, commercientepicorbistrack_EPICORBISTRACK_Users, CommercientSF10__ACCOUNTMATCHING__c, products and 2 custom objects
• Object display names: upsert company, upsert order, upsert order detail, create contact, insert contact, matching customers, SYNC ACCOUNTMATCHING, Sync Users, upsert invoice, upsert invoice detail, upsert job, upsert locations and 4 more
• Template groups: Account, CRM Opportunity and Line, Product

A community template is imported the way a shipped one is, and the same rules apply to what it creates: read the process it creates with crmpro_get_process, its mapping with crmpro_field_mapping, and the view it selects from, before activating it.

7. Verifying

# per-prefix counts; every synced record carries its destination id
dlake tool query --profile <tenant> --sql "SELECT LEFT([Key], CHARINDEX(':',[Key])-1) AS prefix, COUNT(*) n, COUNT(NULLIF(SFDCID,'')) withId FROM dbo.TimeStampRepository WHERE CHARINDEX(':',[Key])>0 GROUP BY LEFT([Key], CHARINDEX(':',[Key])-1)"

withId = n for every prefix is the success condition dlake-crmpro defines. The split is on the first colon, which is the prefix boundary whether the key separator is : or ::.

The prefixes these templates set:

• HUBSPOT_NEW_CONTACT
• HUBSPOT_NEW_CUSTOMER
• HUBSPOT_NEW_ITEM

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 Epicor BisTrack → HubSpot templates set up. dlake-crmpro-hubspot is the destination skill this page sits under: its own text is the authority for the HubSpot 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 clone tables, 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.