Agent skill
dlake-crmpro-mdc
When an agent should use it: What the shipped CRMPro Standard templates set up when MDC is the destination, stated across every source ERP that ships them: the object API names the templates push to (`invoice`, `salesorder`, `salesorderdetail`), the `TimeStampRepository` key separator they build, the view and `TimeStamp_Prefix` conventions, and which template groups every source ships versus only some. Use it when standing up or reading a MDC template set, when deciding which templates to import and activate, or when a run completes without pushing records and the answer is in the view or the configuration row. It extends `dlake-crmpro`, which covers operating CRMPro generally, and it carries one child page per source ERP under `erps/`, which is where everything ERP-specific lives.
Extends dlake-crmpro.
11 source-ERP pages: what the shipped templates set up for each (also readable with dlake skills show dlake-crmpro-mdc/erps/<erp>)
Install with "dlake skills install" or read it in the terminal with "dlake skills show dlake-crmpro-mdc". Skills ship inside the CLI; the copy below mirrors the GitHub repository.
CRMPro → MDC: 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.
The source ERP has its own page under this skill. erps/<erp>.md is a child file of this
skill and describes what the shipped templates for that ERP → MDC pair set up. §6 lists every one
of them and how to pick the right row; read this page first, then that one.
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.
What follows is only what the shipped Standard templates for MDC themselves set, and only the part
of it that is the same across 11 source ERPs. Everything that belongs to one source — which groups
ship, which clone tables the views read, which view names and prefixes are paired — is on that
ERP’s own page under erps/. This page grows as the catalogue does.
1. The objects these templates push to
Every source ERP that ships MDC templates pushes to invoice, salesorder, salesorderdetail.
Copy an object name from the template or from crmpro_crm_objects; case is part of the name.
These appear in some sources’ sets and not others:
CRM_Object_API_Name | Sources whose templates push it |
|---|---|
invoicedetail | 10 of 11 |
pricelevel | 10 of 11 |
product | 10 of 11 |
uom | 10 of 11 |
uomschedule | 10 of 11 |
account | 4 of 11 |
quote | 2 of 11 |
quotedetail | 2 of 11 |
comrcint_apteanm2m_address | 1 of 11 |
comrcint_apteanm2m_contact | 1 of 11 |
comrcint_apteanm2m_customer | 1 of 11 |
comrcint_apteanm2m_invoicedetail | 1 of 11 |
comrcint_apteanm2m_invoiceheader | 1 of 11 |
comrcint_apteanm2m_salesperson | 1 of 11 |
comrcint_apteanm2m_sodetail | 1 of 11 |
comrcint_apteanm2m_soheader | 1 of 11 |
comrcint_baan_customer | 1 of 11 |
comrcint_baan_invoice | 1 of 11 |
comrcint_baan_salesorder | 1 of 11 |
comrcint_baan_salesorderdetail | 1 of 11 |
comrcint_baan_salesperson | 1 of 11 |
comrcint_baan_shiptoaddress | 1 of 11 |
comrcint_epicoreagle_invoice | 1 of 11 |
comrcint_epicoreagle_invoicedetail | 1 of 11 |
comrcint_epicoreagle_salesorder | 1 of 11 |
comrcint_epicoreagle_salesorderdetail | 1 of 11 |
comrcint_ifserp_invoice | 1 of 11 |
comrcint_ifserp_invoicedetail | 1 of 11 |
comrcint_ifserp_salesorder | 1 of 11 |
comrcint_ifserp_salesorderdetail | 1 of 11 |
comrcint_inforsytelinev9_address | 1 of 11 |
comrcint_inforsytelinev9_customer | 1 of 11 |
comrcint_inforsytelinev9_invoice | 1 of 11 |
comrcint_inforsytelinev9_invoicelineitem | 1 of 11 |
comrcint_inforsytelinev9_salesorder | 1 of 11 |
comrcint_inforsytelinev9_salesorderline | 1 of 11 |
comrcint_sage1002017_invoice | 1 of 11 |
comrcint_sage1002017_invoicedetail | 1 of 11 |
comrcint_sage1002017_salesorder | 1 of 11 |
comrcint_sage1002017_salesorderdetail | 1 of 11 |
contact | 1 of 11 |
2. The repository key these templates build
Every one of these template sets builds its TimeStampRepository key as
<TimeStamp_Prefix>:<key>. The literal in the view and the TimeStamp_Prefix on the
configuration row have to be the same string, case included; a key built with the other separator
matches nothing the engine wrote.
The views these templates create are named with the vw_ prefix form. The TimeStamp_Prefix is
not reliably the view name — the ERP pages carry the pairings — and it is what every downstream
view joins on, so it is effectively public API between processes.
3. What the template groups deliver
The rest are shipped by some sources only:
| Template group | Sources that ship it |
|---|---|
| CRM invoice | 10 of 11 |
| CRM Product | 10 of 11 |
| CRM salesorder | 10 of 11 |
| CRM salesorderdetail | 10 of 11 |
| CRM UOM | 10 of 11 |
| CRM invoicedetail | 9 of 11 |
| CRM PriceLevel | 9 of 11 |
| CRM UoMSchedule | 8 of 11 |
| CRM Account | 3 of 11 |
| CRM Contact | 2 of 11 |
| CRM Quote and Line | 2 of 11 |
| CRM UOMSchedule | 2 of 11 |
| apteanm2m Address | 1 of 11 |
| apteanm2m Contact | 1 of 11 |
| apteanm2m customer | 1 of 11 |
| apteanm2m Invoice Detail | 1 of 11 |
| apteanm2m Invoice Header | 1 of 11 |
| apteanm2m Sales Person | 1 of 11 |
| apteanm2m SalesOrder Detail | 1 of 11 |
| apteanm2m SalesOrder Header | 1 of 11 |
| BAAN Customer | 1 of 11 |
| BAAN Invoice | 1 of 11 |
| BAAN Sales Person | 1 of 11 |
| BAAN SalesOrder | 1 of 11 |
| BAAN SalesOrderDetail | 1 of 11 |
| BAAN ShipTo Address | 1 of 11 |
| CRM account | 1 of 11 |
| CRM PriceBook | 1 of 11 |
| CRM quotedetail | 1 of 11 |
| EPICOREAGLE Invoice | 1 of 11 |
| EPICOREAGLE Invoice Detail | 1 of 11 |
| EPICOREAGLE Salesorder | 1 of 11 |
| EPICOREAGLE Salesorder Detail | 1 of 11 |
| IFSERP Invoice | 1 of 11 |
| IFSERP Invoice Detail | 1 of 11 |
| IFSERP Sales Order | 1 of 11 |
| IFSERP Sales Order Detail | 1 of 11 |
| INFORSYTELINEV9 Address | 1 of 11 |
| INFORSYTELINEV9 Customer | 1 of 11 |
| INFORSYTELINEV9 Invoice | 1 of 11 |
That is the 40 most widely shipped; the ERP pages carry the rest.
Every one of these templates inserts Is_Active as 0, so an imported process is inactive until
an operator activates it, and the Registration API’s import does not populate CRM_FieldList — an
object with no CRM_FieldList rows pushes nothing and records no error. Read MappingJson off
the template with dlake admin crmpro_templates, then check crmpro_field_mapping on the created
process before activating it.
4. When a run pushes no records
The signature failure is the one dlake-crmpro §7d describes: every object logs a start and an
end in about 0.00 seconds, the total is zero, and no error is written anywhere. For this
destination, check in this order.
- Does the view return rows? Zero rows means the answer is in the view.
- Does
TimeStamp_Prefixequal the literal the view builds its key from, case included — and not, by reflex, the view’s own name? - Is the separator the one §2 names, in both the view literal and the prefix?
- Does
CRM_FieldListhave rows for thatObject_Name, spelled as the API name? - Any NULL nullable text column on the configuration row? The templates set
''throughout, and a NULL throws inside the engine, which catches it — so the object is skipped with no recorded error. - Is the parent’s prefix the one that actually holds the ids? A view that reads another
process’s prefix returns nothing until that process has run, which is what makes
Sync_Ordera dependency order rather than a preference. - Do the clone tables the view reads carry the prefix this ERP’s templates expect? That is on the ERP’s own page, and it differs between sources.
5. 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 ::.
6. The source ERP’s own page
One row per source ERP the catalogue carries MDC templates for. Each page is a child file of this
skill, addressed as dlake-crmpro-mdc/erps/<erp> — dlake skills show dlake-crmpro-mdc/erps/<erp> prints one, and dlake skills install writes them beside this file.
| ERP | Page | What its templates deliver |
|---|---|---|
| Aptean Made2Manage | erps/aptean-made2manage.md | 18 Standard templates in 18 groups, pushing uomschedule, uom, pricelevel, product and more; : repository keys |
| Baan | erps/baan.md | 14 Standard templates in 14 groups, pushing uomschedule, uom, product, pricelevel and more; : repository keys |
| Epicor Eagle | erps/epicor-eagle.md | 12 Standard templates in 12 groups, pushing uomschedule, uom, pricelevel, product and more; : repository keys |
| IFS | erps/ifs.md | 12 Standard templates in 12 groups, pushing uomschedule, uom, pricelevel, product and more; : repository keys |
| Infor SyteLine V9 | erps/infor-syteline-v9.md | 15 Standard templates in 15 groups, pushing uomschedule, uom, pricelevel, product and more; : repository keys |
| Sage 100 (US) | erps/sage-100-us.md | 8 Standard templates in 8 groups, pushing uomschedule, uom, pricelevel, product and more; : repository keys |
| Sage 100 2017 | erps/sage-100-2017.md | 10 Standard templates in 10 groups, pushing salesorder, salesorderdetail, invoice, invoicedetail and more; : repository keys |
| Sage 100 US (SAGE100US) | erps/sage-100-us-sage100us.md | 10 Standard templates in 10 groups, pushing uomschedule, uom, pricelevel, product and more; : repository keys |
| Sage 50 UK | erps/sage-50-uk.md | 8 Standard templates in 8 groups, pushing uomschedule, uom, pricelevel, product and more; : repository keys |
| SAP B1 | erps/sap-b1.md | 10 Standard templates in 10 groups, pushing uomschedule, uom, pricelevel, product and more; : repository keys |
| SYSPRO 7 and above | erps/syspro-7-and-above.md | 8 Standard templates in 8 groups, pushing uomschedule, uom, pricelevel, product and more; : repository keys |
Work out which row applies before reading one. The source is the ERP the tenant was registered
with: dlake register erps lists the catalogue’s names and codes, and dlake admin crmpro_templates shows what that tenant can actually import. Match that ERP to a row above, then
read its page alongside this one — this page for the conventions that hold across every source,
that page for what this source’s own templates set. If no row matches the tenant’s ERP, this skill
alone applies: the catalogue ships no Standard templates for that pair, so there is nothing
ERP-specific to read and nothing to import.
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 skill
adds what the shipped MDC templates set up, and its erps/ pages add what each source ERP’s own
templates set. dlake-crmpro-hubspot, dlake-crmpro-salesforce and dlake-crmpro-shopify are
the hand-written destination skills for their CRMs, and the conventions genuinely differ between
destinations. 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.
