Source ERP · 2 of 69
TxDownloaderPro ← Salesforce — Applied Epic: what the shipped default templates set up
This is the capability summary the dlake CLI repository publishes; whitelisted customers fetch the operational skill with "dlake admin get_skill dlake-txdownloaderpro-salesforce/erps/applied-epic". It extends the dlake-txdownloaderpro-salesforce skill, which holds what is true whatever the source ERP. Both directions for this pair are summarised at /integrations/applied-epic-salesforce/.
TxDownloaderPro ← Salesforce — Applied Epic: what the shipped default templates set up
This is a capability summary, not an operating guide. To receive the operational skill you must be a
registered, whitelisted Commercient customer. Whitelisted customers fetch it with
dlake admin get_skill dlake-txdownloaderpro-salesforce/erps/applied-epic (or list_skills)
against the Commercient admin plane. Existing customers who need access or help: contact
support@commercient.com. New customers: contact sales@commercient.com to become a customer and be
whitelisted.
dlake-txdownloaderpro-salesforce is the Salesforce page and carries the destination detail: it is the skill this page is a child of, and the authority for the conventions that hold across every ERP, so read it before this page.
What follows is only what the shipped default templates for this pair themselves set, described from their default query, default inbound mapping and default outbound mapping columns. It is a description of structure: which objects and marker columns are read, which parts and members are filled, which token names appear. No template text is reproduced. This page grows as the default catalogue does.
1. What the templates deliver
One row per process the default set ships for this pair. The business language is the catalogue’s own, where it carries any; where it does not, the row says what the source and destination objects are and what the operation flags allow. Operations are the union of the insert, update and delete flags over that process’s templates.
| Process | What it delivers | Source → destination | Templates | Operations |
|---|---|---|---|---|
| Create New Client | Salesforce Account to Applied Epic Client | Account → Client | 1 | create |
| Create New Contact | Salesforce Contact to Applied Epic Contact | Contact → Contact | 1 | create |
Across the 2 default templates: 2 carry insert, 0 carry update, 0 carry delete. A flag decides which operation the process is allowed to perform, not which one it performs on a given record.
2. The process rows the import creates
Importing one of these templates writes one TxDownloaderPro row. The columns the import fills from the template are the ones the operational skill describes: the query, the inbound and outbound mappings and the operation flags are all stored on that row. In-flight state is never in this table — it is in the writeback transaction log (in the operational skill), keyed by its state.
| What the import sets | Where it comes from |
|---|---|
| Query | the template’s default query — section 3 |
| inbound mapping | the template’s default inbound mapping — section 4 |
| outbound mapping | the template’s default outbound mapping — section 5 |
| insert | the template’s own flags — section 1 |
3. What the query retrieves
Query does not have one shape across the product (in the operational skill). For this pair, 2 carry a query statement in the CRM’s own query language. No query text is reproduced here; what follows is what those queries read and filter on.
- Objects read: Account, Contact.
- Marker and key columns the queries name: Commercient AR customer code, External key (custom field). These are the columns a user’s flag lands in and the columns the run writes an outcome back to; which ones are in the filter is what decides whether a record is in scope at all.
- Operators present:
=, a test for an empty value,!=. The operational skill is the authority on the vocabulary; the point here is only which of it these templates use. - Where the filtering happens: in the query, on the CRM side, before anything reaches the source system. Narrowing a template means editing its query — not its mapping.
4. The inbound mapping document
Inbound mapping is a flat object: each member names a field on the source side and its value is a template resolved against the retrieved record’s document (in the operational skill). Of this pair’s 2 default templates, 2 carry a default inbound mapping. A parseable document carries about 15 members.
- Template path roots used: Contact, Account. A path’s first segment has to match the element the engine emits, and the document root itself is never part of the path.
- No line section. These templates map a single record, with no repeating child collection.
5. Result structure — what goes back to the CRM
Outbound mapping is the outbound half: up to four parts, each optional, filled from the source system’s response after the write (in the operational skill). Of this pair’s 2 default templates, 2 carry a parseable default outbound mapping, 0 carry none.
| Part | Filled by | What it addresses | Members present |
|---|---|---|---|
| Part 1 | 2 templates | the record the run is already working with | a map from source path to CRM field |
| Part 2 | 0 templates (2 explicitly null) | the line records under it | — |
| Part 3 | 0 templates (2 explicitly null) | a new record, matched on an external id field | — |
| Part 4 | 0 templates (2 explicitly null) | a different record, addressed by an id field | — |
- CRM fields Part 1 writes to: Commercient AR customer code, External key (custom field). These are the fields on the flagged record that carry the source system’s key or outcome once the write has happened — the names only; what lands in them is the response, per record.
- Response fields it reads them from: Client lookup code, Contact identifier. The map is written source path first, CRM field second (in the operational skill); the wrong way round resolves to the same silent empty string as a mistyped path.
6. Verifying
Read the imported row before a run, not after. The operational skill is the authority on the TxDownloaderPro tools and on the state they report.
The two failures this pair’s templates actually produce: a run that retrieves nothing, which is the query’s own condition and not the mapping; and a record that arrives with fields empty, which is a path that does not match the emitted document.
7. Where this sits
- dlake-txdownloaderpro — the parent: exposure, key scoping, the two tables, its state, the mapping columns, the filter vocabulary, the TxDownloaderPro tools. Read it first.
- dlake-txdownloaderpro-salesforce — the Salesforce destination page, which this page is a child of: the query shape, marker conventions and mapping conventions this destination uses across every ERP, and the ERP table that lists this page and its siblings.
- dlake-integration-setup — registration, CRM choice and the ERP connector, of which writeback is one step.
- dlake-crmpro and dlake-normalsync — the inbound leg, going the other way.
- dlake — general tenant operation.
This page describes the shipped default template set for this pair, and grows as that set does.
How to get started
- Already a customer: the operational skill tells you how to connect, choose what to sync and run it.
Fetch it with
dlake admin get_skill dlake-txdownloaderpro-salesforce/erps/applied-epic, or ask support@commercient.com. - New to Commercient: contact sales@commercient.com. Becoming a customer includes registration and whitelisting, after which the operational skills and tools are available to you.
