Source ERP · 55 of 69
TxDownloaderPro ← Salesforce — Sage 50 US: 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/sage-50-us". 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/sage-50-us-salesforce/.
TxDownloaderPro ← Salesforce — Sage 50 US: 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/sage-50-us (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. 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 insert, update and delete flags over that process’s templates.
| Process | What it delivers | Source → destination | Templates | Operations |
|---|---|---|---|---|
| Update Sales order | Salesforce Order to Sage 50 US Sales Order - Update Order | Order, Opportunity, Quote → Order | 6 | create |
| Create New Sales invoice | Salesforce Opportunity to Sage 50 US Sales Invoice | — | 3 | create |
| Create New Sales order | Salesforce Order to Sage 50 US Sales Order | — | 3 | create |
| Delete Quote | Salesforce Quote to Sage 50 US Quote - Delete Quote | Quote, Order, Opportunity → Quote | 3 | delete |
| Update Sales invoice | Salesforce Opportunity to Sage 50 US Sales Invoice - Update Invoice | Opportunity, Order, Quote → Invoice | 3 | update |
| Create New Customer | Salesforce Account to Sage 50 US Customer | Account → Customer | 2 | create |
| Create New Vendor | Salesforce Account to Sage 50 US Vendor | Account → Vendor | 2 | create |
| Delete Sales invoice | Salesforce Quote to Sage 50 US Invoice - Delete Invoice | — | 2 | delete |
| Delete Sales order | Salesforce Order to Sage 50 US Sales Order - Delete Sales Order | — | 2 | delete |
| Update Vendor | Salesforce Account to Sage 50 US Vendor | Account → Vendor | 2 | update |
| Create Customer contact | Salesforce Contact to Sage 50 US Contact | Contact → Contact | 1 | create |
| Create New Product | Salesforce Product or Item to Sage 50 US Product | Product → Item | 1 | create |
| Create New Purchase Entry | Salesforce Order to Sage 50 US Purchase Entry | Order → Purchase Order Entry | 1 | create |
| Create New Purchase order | Salesforce Order to Sage 50 US Purchase Order | Order → Purchase Order | 1 | create |
| Create New Quote | Salesforce Quote to Sage 50 US Quote | Quote → Quote | 1 | create |
| Create or Update Ship To Customer Address | — | Commercient Sage 50 US Address Managed Custom Object → Shipping address | 1 | create |
| Delete Customer | Salesforce Customer to Sage 50 US Account - Delete Customer | — | 1 | delete |
| Delete Product | Salesforce Product to Sage 50 US item - Delete Item | Product → Item | 1 | delete |
| Delete Purchase order | Salesforce Order to Sage 50 US Purchase Order - Delete Purchase Order | Order → Purchase Order | 1 | delete |
| Delete Vendor | Delete Salesforce Account to Delete Sage 50 US Vendor | Account → Vendor | 1 | delete |
| Update Customer | Salesforce Account to Sage 50 US Customer - Update Customer | Account → Customer | 1 | update |
| Update Product | Salesforce Product or Item to Sage 50 US Product - Update Product | Product → Item | 1 | update |
| Update Purchase order | Salesforce Update Order to Sage 50 US Update Purchase Order | Order → Purchase Order | 1 | update |
| Update Quote | Salesforce Update Quote to Sage 50 US Update Quote | Quote → Quote | 1 | update |
Across the 42 default templates: 16 carry insert, 16 carry update, 11 carry delete. A flag decides which operation the process is allowed to perform, not which one it performs on a given record. 4 catalogue descriptions were not printed because they are placeholders or carry text that is not ours to publish.
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 |
The process versions this pair’s default templates belong to: and 3 more.
3 of these template rows carry a licence group, so what a given tenant is offered in the picker is narrower than what the catalogue holds.
3. What the query retrieves
Query does not have one shape across the product (in the operational skill). For this pair, 42 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: Contact, Account, Product, order products, quote line items, opportunity line items, Commercient Sage 50 US Address Managed Custom Object, Order, Quote, Opportunity.
- Child collections pulled in the same query: order products, quote line items, opportunity line items. A header retrieved without its lines is a query that does not name the child collection.
- Marker and key columns the queries name: Commercient AR customer code, External key (custom field), Commercient account (related record), Commercient address line 1, Commercient address line 2, Commercient city, Commercient country, Commercient external key, Commercient customer (related record), Commercient name, Commercient state, Commercient address type number, Commercient tax code, Commercient zip code, Commercient Sage 50 US Address Managed Custom Object, Commercient message. 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,!=, and, a null test,>. 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 42 default templates, 42 carry a default inbound mapping; 5 of those do not parse as and are counted but not described. A parseable document carries about 10 members.
- Template path roots used: Order, Account, Quote, Opportunity, quote line items, opportunity line items, order products, order line items, Commercient Sage 50 US Address Managed Custom Object, Contact, Product, quote line items nested under the quote. 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 members present: line quantity, a collection member, line item identifier field, line unit price, line description, line general ledger account, line tax type, line amount, line stocking quantity, line sales order description, line item identifier, line unit price. 15 templates name the collection through a collection member; the members beside it are resolved against that collection’s own root rather than through the header.
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 42 default templates, 12 carry a parseable default outbound mapping, 30 carry none.
| Part | Filled by | What it addresses | Members present |
|---|---|---|---|
| Part 1 | 12 templates | the record the run is already working with | a map from source path to CRM field |
| Part 2 | 0 templates (12 explicitly null) | the line records under it | — |
| Part 3 | 0 templates (12 explicitly null) | a new record, matched on an external id field | — |
| Part 4 | 0 templates (12 explicitly null) | a different record, addressed by an id field | — |
- CRM fields Part 1 writes to: Commercient AR customer code, External key (custom field), Commercient address type number. 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: Customer identifier, returned vendor identifier, returned purchase order number, returned quote number, returned invoice number, returned sequence number. 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. 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 process versions they belong to.
- How many: 76 community templates, across 22 process versions.
- Operations: 53 carry insert, 16 carry update, 0 carry delete. A flag decides which operation the template is allowed to perform, as it does for a default template.
| Source → destination | Templates |
|---|---|
| Customer → — | 23 |
| Sales Order → — | 9 |
| Vendor → — | 8 |
| Sales Invoice → — | 7 |
| Contact → — | 6 |
| General Journal → — | 5 |
| Item → — | 4 |
| Job → — | 4 |
| Payment → — | 3 |
| Purcahse Order Entry → — | 2 |
| Purchase Order → — | 2 |
| Quote → — | 1 |
| Receipt → — | 1 |
| Ship to → — | 1 |
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: Create New Customer (10), Update Customer (5), Create Customer (4), Create Sales Order (4), Create Contact (3), Create New Sales Order (3), New Account (3), Create Invoice (2), Create New Product (2), Create New Sales Invoice (2), Create Purchase Order (2), Create Vendor (2), New Invoice (2), Update Job (2), Create general ledger Journal (1), Create Job (1), Create New Account (1), Create New Bill (1), Create New Contact (1), Create New Customer Contact (1), Create New general ledger Entry (1), Create New general ledger Entry 2 (1), Create New Invoice (1), Create New Payment 1099 (1), and 12 more.
- Names not reproduced: 8 of these templates carry a name that is not a product artefact name, and it is not printed here.
Importing one of these writes the same TxDownloaderPro row that importing a default template writes (in the operational skill); 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.
7. 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.
8. 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/sage-50-us, 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.
