CRMPro → Salesforce — MYOB AccountRight: what the shipped templates set up

CRMPro → Salesforce — MYOB AccountRight: 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/myob-accountright.md, and that skill’s ERP table is what points at it. What follows is only what the shipped MYOB AccountRight → 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 USER	The templates push users to Salesforce. New records are created, existing ones updated, and records removed in the ERP are deleted.	users	—
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, CommercientSF24__MYOX_Customers__c, CommercientSF24_MYOX_SalesPerson__c	SF_ERP_Salesforce_Clone_MYOX_Customers, SF_ERP_Salesforce_Clone_MYOX_CustomerAddresses, SF_ERP_Salesforce_Clone_MYOX_Cards, SF_ERP_Salesforce_Clone_MYOX_CardAddresses, SF_ERP_Salesforce_Clone_MYOX_Employees, SF_ERP_Salesforce_Clone_MYOX_EmployeeAddresses
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. Existing records are updated only — nothing is created and nothing is deleted.	CommercientSF24__MYOX_CustomerAddresses__c	SF_ERP_Salesforce_Clone_MYOX_CustomerAddresses
Product	The templates push CommercientSF24__MYOX_Items__c, Product2 to Salesforce. Existing records are updated only — nothing is created and nothing is deleted.	CommercientSF24__MYOX_Items__c, Product2	SF_ERP_Salesforce_Clone_MYOX_Items
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). Existing records are updated only — nothing is created and nothing is deleted.	CommercientSF24__MYOX_ItemSales__c, CommercientSF24__MYOX_ItemSaleLines__c	SF_ERP_Salesforce_Clone_MYOX_ItemSales, CommercientFlags, SF_ERP_Salesforce_Clone_MYOX_ItemSaleLines
Pricebook	The templates push PricebookEntry to Salesforce. New records are created and existing ones updated; none are deleted.	PricebookEntry	SF_ERP_Salesforce_Clone_MYOX_Items, SF_ERP_Salesforce_Clone_MYOX_ItemPriceMatrixDetails
Salesorder	Commercient will sync the Sales Orders from the ERP Sales Order Entry module to the Commercient Sales Order Header (MCO) objects in CRM. In the CRM, customer service and sales people can visualize the status of the order such as on hold, backorder, forward order, scheduled for delivery, whether it has shipped, and completion status. Existing records are updated only — nothing is created and nothing is deleted.	CommercientSF24__MYOX_ItemSalesOrders__c, CommercientSF24__MYOX_ItemSalesOrderLines__c	SF_ERP_Salesforce_Clone_MYOX_ItemSalesOrders, CommercientFlags, SF_ERP_Salesforce_Clone_MYOX_ItemSalesOrderLines

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 USER	users	—	0	vw_MYOBACCOUNTRIGHT_User	1=0	'' / ''	1
MYOB SalesPerson	CommercientSF24_MYOX_SalesPerson__c	ExternalKey__c	1	vw_MYOBACCOUNTRIGHT_SalesPerson	vw_MYOBACCOUNTRIGHT_SalesPerson	'' / __c	1
Account	Account	CommercientSF__Commercient_ArCustomerCode__c	3	vw_MYOBACCOUNTRIGHT_Account	vw_MYOBACCOUNTRIGHT_Account	'' / ''	1
Customer	CommercientSF24__MYOX_Customers__c	CommercientSF24__ExternalKey__c	4	vw_MYOBACCOUNTRIGHT_Customer	vw_MYOBACCOUNTRIGHT_Customer	CommercientSF24__ / __c	1
CustomerToAccount Reverse Lookup	Account	CommercientSF__Commercient_ArCustomerCode__c	5	vw_MYOBACCOUNTRIGHT_CustomerToAccountLookup	vw_MYOBACCOUNTRIGHT_CustomerToAccountLookup	'' / ''	1
Contact	Contact	ExternalKey__c	6	vw_MYOBACCOUNTRIGHT_Contact	vw_MYOBACCOUNTRIGHT_Contact	'' / ''	1
Customer Address	CommercientSF24__MYOX_CustomerAddresses__c	CommercientSF24__ExternalKey__c	6	vw_MYOBACCOUNTRIGHT_CustomerAddress	vw_MYOBACCOUNTRIGHT_CustomerAddress	CommercientSF24__ / __c	1
Product	Product2	CommercientSF__ExternalKey__c	7	vw_MYOBACCOUNTRIGHT_Product	vw_MYOBACCOUNTRIGHT_Product	'' / ''	1
Item	CommercientSF24__MYOX_Items__c	CommercientSF24__ExternalKey__c	8	vw_MYOBACCOUNTRIGHT_Items	vw_MYOBACCOUNTRIGHT_Items	CommercientSF24__ / __c	1
ItemToProduct Reverse Lookup	Product2	CommercientSF__ExternalKey__c	9	vw_MYOBACCOUNTRIGHT_ProductToItemMastertLookup	vw_MYOBACCOUNTRIGHT_ProductToItemMastertLookup	'' / ''	1
Sales Order	CommercientSF24__MYOX_ItemSalesOrders__c	CommercientSF24__ExternalKey__c	10	vw_MYOBACCOUNTRIGHT_SalesOrders	vw_MYOBACCOUNTRIGHT_SalesOrders	CommercientSF24__ / __c	1
Sales Order Lines	CommercientSF24__MYOX_ItemSalesOrderLines__c	CommercientSF24__ExternalKey__c	11	vw_MYOBACCOUNTRIGHT_SalesOrderLines	vw_MYOBACCOUNTRIGHT_SalesOrderLines	CommercientSF24__ / __c	1
Sales Invoice	CommercientSF24__MYOX_ItemSales__c	CommercientSF24__ExternalKey__c	12	vw_MYOBACCOUNTRIGHT_SalesInvoice	vw_MYOBACCOUNTRIGHT_SalesInvoice	CommercientSF24__ / __c	1
Sales Invoice Lines	CommercientSF24__MYOX_ItemSaleLines__c	CommercientSF24__ExternalKey__c	13	vw_MYOBACCOUNTRIGHT_SalesInvoiceLines	vw_MYOBACCOUNTRIGHT_SalesInvoiceLines	CommercientSF24__ / __c	1
Standard Pricebook Create	PricebookEntry	ExternalKey__c	14	vw_MYOBACCOUNTRIGHT_ProductPriceBook	vw_MYOBACCOUNTRIGHT_StandardPriceBookCreate	'' / ''	1
Standard Pricebook Update	PricebookEntry	ExternalKey__c	15	vw_MYOBACCOUNTRIGHT_ProductPriceBook	vw_MYOBACCOUNTRIGHT_StandardPriceBookUpdate	'' / ''	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, 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 USER, Account, Standard Pricebook Create, Product — 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_MYOBACCOUNTRIGHT_SalesPerson	insert + update	vw_MYOBACCOUNTRIGHT_SalesPerson:	SNZ:	ExternalKey	SF_ERP_Salesforce_Clone_MYOX_Employees, SF_ERP_Salesforce_Clone_MYOX_EmployeeAddresses
vw_MYOBACCOUNTRIGHT_Account	insert + update	vw_MYOBACCOUNTRIGHT_Account:	vw_MYOBACCOUNTRIGHT_User:	—	SF_ERP_Salesforce_Clone_MYOX_Customers, SF_ERP_Salesforce_Clone_MYOX_CustomerAddresses
vw_MYOBACCOUNTRIGHT_Customer	insert + update	vw_MYOBACCOUNTRIGHT_Customer:	vw_MYOBACCOUNTRIGHT_Account:	—	SF_ERP_Salesforce_Clone_MYOX_Customers
vw_MYOBACCOUNTRIGHT_CustomerToAccountLookup	insert + update	vw_MYOBACCOUNTRIGHT_CustomerToAccountLookup:	vw_MYOBACCOUNTRIGHT_Customer:	—	SF_ERP_Salesforce_Clone_MYOX_Customers
vw_MYOBACCOUNTRIGHT_Contact	insert + update	vw_MYOBACCOUNTRIGHT_Contact:	vw_MYOBACCOUNTRIGHT_Account:, SNZ:	Externalkey__c	SF_ERP_Salesforce_Clone_MYOX_Cards, SF_ERP_Salesforce_Clone_MYOX_CardAddresses, SF_ERP_Salesforce_Clone_MYOX_Customers
vw_MYOBACCOUNTRIGHT_CustomerAddress	insert + update	vw_MYOBACCOUNTRIGHT_CustomerAddress:	vw_MYOBACCOUNTRIGHT_Account:, vw_MYOBACCOUNTRIGHT_Customer:	—	SF_ERP_Salesforce_Clone_MYOX_CustomerAddresses
vw_MYOBACCOUNTRIGHT_Product	insert + update	vw_MYOBACCOUNTRIGHT_Product:	—	CommercientSF__ExternalKey__c	SF_ERP_Salesforce_Clone_MYOX_Items
vw_MYOBACCOUNTRIGHT_Items	insert + update	vw_MYOBACCOUNTRIGHT_Items:	vw_MYOBACCOUNTRIGHT_Product:	—	SF_ERP_Salesforce_Clone_MYOX_Items
vw_MYOBACCOUNTRIGHT_ProductToItemMastertLookup	insert + update	vw_MYOBACCOUNTRIGHT_ProductToItemMastertLookup:	vw_MYOBACCOUNTRIGHT_Items:	CommercientSF__ExternalKey__c	SF_ERP_Salesforce_Clone_MYOX_Items
vw_MYOBACCOUNTRIGHT_SalesOrders	insert + update	vw_MYOBACCOUNTRIGHT_SalesOrders:	vw_MYOBACCOUNTRIGHT_Account:, vw_MYOBACCOUNTRIGHT_Customer:	—	SF_ERP_Salesforce_Clone_MYOX_ItemSalesOrders, CommercientFlags
vw_MYOBACCOUNTRIGHT_SalesOrderLines	insert + update	vw_MYOBACCOUNTRIGHT_SalesOrderLines:	vw_MYOBACCOUNTRIGHT_SalesOrders:, vw_MYOBACCOUNTRIGHT_Product:, vw_MYOBACCOUNTRIGHT_Items:	—	SF_ERP_Salesforce_Clone_MYOX_ItemSalesOrderLines
vw_MYOBACCOUNTRIGHT_SalesInvoice	insert + update	vw_MYOBACCOUNTRIGHT_SalesInvoice:	vw_MYOBACCOUNTRIGHT_Account:, vw_MYOBACCOUNTRIGHT_Customer:	—	SF_ERP_Salesforce_Clone_MYOX_ItemSales, CommercientFlags
vw_MYOBACCOUNTRIGHT_SalesInvoiceLines	insert + update	vw_MYOBACCOUNTRIGHT_SalesInvoiceLines:	vw_MYOBACCOUNTRIGHT_SalesInvoice:, vw_MYOBACCOUNTRIGHT_Product:, vw_MYOBACCOUNTRIGHT_Items:	—	SF_ERP_Salesforce_Clone_MYOX_ItemSaleLines
vw_MYOBACCOUNTRIGHT_StandardPriceBookCreate	insert + update	vw_MYOBACCOUNTRIGHT_ProductPriceBook:	vw_MYOBACCOUNTRIGHT_Product:	ExternalKey__c	SF_ERP_Salesforce_Clone_MYOX_Items, SF_ERP_Salesforce_Clone_MYOX_ItemPriceMatrixDetails
vw_MYOBACCOUNTRIGHT_StandardPriceBookUpdate	insert + update	vw_MYOBACCOUNTRIGHT_ProductPriceBook:	vw_MYOBACCOUNTRIGHT_Product:	ExternalKey__c	SF_ERP_Salesforce_Clone_MYOX_Items, SF_ERP_Salesforce_Clone_MYOX_ItemPriceMatrixDetails

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 15. A run processes active rows in ascending Sync_Order, which is the order the templates put them in:

• 0 — GET USER
• 1 — MYOB SalesPerson
• 3 — Account
• 4 — Customer
• 5 — CustomerToAccount Reverse Lookup
• 6 — Contact, Customer Address
• 7 — Product
• 8 — Item
• 9 — ItemToProduct Reverse Lookup
• 10 — Sales Order
• 11 — Sales Order Lines
• 12 — Sales Invoice
• 13 — Sales Invoice Lines
• 14 — Standard Pricebook Create
• 15 — Standard Pricebook Update

Several of these rows share a Sync_Order value: each template group carries its own numbering, so give the imported processes an order across the whole set rather than taking the template values as one.

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_MYOBACCOUNTRIGHT_Account reads vw_MYOBACCOUNTRIGHT_User:
• vw_MYOBACCOUNTRIGHT_CustomerToAccountLookup reads vw_MYOBACCOUNTRIGHT_Customer:
• vw_MYOBACCOUNTRIGHT_Contact reads vw_MYOBACCOUNTRIGHT_Account:, SNZ:; no template in this set writes SNZ:
• vw_MYOBACCOUNTRIGHT_Customer reads vw_MYOBACCOUNTRIGHT_Account:
• vw_MYOBACCOUNTRIGHT_CustomerAddress reads vw_MYOBACCOUNTRIGHT_Account:, vw_MYOBACCOUNTRIGHT_Customer:
• vw_MYOBACCOUNTRIGHT_Items reads vw_MYOBACCOUNTRIGHT_Product:
• vw_MYOBACCOUNTRIGHT_SalesInvoice reads vw_MYOBACCOUNTRIGHT_Account:, vw_MYOBACCOUNTRIGHT_Customer:
• vw_MYOBACCOUNTRIGHT_SalesInvoiceLines reads vw_MYOBACCOUNTRIGHT_SalesInvoice:, vw_MYOBACCOUNTRIGHT_Product:, vw_MYOBACCOUNTRIGHT_Items:
• vw_MYOBACCOUNTRIGHT_StandardPriceBookCreate reads vw_MYOBACCOUNTRIGHT_Product:
• vw_MYOBACCOUNTRIGHT_StandardPriceBookUpdate reads vw_MYOBACCOUNTRIGHT_Product:
• vw_MYOBACCOUNTRIGHT_ProductToItemMastertLookup reads vw_MYOBACCOUNTRIGHT_Items:
• vw_MYOBACCOUNTRIGHT_SalesOrders reads vw_MYOBACCOUNTRIGHT_Account:, vw_MYOBACCOUNTRIGHT_Customer:
• vw_MYOBACCOUNTRIGHT_SalesOrderLines reads vw_MYOBACCOUNTRIGHT_SalesOrders:, vw_MYOBACCOUNTRIGHT_Product:, vw_MYOBACCOUNTRIGHT_Items:
• vw_MYOBACCOUNTRIGHT_SalesPerson reads SNZ:; no template in this set writes SNZ:

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
MYOB SalesPerson	CommercientSF24_MYOX_SalesPerson__c	38	CompanyRecordID → CompanyRecordID, EmployeeUID → EmployeeUID__c, ETag → ETag__c, CompanyName → CompanyName__c, CurrentBalance → CurrentBalance
Account	Account	13	CompanyRecordID, CustomerUID → CommercientSF__Commercient_ArCustomerCode__c, CompanyName, LastName → Name, Phone1 → Phone, StreetLine1, StreetLine2, StreetLine3, StreetLine4 → BillingStreet, City → BillingCity
Customer	CommercientSF24__MYOX_Customers__c	64	CompanyRecordID,CustomerUID → CommercientSF24__ExternalKey__c, CompanyName,LastName → Name, SFDCID → Account, CompanyRecordID → CommercientSF24__CompanyRecordID__c, CustomerUID → CommercientSF24__CustomerUID__c
CustomerToAccount Reverse Lookup	Account	2	CompanyRecordID, CustomerUID → CommercientSF__Commercient_ArCustomerCode__c, SFDCID → CommercientSF24__Acumatica_Cloud_Customer__c
Contact	Contact	11	Fax → Fax, Email → Email, Phone → Phone, MailingStreet → MailingStreet, MailingCity → MailingCity
Customer Address	CommercientSF24__MYOX_CustomerAddresses__c	28	CompanyRecordID, CustomerUID, Location → CommercientSF24__ExternalKey__c, CustomerCompanyName, CustomerLastName, Location → Name, SFDCID → Account, SFDCID → Acumatica_Cloud_Customer, CompanyRecordID → CompanyRecordID
Product	Product2	5	CompanyRecordID,ItemUID → CommercientSF__ExternalKey__c, Name → Name, Number → ProductCode, IsActive → IsActive, Description → Description
Item	CommercientSF24__MYOX_Items__c	59	CompanyRecordID,ItemUID → CommercientSF24__ExternalKey__c, Name → Name, SFDCID → Product, CompanyRecordID → CommercientSF24__CompanyRecordID__c, ItemUID → CommercientSF24__ItemUID__c
ItemToProduct Reverse Lookup	Product2	2	CompanyRecordID, ItemUID → CommercientSF__ExternalKey__c, SFDCID → CommercientSF24__Acumatica_Cloud_Item__c
Sales Order	CommercientSF24__MYOX_ItemSalesOrders__c	53	CompanyRecordID, SalesOrderUID → CommercientSF24__ExternalKey__c, SalesOrderNumber → Name, CompanyRecordID, CustomerUID → Account, CompanyRecordID, CustomerUID → Acumatica_Cloud_Customer, CompanyRecordID → CommercientSF24__CompanyRecordID__c
Sales Order Lines	CommercientSF24__MYOX_ItemSalesOrderLines__c	25	CompanyRecordID, SalesOrderUID, RowID → CommercientSF24__ExternalKey__c, SalesOrderNumber, Index → Name, SFDCID → Acumatica_Cloud_Sales_Order, SFDCID → Product, SFDCID → Acumatica_Cloud_Item
Sales Invoice	CommercientSF24__MYOX_ItemSales__c	58	CompanyRecordID,SaleUID → CommercientSF24__ExternalKey__c, Number → Name, CompanyRecordID,CustomerUID → Account, CompanyRecordID,CustomerUID → Acumatica_Cloud_Customer, InvoiceType → InvoiceType
Sales Invoice Lines	CommercientSF24__MYOX_ItemSaleLines__c	28	CompanyRecordID, SaleUID, RowID → CommercientSF24__ExternalKey__c, Number, Index → Name, SFDCID → Acumatica_Cloud_Sales_Invoice, SFDCID → Product, SFDCID → Acumatica_Cloud_Item
Standard Pricebook Create	PricebookEntry	5	CompanyRecordID, Number → ExternalKey__c, SFDCID → Product2ID, IsActive → IsActive, LevelA → UnitPrice, TimeStamp → TimeStamp
Standard Pricebook Update	PricebookEntry	4	CompanyRecordID, Number → ExternalKey__c, IsActive → IsActive, LevelA → UnitPrice, TimeStamp → TimeStamp

6. Community templates

The catalogue carries 123 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: 123
• Default operations: insert on 123, update on 123, delete on 123
• Marked circular-sync: 4
• Licence groups they span: 11
• Destination objects: Account, Product2, PricebookEntry, CommercientSF24__MYOX_Customers__c, Contact, CommercientSF24__MYOX_CustomerAddresses__c, CommercientSF24__MYOX_Items__c, CommercientSF24__MYOX_ItemSales__c, CommercientSF24__MYOX_ItemSaleLines__c, CommercientSF24__MYOX_ItemSalesOrderLines__c, CommercientSF24__MYOX_ItemSalesOrders__c, CommercientSF24_MYOX_SalesPerson__c, ContentDocument, Order, OrderItem, CommercientSF24_MYOX_Contact_Address__c, CommercientSF24_MYOX_SalesInvoiceService__c, CommercientSF24_MYOX_SalesServiceDetail__c, MYOX_CustomerPayment__c, MYOX_CustomerPaymentLine__c, 1 more and a custom object
• Object display names: Account, Contact, Customer, CustomerToAccount Reverse Lookup, Customer Address, Item, ItemToProduct Reverse Lookup, Product, Sales Invoice, Sales Order Lines, Sales Invoice Lines, Sales Orders and 29 more
• Template groups: Account, Product, Invoice, Salesorder, Customer Multi Ship Addresses, CRM Order and Line

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_MYOBACCOUNTRIGHT_User
• vw_MYOBACCOUNTRIGHT_Account
• vw_MYOBACCOUNTRIGHT_CustomerToAccountLookup
• vw_MYOBACCOUNTRIGHT_Contact
• vw_MYOBACCOUNTRIGHT_Customer
• vw_MYOBACCOUNTRIGHT_CustomerAddress
• vw_MYOBACCOUNTRIGHT_Items
• vw_MYOBACCOUNTRIGHT_SalesInvoice
• vw_MYOBACCOUNTRIGHT_SalesInvoiceLines
• vw_MYOBACCOUNTRIGHT_ProductPriceBook
• vw_MYOBACCOUNTRIGHT_Product
• vw_MYOBACCOUNTRIGHT_ProductToItemMastertLookup
• vw_MYOBACCOUNTRIGHT_SalesOrders
• vw_MYOBACCOUNTRIGHT_SalesOrderLines
• vw_MYOBACCOUNTRIGHT_SalesPerson

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 MYOB AccountRight → 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.