Source ERP · 21 of 24
CRMPro → Shopify — Sage Intacct: what the shipped templates set up
Read it in the terminal with "dlake skills show dlake-crmpro-shopify/erps/sage-intacct". It extends the dlake-crmpro-shopify skill, which holds what is true whatever the source ERP.
CRMPro → Shopify — Sage Intacct: what the shipped templates set up
Keep this skill current.
dlakeships updates often and this text is embedded in the CLI you have installed. Before relying on it, comparedlake --versionwithnpm view @commercient/dlake version; if they differ, runnpm install -g @commercient/dlake@latestand thendlake 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/sage-intacct.md, and that
skill’s ERP table is what points at it. What follows is only what the shipped Sage Intacct →
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 |
|---|---|---|---|
| updatequantity | The templates push PRODUCTQUANTITY to Shopify. New records are created and existing ones updated; none are deleted. | PRODUCTQUANTITY | SF_ERP_Salesforce_Clone_item, 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 | Sync_Operation_Type |
|---|---|---|---|---|---|---|
| updatequantity | PRODUCTQUANTITY | 1 | PRODUCTQUANTITY | Shopify_ProductVariant_QuantyUpdate | '' / '' | 1 |
Every one of these inserts Is_Active as 1, so an imported process starts active — check the
view before importing 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 |
|---|---|---|---|---|---|
Shopify_ProductVariant_QuantyUpdate | — | — | RecordKey | SF_ERP_Salesforce_Clone_item, Shopify_ProductVariant, Shopify_InventoryLevel |
4. 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:
PRODUCTQUANTITY
5. 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 Intacct → 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.