CRMPro → HubSpot — Infor CloudSuite: what the shipped templates set up

CRMPro → HubSpot — Infor CloudSuite: 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/infor-cloudsuite.md, and that skill’s ERP table is what points at it. What follows is only what the shipped Infor CloudSuite → 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_contact_mst, SF_ERP_Salesforce_Clone_customer_contact_mst, SF_ERP_Salesforce_Clone_custaddr_mst data becomes contact in HubSpot. New records are created and existing ones updated; none are deleted.	contact	SF_ERP_Salesforce_Clone_contact_mst, SF_ERP_Salesforce_Clone_customer_contact_mst, SF_ERP_Salesforce_Clone_custaddr_mst
create company	ERP CUSTADDR_MST, CUSTOMER_MST data becomes company in HubSpot. New records are created and existing ones updated; none are deleted.	company	SF_ERP_Salesforce_Clone_customer_mst, SF_ERP_Salesforce_Clone_custaddr_mst
create opporrtunity deal	ERP CUSTADDR_MST, CUSTOMER_MST, OPPORTUNITY_MST data becomes deal in HubSpot. New records are created and existing ones updated; none are deleted.	deal	SF_ERP_Salesforce_Clone_opportunity_mst, SF_ERP_Salesforce_Clone_custaddr_mst, SF_ERP_Salesforce_Clone_customer_mst, SF_ERP_Salesforce_Clone_slsman_mst

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 company	company	1	HUBSPOT_NEW_CUSTOMER	vw_HUBSPOT_NEW_CUSTOMER	'' / ''	2
create opportunity	deal	3	HUBSPOT_NEW_DEAL	vw_HUBSPOT_NEW_OPP_DEAL	'' / ''	2
create contact	contact	5	HUBSPOT_NEW_CONTACT	vw_HUBSPOT_NEW_CONTACT	'' / ''	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, 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	Emits SFDCID	Source tables
vw_HUBSPOT_NEW_CUSTOMER	insert-only	HUBSPOT_NEW_CUSTOMER::	—	RecordKey	no	SF_ERP_Salesforce_Clone_customer_mst, SF_ERP_Salesforce_Clone_custaddr_mst
vw_HUBSPOT_NEW_OPP_DEAL	insert-only	HUBSPOT_NEW_DEAL::	HUBSPOT_NEW_CUSTOMER::, HUBSPOT_NEW_CONTACT::	RecordKey, externalkey	yes	SF_ERP_Salesforce_Clone_opportunity_mst, SF_ERP_Salesforce_Clone_custaddr_mst, SF_ERP_Salesforce_Clone_customer_mst, SF_ERP_Salesforce_Clone_slsman_mst
vw_HUBSPOT_NEW_CONTACT	insert-only	HUBSPOT_NEW_CONTACT::	HUBSPOT_NEW_CUSTOMER::	RecordKey, externalkey	no	SF_ERP_Salesforce_Clone_contact_mst, SF_ERP_Salesforce_Clone_customer_contact_mst, SF_ERP_Salesforce_Clone_custaddr_mst

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 1, 3, 5. A run processes active rows in ascending Sync_Order, which is the order the templates put them in:

• 1 — create company
• 3 — create opportunity
• 5 — create contact

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_CUSTOMER::
• vw_HUBSPOT_NEW_OPP_DEAL reads HUBSPOT_NEW_CUSTOMER::, HUBSPOT_NEW_CONTACT::

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 company	company	10	site_ref, cust_num, cust_seq → arcustomercode, name → name, city → city, state → state, zip → zip
create opportunity	deal	9	opp_id, site_ref → externalkey, description, opp_id → dealname, est_value → amount, close_date, projected_close_date → closedate, CreateDate → createdate
create contact	contact	19	contact_id → externalkey, fname → firstname, lname → lastname, email → email, office_phone → phone

6. Community templates

The catalogue carries 52 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: 52
• Default operations: insert on 52, update on 52, delete on 52
• Marked circular-sync: 0
• Licence groups they span: 6
• Destination objects: deal, company, line_item, contact, product, quote, ACCOUNTMATCHING__c, Companies, Deals, SHIPTOMATCHING__c and a custom object
• Object display names: upsert company, upsert opportunity, upsert contact, upsert batch product, upsert estimate line, upsert product, create company, create contact, create opportunity, create quote, create quote line, delete batch line item, 20 more and 8 further templates
• Template groups: Account, CRM Quote and Line, CRM Opportunity and Line, Customer Multi Ship Addresses

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_DEAL

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 Infor CloudSuite → 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.