CRMPro → Salesforce — Xero: what the shipped templates set up

CRMPro → Salesforce — Xero: what the shipped 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-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. 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: read it first, then come back here for what this source’s own templates set. This page is dlake-crmpro-salesforce/erps/xero.md, and that skill’s ERP table is what points at it. What follows is only what the shipped Xero → Salesforce templates themselves set, read from their Insert_Query, CreateViewQuery and MappingJson. This page grows as the catalogue does.

1. What the templates deliver

Group	Business outcome	Objects	Source tables and views
Get Salesforce User	The templates push User to Salesforce. New records are created, existing ones updated, and records removed in the ERP are deleted.	User	—
DOCUMENT SYNC - XERO INVOICES	ERP INVOICES, INVOICESATTACHMENTS data becomes ContentDocument in Salesforce. New records are created, existing ones updated, and records removed in the ERP are deleted.	ContentDocument	SF_ERP_Salesforce_Clone_Invoices, SF_ERP_Salesforce_Clone_InvoicesAttachments
XERO Credit Notes	ERP CONTACT, CREDITNOTES, CREDITNOTESCONTACT data becomes CommercientSF15__InvoicesCreditNotes__c in Salesforce. New records are created, existing ones updated, and records removed in the ERP are deleted.	CommercientSF15__InvoicesCreditNotes__c	SF_ERP_Salesforce_Clone_CreditNotes, SF_ERP_Salesforce_Clone_CreditNotesPayments, SF_ERP_Salesforce_Clone_CreditNotesContact, SF_ERP_Salesforce_Clone_Contact, SF_ERP_Salesforce_Clone_InvoicesCreditNotes
Account	In addition to creating the Account record from your ERP customer records, Commercient syncs over the entire Accounting AR Customer record into a Commercient AR Customer object which is a Managed Custom Object (MCO). A lookup field is provided to lookup to the default AR Customer record MCO from the Account record. New records are created, existing ones updated, and records removed in the ERP are deleted.	Account, Contact, CommercientSF15__XERO_CONTACT__c	SF_ERP_Salesforce_Clone_Contact, SF_ERP_Salesforce_Clone_ContactAddresses, SF_ERP_Salesforce_Clone_ContactPhones, SF_ERP_Salesforce_Clone_ContactSalesTrackingCategories, SF_ERP_Salesforce_Clone_ContactAccountsPayable, SF_ERP_Salesforce_Clone_ContactAccountsReceivable
Customer Multi Ship Addresses	If you are using multiple ship to addresses for a given AR Customer in your ERP system then you will be able to see all the addresses inside the CRM Account screen in a Commercient Multi Ship To Address MCO related list. New records are created, existing ones updated, and records removed in the ERP are deleted.	CommercientSF15__XERO_ADDRESS__c	SF_ERP_Salesforce_Clone_ContactAddresses, SF_ERP_Salesforce_Clone_Contact
Invoice	Both Open and Historical invoices are synchronized. Open invoice changes, such as a balance change, or a terms change are reflected in the CRM as they sync based on the frequency of the sync you have chosen (e.g. every hour for example). New records are created, existing ones updated, and records removed in the ERP are deleted.	CommercientSF15__XERO_INVOICE__c, CommercientSF15__XERO_LINEITEM__c, CommercientSF15__XERO_PAYMENT__c, CommercientSF15__InvoicesCreditNotes__c	SF_ERP_Salesforce_Clone_Invoices, SF_ERP_Salesforce_Clone_InvoicesContact, SF_ERP_Salesforce_Clone_Contact, SF_ERP_Salesforce_Clone_InvoicesLineItems, SF_ERP_Salesforce_Clone_InvoicesPayments, SF_ERP_Salesforce_Clone_Payments

2. The process rows the templates create

Each template’s Insert_Query writes one CRM_Configuration row. These are the values it sets; a column the inserts never set is not listed.

Display name	CRM_Object_API_Name	CRM_PK_API_Name	Sync_Order	TimeStamp_Prefix	SQL_Query target	field prefix / postfix	Sync_Operation_Type
Get Salesforce User	User	CommercientSF6__SalespersonCode__c	0	vw_XERO_GetUser	1=0	'' / ''	1
Account	Account	CommercientSF__Commercient_ArCustomerCode__c	1	vw_XERO_Account	vw_XERO_Account	'' / ''	1
XERO Customer	CommercientSF15__XERO_CONTACT__c	CommercientSF15__ExternalKey__c	2	vw_XERO_Customer	vw_XERO_Customer	CommercientSF15__ / __c	1
XERO CustomerToAccountLookup	Account	CommercientSF__Commercient_ArCustomerCode__c	3	vw_XERO_CustomerToAccountLookup	vw_XERO_CustomerToAccountLookup	'' / ''	1
XERO Address	CommercientSF15__XERO_ADDRESS__c	CommercientSF15__ExternalKey__c	4	vw_XERO_Address	vw_XERO_Address	CommercientSF15__ / __c	1
XERO Invoice	CommercientSF15__XERO_INVOICE__c	CommercientSF15__ExternalKey__c	5	vw_XERO_Invoice	vw_XERO_Invoice	CommercientSF15__ / __c	1
XERO InvoiceLineItem	CommercientSF15__XERO_LINEITEM__c	CommercientSF15__ExternalKey__c	6	vw_XERO_InvoiceLineItem	vw_XERO_InvoiceLineItem	CommercientSF15__ / __c	1
XERO InvoicePayment	CommercientSF15__XERO_PAYMENT__c	CommercientSF15__ExternalKey__c	7	vw_XERO_InvoicePayment	vw_XERO_InvoicePayment	CommercientSF15__ / __c	1
DOCUMENT SYNC - XERO INVOICES	ContentDocument	—	8	vw_XERO_InvoiceUpload	vw_XERO_InvoiceUpload	'' / ''	5
Contact	Contact	ExternalKey__c	10	vw_XERO_Contact	vw_XERO_Contact	'' / ''	1
XERO Invoice Credit Notes	CommercientSF15__InvoicesCreditNotes__c	CommercientSF15__ExternalKey__c	11	vw_XERO_InvoiceCreditNotes	vw_XERO_InvoiceCreditNotes	CommercientSF15__ / __c	1
XERO Credit Notes	CommercientSF15__InvoicesCreditNotes__c	CommercientSF15__ExternalKey__c	12	vw_XERO_CreditNotes	vw_XERO_CreditNotes	CommercientSF15__ / __c	1

Every one of these inserts Is_Active as 0, so an imported process is inactive until an operator activates it. Across the set they insert Is_Create_Entity 0, Is_Create_Fields 0, Is_Active_Get_Records 0, Is_Active_Delete_Records 0, IsAccountMatching False, Sync_Batch_Size 200. Text columns a template does not use are inserted as '' rather than left NULL. Get_SOQL_Query carries a query on Get Salesforce User, DOCUMENT SYNC - XERO INVOICES, Account, Contact — those rows read records back from Salesforce as well as pushing.

3. The views

Each template creates its view with CreateViewQuery, in the gateway dbo schema. “Change detection” names which of the three kinds dlake-crmpro defines the view’s own WHERE makes it; where a view’s shape is not one of those three the column is left empty and the view’s own WHERE is the authority.

View	Change detection	Repository key	Reads other prefixes	Identity column	Source tables
vw_XERO_Account	insert + update	vw_XERO_Account:	vw_XERO_GetUser:	—	SF_ERP_Salesforce_Clone_Contact, SF_ERP_Salesforce_Clone_ContactAddresses, SF_ERP_Salesforce_Clone_ContactPhones, SF_ERP_Salesforce_Clone_ContactSalesTrackingCategories
vw_XERO_Customer	insert + update	vw_XERO_Customer:	vw_XERO_Account:	ExternalKey	SF_ERP_Salesforce_Clone_Contact, SF_ERP_Salesforce_Clone_ContactAccountsPayable, SF_ERP_Salesforce_Clone_ContactAccountsReceivable
vw_XERO_CustomerToAccountLookup	insert + update	vw_XERO_CustomerToAccountLookup:	vw_XERO_Customer:, vw_XERO_Account:	—	SF_ERP_Salesforce_Clone_Contact
vw_XERO_Address	insert + update	vw_XERO_Address:	vw_XERO_Account:, vw_XERO_Customer:	ExternalKey	SF_ERP_Salesforce_Clone_ContactAddresses, SF_ERP_Salesforce_Clone_Contact
vw_XERO_Invoice	insert + update	vw_XERO_Invoice:	vw_XERO_Account:, vw_XERO_Customer:	ExternalKey	SF_ERP_Salesforce_Clone_Invoices, SF_ERP_Salesforce_Clone_InvoicesContact, SF_ERP_Salesforce_Clone_Contact
vw_XERO_InvoiceLineItem	insert + update	vw_XERO_InvoiceLineItem:	vw_XERO_Invoice:	ExternalKey	SF_ERP_Salesforce_Clone_InvoicesLineItems, SF_ERP_Salesforce_Clone_Invoices
vw_XERO_InvoicePayment	insert + update	vw_XERO_InvoicePayment:	vw_XERO_Customer:, vw_XERO_Invoice:	ExternalKey	SF_ERP_Salesforce_Clone_InvoicesPayments, SF_ERP_Salesforce_Clone_Payments, SF_ERP_Salesforce_Clone_InvoicesContact, SF_ERP_Salesforce_Clone_Contact
vw_XERO_InvoiceUpload	insert + update	vw_XERO_InvoiceUpload:	vw_XERO_Invoice:, LTD:	ExternalKey	SF_ERP_Salesforce_Clone_Invoices, SF_ERP_Salesforce_Clone_InvoicesAttachments
vw_XERO_Contact	insert + update	vw_XERO_Contact:	vw_XERO_Account:	—	SF_ERP_Salesforce_Clone_Contact, SF_ERP_Salesforce_Clone_ContactPhones, SF_ERP_Salesforce_Clone_ContactAddresses
vw_XERO_InvoiceCreditNotes	insert + update	vw_XERO_InvoiceCreditNotes:	vw_XERO_Account:, vw_XERO_Customer:, vw_XERO_Invoice:	ExternalKey	SF_ERP_Salesforce_Clone_InvoicesCreditNotes, SF_ERP_Salesforce_Clone_Invoices, SF_ERP_Salesforce_Clone_InvoicesContact, SF_ERP_Salesforce_Clone_Contact
vw_XERO_CreditNotes	insert + update	vw_XERO_CreditNotes:	vw_XERO_Account:, vw_XERO_Customer:	ExternalKey	SF_ERP_Salesforce_Clone_CreditNotes, SF_ERP_Salesforce_Clone_CreditNotesPayments, SF_ERP_Salesforce_Clone_CreditNotesContact, SF_ERP_Salesforce_Clone_Contact, SF_ERP_Salesforce_Clone_InvoicesCreditNotes

The repository key these templates build is <TimeStamp_Prefix>:<key>. The literal in the view and the TimeStamp_Prefix on the configuration row have to be the same string, case included.

4. Order of work

The templates set Sync_Order from 0 to 12. A run processes active rows in ascending Sync_Order, which is the order the templates put them in:

• 0 — Get Salesforce User
• 1 — Account
• 2 — XERO Customer
• 3 — XERO CustomerToAccountLookup
• 4 — XERO Address
• 5 — XERO Invoice
• 6 — XERO InvoiceLineItem
• 7 — XERO InvoicePayment
• 8 — DOCUMENT SYNC - XERO INVOICES
• 10 — Contact
• 11 — XERO Invoice Credit Notes
• 12 — XERO Credit Notes

These views read another process’s repository prefix, which is what makes the order a dependency order: the row appears in the view only once the process that writes that prefix has run, so a parent flows on one run and its children on the next.

• vw_XERO_InvoiceUpload reads vw_XERO_Invoice:, LTD:; no template in this set writes LTD:
• vw_XERO_CreditNotes reads vw_XERO_Account:, vw_XERO_Customer:
• vw_XERO_Account reads vw_XERO_GetUser:
• vw_XERO_CustomerToAccountLookup reads vw_XERO_Customer:, vw_XERO_Account:
• vw_XERO_Contact reads vw_XERO_Account:
• vw_XERO_Customer reads vw_XERO_Account:
• vw_XERO_Address reads vw_XERO_Account:, vw_XERO_Customer:
• vw_XERO_Invoice reads vw_XERO_Account:, vw_XERO_Customer:
• vw_XERO_InvoiceLineItem reads vw_XERO_Invoice:
• vw_XERO_InvoicePayment reads vw_XERO_Customer:, vw_XERO_Invoice:
• vw_XERO_InvoiceCreditNotes reads vw_XERO_Account:, vw_XERO_Customer:, vw_XERO_Invoice:

5. Field mapping

CRM_FieldList carries one row per pushed column, with Object_Name equal to the CRM_Object_API_Name value — as dlake-crmpro puts it, an object with no CRM_FieldList rows pushes nothing and records no error. Each template carries its intended mapping in MappingJson. Read that with dlake admin crmpro_templates, then check crmpro_field_mapping on the created process before activating it.

Template	Object	Mapped fields	First ERP → Salesforce pairs
Account	Account	13	CommercientSFommercient_ArCustomerCode → CommercientSF__Commercient_ArCustomerCode__c, Phone → Phone, BillingStreet → BillingStreet, BillingCity → BillingCity, BillingStateCode → BillingStateCode
XERO Customer	CommercientSF15__XERO_CONTACT__c	24	Account → Account, AccountNumber → AccountNumber, AccountsPayableTaxType → AccountsPayableTaxType, AccountsReceivableTaxType → AccountsReceivableTaxType, ApBalanceOutstanding → ApBalanceOutstanding
XERO CustomerToAccountLookup	Account	2	CommercientSFommercient_ArCustomerCode → CommercientSF__Commercient_ArCustomerCode__c, CommercientSF15__XERO_Contact → CommercientSF15__XERO_Contact__c
XERO Address	CommercientSF15__XERO_ADDRESS__c	14	Account → Account, XERO_Contact → XERO_Contact__c, AddressLine1 → CommercientSF15__AddressLine1__c, AddressLine2 → CommercientSF15__AddressLine2__c, AddressLine3 → CommercientSF15__AddressLine3__c
XERO Invoice	CommercientSF15__XERO_INVOICE__c	25	Account → Account, XERO_Contact → XERO_Contact, AmountCredited → AmountCredited, AmountDue → CommercientSF15__AmountDue__c, AmountPaid → CommercientSF15__AmountPaid__c
XERO InvoiceLineItem	CommercientSF15__XERO_LINEITEM__c	13	XERO_Invoice → XERO_Invoice, AccountCode → AccountCode, Description → Description, DiscountRate → DiscountRate, InvId → CommercientSF15__InvId__c
XERO InvoicePayment	CommercientSF15__XERO_PAYMENT__c	13	XERO_Contact → XERO_Contact, Invoice1 → Invoice1, Amount → CommercientSF15__Amount__c, BankAmount → CommercientSF15__BankAmount__c, CurrencyRate → CurrencyRate
DOCUMENT SYNC - XERO INVOICES	ContentDocument	6	ID → ID, FileDisplayName → FileDisplayName, Body → Body, Description → Description, ParentID → ParentID
Contact	Contact	12	FirstName → FirstName, LastName → LastName, AccountID → AccountID, Email → Email, Phone → Phone
XERO Invoice Credit Notes	CommercientSF15__InvoicesCreditNotes__c	13	Account → Account, XERO_Contact → XERO_Contact, XERO_Invoice → XERO_Invoice, CreditNoteID → CommercientSF15__CreditNoteID__c, CreditNoteNumber → CommercientSF15__CreditNoteNumber__c
XERO Credit Notes	CommercientSF15__InvoicesCreditNotes__c	11	Account → Account, XERO_Contact → XERO_Contact, CreditNoteID → CommercientSF15__CreditNoteID__c, CreditNoteNumber → CommercientSF15__CreditNoteNumber__c, ID → CommercientSF15__ID__c

6. Community templates

The catalogue carries 23 community templates for this pair. A community template is authored in a tenant rather than shipped with the product, and it imports the same way as any other. Its own names, notes, field mapping and SQL are tenant content, so what this section states is what the set amounts to: how many templates there are, what they default to doing, which destination objects they write and which groups they fall in. They are not part of the shipped set described above.

• Templates: 23
• Default operations: insert on 23, update on 23, delete on 23
• Marked circular-sync: 1
• Licence groups they span: 6
• Destination objects: Account, CommercientSF15__InvoicesCreditNotes__c, CommercientSF15__XERO_ADDRESS__c, CommercientSF15__XERO_CONTACT__c, CommercientSF15__XERO_INVOICE__c, CommercientSF15__XERO_LINEITEM__c, CommercientSF15__XERO_PAYMENT__c, Contact, ContentDocument, User
• Object display names: Account, Contact, DOCUMENT SYNC - XERO INVOICES, XERO Address, XERO Credit Notes, XERO Customer, XERO CustomerToAccountLookup, XERO Invoice, XERO Invoice Credit Notes, XERO InvoiceLineItem, XERO InvoicePayment, Get Salesforce User
• Template groups: Account, Invoice, Customer Multi Ship Addresses

A community template is imported the way a shipped one is, and the same rules apply to what it creates: read the process it creates with crmpro_get_process, its mapping with crmpro_field_mapping, and the view it selects from, before activating it.

7. 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 ::.

The prefixes these templates set:

• vw_XERO_GetUser
• vw_XERO_InvoiceUpload
• vw_XERO_CreditNotes
• vw_XERO_Account
• vw_XERO_CustomerToAccountLookup
• vw_XERO_Contact
• vw_XERO_Customer
• vw_XERO_Address
• vw_XERO_Invoice
• vw_XERO_InvoiceLineItem
• vw_XERO_InvoicePayment
• vw_XERO_InvoiceCreditNotes

8. 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 page adds what the shipped Xero → Salesforce templates set up. 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.