CRMPro → Shopify — QuickBooks Desktop: what the shipped templates set up

CRMPro → Shopify — QuickBooks Desktop: 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-shopify is the destination skill this page is a child of, and the authority for the Shopify 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-shopify/erps/quickbooks-desktop.md, and that skill’s ERP table is what points at it. What follows is only what the shipped QuickBooks Desktop → Shopify 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
CUSTOMER	The templates push CUSTOMER to Shopify. Records are created once; they are not updated and none are deleted.	CUSTOMER	SF_ERP_Salesforce_Clone_Customer
CUSTOMER ADDRESS	The templates push CUSTOMERADDRESS to Shopify. Records are created once; they are not updated and none are deleted.	CUSTOMERADDRESS	SF_ERP_Salesforce_Clone_Customer
PRODUCT	The templates push PRODUCT to Shopify. Records are created once; they are not updated and none are deleted.	PRODUCT	SF_ERP_Salesforce_Clone_ItemInventory
PRODUCT UPDATE	The templates push PRODUCTQUANTITY, PRODUCTPRICE to Shopify. New records are created and existing ones updated; none are deleted.	PRODUCTQUANTITY, PRODUCTPRICE	SF_ERP_Salesforce_Clone_ItemInventory, Shopify_ProductVariant, Shopify_InventoryLevel

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
createcustomer	CUSTOMER	1	SHOPIFY_NEW_CUSTOMER	vw_SHOPIFY_NEW_CUSTOMER	'' / ''
createproduct	PRODUCT	1	SHOPIFY_NEW_PRODUCT	vw_SHOPIFY_NEW_PRODUCT	'' / ''
updatequantity	PRODUCTQUANTITY	1	PRODUCTQUANTITY	Shopify_ProductVariant_QuantyUpdate	'' / ''
updateprice	PRODUCTPRICE	1	PRODUCTPRICE	Shopify_ProductVariant_PriceUpdate	'' / ''
CUSTOMERADDRESS	CUSTOMERADDRESS	2	SHOPIFY_NEW_CUSTOMER_ADDRESS	vw_SHOPIFY_NEW_CUSTOMER_ADDRESS	'' / ''

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. The insert column lists do not include Sync_Operation_Type, Sync_Batch_Size, IsAccountMatching, Document_Source_Path, so those columns take their CRM_Configuration defaults. 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_SHOPIFY_NEW_CUSTOMER	insert-only	SHOPIFY_NEW_CUSTOMER::	—	RecordKey	SF_ERP_Salesforce_Clone_Customer
vw_SHOPIFY_NEW_PRODUCT	insert-only	SHOPIFY_NEW_PRODUCT::	—	RecordKey	SF_ERP_Salesforce_Clone_ItemInventory
Shopify_ProductVariant_QuantyUpdate		—	—	RecordKey	SF_ERP_Salesforce_Clone_ItemInventory, Shopify_ProductVariant, Shopify_InventoryLevel
Shopify_ProductVariant_PriceUpdate		—	—	RecordKey	SF_ERP_Salesforce_Clone_ItemInventory, Shopify_ProductVariant
vw_SHOPIFY_NEW_CUSTOMER_ADDRESS	insert-only	SHOPIFY_NEW_CUSTOMER_ADDRESS::	SHOPIFY_NEW_CUSTOMER::	RecordKey	SF_ERP_Salesforce_Clone_Customer

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

• 1 — createcustomer, createproduct, updatequantity, updateprice
• 2 — CUSTOMERADDRESS

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_SHOPIFY_NEW_CUSTOMER_ADDRESS reads SHOPIFY_NEW_CUSTOMER::

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 → Shopify pairs
createcustomer	CUSTOMER	9	RecordKey → RecordKey, description → description, erp_code → erp_code, Email → Email, FirstName → FirstName
createproduct	PRODUCT	7	Title → Title, BodyHtml → BodyHtml, RecordKey → RecordKey, SavedTimeStamp → SavedTimeStamp, SKU → SKU
updatequantity	PRODUCTQUANTITY	6	RecordKey → RecordKey, Id → Id, InventoryQuantity → InventoryQuantity, InventoryItemId → InventoryItemId, OldQuantity → OldQuantity
updateprice	PRODUCTPRICE	3	RecordKey → RecordKey, ProductVariantId → ProductVariantId, Price → Price
CUSTOMERADDRESS	CUSTOMERADDRESS	16	RecordKey → RecordKey, description → description, erp_code → erp_code, Address1 → Address1, Address2 → Address2

6. 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:

• SHOPIFY_NEW_CUSTOMER
• SHOPIFY_NEW_CUSTOMER_ADDRESS
• SHOPIFY_NEW_PRODUCT
• PRODUCTQUANTITY
• PRODUCTPRICE

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 QuickBooks Desktop → Shopify templates set up. dlake-crmpro-shopify is the destination skill this page sits under: its own text is the authority for the Shopify 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.