Source ERP · 100 of 105
CRMPro → Salesforce — SYSPRO 7 and above: what the shipped templates set up
The dlake CLI repository no longer publishes this guide. It is kept here as last published with dlake v0.5.47. Source table, view and field names are not shown here; whitelisted customers fetch the full guide, with its per-ERP pages, from the admin plane with "dlake admin get_skill dlake-crmpro-salesforce". It extends the dlake-crmpro-salesforce skill, which holds what is true whatever the source ERP. Both directions for this pair are summarised at /integrations/syspro-7-and-above-salesforce/.
CRMPro → Salesforce — SYSPRO 7 and above: what the shipped templates set up
dlake-crmpro-salesforce is the destination skill this page is a child of, and the authority for the Salesforce conventions that hold across every ERP — the single-colon key, the external-id identity column, the namespace pair, the id-chaining ladder. Read those first; this page does not repeat them. This page is dlake-crmpro-salesforce/erps/syspro-7-and-above.md, and that skill’s ERP table is what points at it.
Where the catalogue and a live install disagree, trust the install and say so.
1. What the default catalogue delivers
| Group | Business outcome | Objects |
|---|---|---|
| Account | ERP customers become Salesforce Accounts, and the full AR customer record lands beside them in the managed package so sales sees terms, class, area, branch and salesperson from the ERP | accounts, custom objects |
| Sal Area | ERP sales areas become lookup records the AR customer points at | custom objects |
| Branch | Where the ERP tracks branches, divisions or locations on the AR customer master, those become records the Account hierarchy can be read through | custom objects |
| Salesorder | Sales orders and their lines arrive in full, so service and sales can see order status, requested ship dates, PO numbers, discounts and per-line quantities without leaving the CRM | custom objects |
| Invoice | Open and historical invoices, their payments and their transaction detail sync; a balance or terms change on an open invoice is reflected on the next run | custom objects |
| Product | ERP stock codes become Salesforce Products, with the inventory master and per-warehouse quantities alongside them | products, custom objects |
| Pricebook | ERP selling prices become price book entries | price book entries |
| Customer Multi Ship Addresses | Every ship-to address on an AR customer appears as a related list on the Account | custom objects |
| Sales Move | ERP sales-movement history syncs for reporting on the Account | custom objects |
1 more template group is not listed here because its name is an internal identifier; it is in the operational skill (dlake admin get_skill dlake-crmpro-salesforce).
Check what the tenant actually has with dlake admin crmpro_tables_views before applying a template: an import against the wrong prefix fails with a missing-table warning and leaves the view pending.
2. The view-name and prefix pairings
The detail behind this section is part of the operational skill, which whitelisted customers fetch, with its per-ERP pages, from the admin plane with dlake admin get_skill dlake-crmpro-salesforce.
3. A worked view from this set
The detail behind this section is part of the operational skill, which whitelisted customers fetch, with its per-ERP pages, from the admin plane with dlake admin get_skill dlake-crmpro-salesforce.
4. The lookup ladder in this set
The detail behind this section is part of the operational skill, which whitelisted customers fetch, with its per-ERP pages, from the admin plane with dlake admin get_skill dlake-crmpro-salesforce.
5. Base views the import will not create
The detail behind this section is part of the operational skill, which whitelisted customers fetch, with its per-ERP pages, from the admin plane with dlake admin get_skill dlake-crmpro-salesforce.
6. Two things in this set that do not work as written
The detail behind this section is part of the operational skill, which whitelisted customers fetch, with its per-ERP pages, from the admin plane with dlake admin get_skill dlake-crmpro-salesforce.
7. Where this sits
dlake-crmpro is the general operating surface, and dlake-crmpro-salesforce is the destination skill this page sits under: its own text is the authority for the Salesforce 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.
