TxDownloaderPro ← Salesforce — Exact Globe Next: what the shipped default templates set up

TxDownloaderPro ← Salesforce — Exact Globe Next: what the shipped default 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-txdownloaderpro is the parent skill and the authority for everything general: what the writeback objects are and how they are exposed to the Data API (§1–§7), how a key is scoped to them, the TxDownloaderPro configuration table and the TxDownloaderProTrans transaction table and their columns (§9, §10), the SFUpdated state machine (§10), the field-mapping columns ProcessStructure, ResultStructure, XMLResult, ERPResponse, JsonRequest and JsonResponse and the {{Object.Field}} template paths that read them (§11), the filter-operator vocabulary (§12), and the txdownloaderpro_* tools that are the preferred way to configure any of it (§14). Read it first; this page does not repeat it. dlake-txdownloaderpro-salesforce is the Salesforce page and carries the destination-side 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. This page is dlake-txdownloaderpro-salesforce/erps/exact-globe-next.md, and that skill’s ERP table is what points at it.

What follows is only what the shipped default templates for this pair themselves set, described from their DefaultQuery, DefaultProcessStructure and DefaultResultStructure 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. The community templates the catalogue also carries for this pair are listed in a section of their own below, by count, object and name only.

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 IsInsert, IsUpdate and IsDelete flags over that process’s templates.

Process	What it delivers	Source → destination	Templates	Operations
TxDownloaderPro_129_2_1	Salesforce Contact to Exact Globe Next Contact	Contact → Contact	1	create
TxDownloaderPro_129_3_1	Salesforce Order to Exact Globe Next Sales Order	Order → SalesOrder	1	create
TxDownloaderPro_129_4_1	Salesforce Product to Exact Globe Next Product	Product2 → Item	1	create

Across the 3 default templates: 3 carry IsInsert, 0 carry IsUpdate, 0 carry IsDelete. 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 parent’s §9 describes: the query goes into Query, the inbound mapping into ProcessStructure, the outbound mapping into ResultStructure, and the operation flags onto the row. In-flight state is never in this table — it is in TxDownloaderProTrans (parent §10), keyed by SFUpdated.

A default template carries no TxDownloaderDllName and no template name of its own. It is identified by its field-process version, and the version is what supplies the DLL on a create. That is where erpProcessId comes from, so a create against the wrong version produces a row that never matches a run.

What the import sets	Where it comes from
Query	the template’s DefaultQuery — section 3
ProcessStructure	the template’s DefaultProcessStructure — section 4
ResultStructure	the template’s DefaultResultStructure — section 5
IsInsert / IsUpdate / IsDelete	the template’s own flags — section 1
the DLL and erpProcessId	the field-process version, not the template

The field-process versions this pair’s default templates belong to: TxDownloaderPro_129_2, TxDownloaderPro_129_3, TxDownloaderPro_129_4.

3. What the query retrieves

Query does not have one shape across the product (parent §9). For this pair, 3 carry a SELECT 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: Contact, OrderItems, PricebookEntries.
• Child collections pulled in the same query: OrderItems, PricebookEntries. A header retrieved without its lines is a query that does not name the child collection.
• Marker and key columns the queries name: CommercientSF__Commercient_ArCustomerCode__c, ExternalKey__c. 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 WHERE is what decides whether a record is in scope at all.
• Operators present: !=, =, AND, an empty-string test. The parent’s §12 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

ProcessStructure is a flat JSON object: each member names a field on the source side and its value is a template resolved against the retrieved record’s XML document (parent §11). Of this pair’s 3 default templates, 3 carry a DefaultProcessStructure. A parseable document carries about 13 members.

• Template path roots used: Order, Contact, Product2, OrderItems. A path’s first segment has to match the element the engine emits, and the document root itself is never part of the path.
• Line. section members present: Line.mainXml, Line.ItemCode, Line.Description, Line.Quantity, Line.Price. 1 template name the collection through Line.mainXml; the members beside it are resolved against that collection’s own root rather than through the header.
• $FUN_ value tokens the documents carry: $FUN_UNESCAPEXML. The names are what the templates carry; no semantics are claimed for them here — the parent’s §12 is explicit that the platform-side resolver is dotted path substitution only, and these tokens are evaluated on the customer’s own host.

5. Result structure — what goes back to the CRM

ResultStructure is the outbound half: up to four parts, each optional, filled from the source system’s response after the write (parent §11). Of this pair’s 3 default templates, 3 carry a parseable DefaultResultStructure, 0 carry none.

Part	Filled by	What it addresses	Members present
Part1	3 templates	the record the run is already working with	a source-path-to-CRM-field map
Part2	0 templates (3 explicitly null)	the child/line records under it	—
Part3	0 templates (3 explicitly null)	a new record, matched on an external id field	—
Part4	0 templates (3 explicitly null)	a different record, addressed by an id field	—

• CRM fields Part1 writes to: ExternalKey__c. 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: ContactID, SalesOrderNumber, ID. The map is written source-path first, CRM-field second (parent §11); the wrong way round resolves to the same silent empty string as a mistyped path.

6. Community templates

The catalogue carries community templates for this pair as well as the default set above: templates written on a tenant rather than shipped. Their content is not read and not described here — no query, no mapping document, no field. What this section states is how many there are, which objects they start from, what they are called where the name is a product artefact name, and which field-process versions they belong to.

• How many: 24 community templates, across 4 field-process versions.
• Operations: 12 carry IsInsert, 7 carry IsUpdate, 0 carry IsDelete. A flag decides which operation the template is allowed to perform, as it does for a default template.

Source → destination	Templates
— → —	11
Account → —	10
Item → —	3

None of these rows carries a destination object name in the catalogue, so the destination side of every shape above is empty.

• Template names the catalogue carries: Update Customer (5), Create New Contact (4), Create New Customer (4), Create New Sales Order (4), New Contact (1), New Customer (1), New PriceBook (1), New Product (1), New Quote (1), Update Contact (1), Update Product (1).
• Field-process versions they belong to: TxDownloaderPro_129_1, TxDownloaderPro_129_2, TxDownloaderPro_129_3, TxDownloaderPro_129_4.

Importing one of these writes the same TxDownloaderPro row that importing a default template writes (parent §9); what differs is where the template came from, not how it is stored. What any one of them contains is read from the imported row itself, with the tools below.

7. Verifying

Read the imported row before a run, not after. The parent’s §14 is the authority on these tools and §10 on the state they report.

# the processes this tenant has, with their unresolved-error counts
dlake admin txdownloaderpro_list_processes

# one process in its edit shape, including the query and both mapping documents
dlake admin txdownloaderpro_get_process --processId <id>

# run the SAVED query against the live CRM and render one record as the engine’s XML
dlake admin txdownloaderpro_preview_xml --processId <id>

# the state breakdown the parent §10 reads
dlake txdownloaderpro transactions <processId> --status <state>

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. Both are read through txdownloaderpro_preview_xml, against a real record.

8. Where this sits

• dlake-txdownloaderpro — the parent: exposure, key scoping, the two tables, SFUpdated, 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.