CRMPro → Salesforce — Aptean Made2Manage: what the shipped templates set up

CRMPro → Salesforce — Aptean Made2Manage: 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/aptean-made2manage.md, and that skill’s ERP table is what points at it. What follows is only what the shipped Aptean Made2Manage → 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
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, CommercientSF21__Aptean_M2M_UTTERMS__c, Contact, CommercientSF21__Aptean_M2M_SLCDPM__c, CommercientSF21__Aptean_M2M_SLSPNS__c	SF_ERP_Salesforce_Clone_SLCDPM, SF_ERP_Salesforce_Clone_SLSPNS, SF_ERP_Salesforce_Clone_SYADDR, SF_ERP_Salesforce_Clone_UTTERMS, SF_ERP_Salesforce_Clone_SYPHON, SF_ERP_Salesforce_Clone_SLCDPMX
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 and existing ones updated; none are deleted.	CommercientSF21__Aptean_M2M_SYADDR__c	SF_ERP_Salesforce_Clone_SYADDR, SF_ERP_Salesforce_Clone_SLCDPM
Product	The templates push CommercientSF21__Aptean_M2M_INMAST__c to Salesforce. New records are created and existing ones updated; none are deleted.	CommercientSF21__Aptean_M2M_INMAST__c	SF_ERP_Salesforce_Clone_INMAST
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 and existing ones updated; none are deleted.	CommercientSF21__Aptean_M2M_ARMAST__c, CommercientSF21__Aptean_M2M_ARITEM__c	SF_ERP_Salesforce_Clone_ARMAST, SF_ERP_Salesforce_Clone_SLCDPM, CommercientFlags, SF_ERP_Salesforce_Clone_ARITEM, SF_ERP_Salesforce_Clone_INMAST
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. New records are created and existing ones updated; none are deleted.	CommercientSF21__Aptean_M2M_SOMAST__c, CommercientSF21__Aptean_M2M_SOITEM__c	SF_ERP_Salesforce_Clone_SOMAST, SF_ERP_Salesforce_Clone_SLCDPM, CommercientFlags, SF_ERP_Salesforce_Clone_SOITEM, SF_ERP_Salesforce_Clone_INMAST

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
PaymentTerms	CommercientSF21__Aptean_M2M_UTTERMS__c	CommercientSF21__ExternalKey__c	1	vw_APTEANMADE2MANAGE_PaymentTerms:	vw_APTEANMADE2MANAGE_PaymentTerms	CommercientSF21__ / __c	—
SalesPerson	CommercientSF21__Aptean_M2M_SLSPNS__c	CommercientSF21__ExternalKey__c	2	vw_APTEANMADE2MANAGE_SalesPerson:	vw_APTEANMADE2MANAGE_SalesPerson	CommercientSF21__ / __c	—
Account	Account	CommercientSF__Commercient_ArCustomerCode__c	3	vw_APTEANMADE2MANAGE_Account:	vw_APTEANMADE2MANAGE_Account	'' / ''	—
Customer	CommercientSF21__Aptean_M2M_SLCDPM__c	CommercientSF21__ExternalKey__c	4	vw_APTEANMADE2MANAGE_Customer:	vw_APTEANMADE2MANAGE_Customer	CommercientSF21__ / __c	—
Address	CommercientSF21__Aptean_M2M_SYADDR__c	CommercientSF21__ExternalKey1__c	5	vw_APTEANMADE2MANAGE_Address:	vw_APTEANMADE2MANAGE_Address	CommercientSF21__ / __c	—
Item Master	CommercientSF21__Aptean_M2M_INMAST__c	CommercientSF21__ExternalKey__c	6	vw_APTEANMADE2MANAGE_Item:	vw_APTEANMADE2MANAGE_Item	CommercientSF21__ / __c	—
SalesOrderHeader	CommercientSF21__Aptean_M2M_SOMAST__c	CommercientSF21__ExternalKey__c	7	vw_APTEANMADE2MANAGE_SOHeader:	vw_APTEANMADE2MANAGE_SOHeader	CommercientSF21__ / __c	—
SalesOrderDetail	CommercientSF21__Aptean_M2M_SOITEM__c	CommercientSF21__ExternalKey__c	8	vw_APTEANMADE2MANAGE_SODetail:	vw_APTEANMADE2MANAGE_SODetail	CommercientSF21__ / __c	—
InvoiceHeader	CommercientSF21__Aptean_M2M_ARMAST__c	CommercientSF21__ExternalKey__c	9	vw_APTEANMADE2MANAGE_InvoiceHeader:	vw_APTEANMADE2MANAGE_InvoiceHeader	CommercientSF21__ / __c	—
InvoiceDetail	CommercientSF21__Aptean_M2M_ARITEM__c	CommercientSF21__ExternalKey__c	10	vw_APTEANMADE2MANAGE_InvoiceDetail:	vw_APTEANMADE2MANAGE_InvoiceDetail	CommercientSF21__ / __c	—
Contact SYNC	Contact	ExternalKey__c	13	vw_APTEANMADE2MANAGE_Contact	vw_APTEANMADE2MANAGE_Contact	'' / ''	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. IsAccountMatching is set on Account. Text columns a template does not use are inserted as '' rather than left NULL.

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_APTEANMADE2MANAGE_PaymentTerms	insert + update	—	vw_APTEANMADE2MANAGE_PaymentTerms:	ExternalKey	SF_ERP_Salesforce_Clone_UTTERMS
vw_APTEANMADE2MANAGE_SalesPerson	insert + update	—	vw_APTEANMADE2MANAGE_SalesPerson:	ExternalKey	SF_ERP_Salesforce_Clone_SLSPNS
vw_APTEANMADE2MANAGE_Customer	insert + update	—	vw_APTEANMADE2MANAGE_Account:, vw_APTEANMADE2MANAGE_Customer:	ExternalKey	SF_ERP_Salesforce_Clone_SLCDPM
vw_APTEANMADE2MANAGE_Address	insert + update	—	vw_APTEANMADE2MANAGE_Customer:, vw_APTEANMADE2MANAGE_Address:	ExternalKey1	SF_ERP_Salesforce_Clone_SYADDR, SF_ERP_Salesforce_Clone_SLCDPM
vw_APTEANMADE2MANAGE_Item	insert + update	—	vw_APTEANMADE2MANAGE_Item:	ExternalKey	SF_ERP_Salesforce_Clone_INMAST
vw_APTEANMADE2MANAGE_SOHeader	insert + update	—	vw_APTEANMADE2MANAGE_Account:, vw_APTEANMADE2MANAGE_Customer:, vw_APTEANMADE2MANAGE_SOHeader:	ExternalKey	SF_ERP_Salesforce_Clone_SOMAST, SF_ERP_Salesforce_Clone_SLCDPM, CommercientFlags
vw_APTEANMADE2MANAGE_SODetail	insert + update	—	vw_APTEANMADE2MANAGE_SOHeader:, vw_APTEANMADE2MANAGE_Item:, vw_APTEANMADE2MANAGE_SODetail:	ExternalKey	SF_ERP_Salesforce_Clone_SOITEM, SF_ERP_Salesforce_Clone_SOMAST, SF_ERP_Salesforce_Clone_INMAST
vw_APTEANMADE2MANAGE_InvoiceHeader	insert + update	—	vw_APTEANMADE2MANAGE_Account:, vw_APTEANMADE2MANAGE_Customer:, vw_APTEANMADE2MANAGE_InvoiceHeader:	ExternalKey	SF_ERP_Salesforce_Clone_ARMAST, SF_ERP_Salesforce_Clone_SLCDPM, CommercientFlags
vw_APTEANMADE2MANAGE_InvoiceDetail	insert + update	—	vw_APTEANMADE2MANAGE_InvoiceHeader:, vw_APTEANMADE2MANAGE_Item:, vw_APTEANMADE2MANAGE_InvoiceDetail:	ExternalKey	SF_ERP_Salesforce_Clone_ARITEM, SF_ERP_Salesforce_Clone_ARMAST, SF_ERP_Salesforce_Clone_INMAST
vw_APTEANMADE2MANAGE_Contact	insert + update	vw_APTEANMADE2MANAGE_Contact:	vw_APTEANMADE2MANAGE_Account:	ExternalKey__c	SF_ERP_Salesforce_Clone_SYPHON, SF_ERP_Salesforce_Clone_SLCDPMX

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

• 1 — PaymentTerms
• 2 — SalesPerson
• 3 — Account
• 4 — Customer
• 5 — Address
• 6 — Item Master
• 7 — SalesOrderHeader
• 8 — SalesOrderDetail
• 9 — InvoiceHeader
• 10 — InvoiceDetail
• 13 — Contact SYNC

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.

• Account reads vw_APTEANMADE2MANAGE_SalesPerson:, vw_APTEANMADE2MANAGE_Account:; no template in this set writes vw_APTEANMADE2MANAGE_SalesPerson:, vw_APTEANMADE2MANAGE_Account:
• vw_APTEANMADE2MANAGE_PaymentTerms reads vw_APTEANMADE2MANAGE_PaymentTerms:; no template in this set writes vw_APTEANMADE2MANAGE_PaymentTerms:
• vw_APTEANMADE2MANAGE_Contact reads vw_APTEANMADE2MANAGE_Account:; no template in this set writes vw_APTEANMADE2MANAGE_Account:
• vw_APTEANMADE2MANAGE_Customer reads vw_APTEANMADE2MANAGE_Account:, vw_APTEANMADE2MANAGE_Customer:; no template in this set writes vw_APTEANMADE2MANAGE_Account:, vw_APTEANMADE2MANAGE_Customer:
• vw_APTEANMADE2MANAGE_Address reads vw_APTEANMADE2MANAGE_Customer:, vw_APTEANMADE2MANAGE_Address:; no template in this set writes vw_APTEANMADE2MANAGE_Customer:, vw_APTEANMADE2MANAGE_Address:
• vw_APTEANMADE2MANAGE_Item reads vw_APTEANMADE2MANAGE_Item:; no template in this set writes vw_APTEANMADE2MANAGE_Item:
• vw_APTEANMADE2MANAGE_InvoiceHeader reads vw_APTEANMADE2MANAGE_Account:, vw_APTEANMADE2MANAGE_Customer:, vw_APTEANMADE2MANAGE_InvoiceHeader:; no template in this set writes vw_APTEANMADE2MANAGE_Account:, vw_APTEANMADE2MANAGE_Customer:, vw_APTEANMADE2MANAGE_InvoiceHeader:
• vw_APTEANMADE2MANAGE_InvoiceDetail reads vw_APTEANMADE2MANAGE_InvoiceHeader:, vw_APTEANMADE2MANAGE_Item:, vw_APTEANMADE2MANAGE_InvoiceDetail:; no template in this set writes vw_APTEANMADE2MANAGE_InvoiceHeader:, vw_APTEANMADE2MANAGE_Item:, vw_APTEANMADE2MANAGE_InvoiceDetail:
• vw_APTEANMADE2MANAGE_SOHeader reads vw_APTEANMADE2MANAGE_Account:, vw_APTEANMADE2MANAGE_Customer:, vw_APTEANMADE2MANAGE_SOHeader:; no template in this set writes vw_APTEANMADE2MANAGE_Account:, vw_APTEANMADE2MANAGE_Customer:, vw_APTEANMADE2MANAGE_SOHeader:
• vw_APTEANMADE2MANAGE_SODetail reads vw_APTEANMADE2MANAGE_SOHeader:, vw_APTEANMADE2MANAGE_Item:, vw_APTEANMADE2MANAGE_SODetail:; no template in this set writes vw_APTEANMADE2MANAGE_SOHeader:, vw_APTEANMADE2MANAGE_Item:, vw_APTEANMADE2MANAGE_SODetail:
• vw_APTEANMADE2MANAGE_SalesPerson reads vw_APTEANMADE2MANAGE_SalesPerson:; no template in this set writes vw_APTEANMADE2MANAGE_SalesPerson:

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
PaymentTerms	CommercientSF21__Aptean_M2M_UTTERMS__c	13	identity_column → CommercientSF21__ExternalKey__c, fcdescr → Name, fcclass → FCCLASS, fcdescr → FCDESCR, fctermsid → FCTERMSID
SalesPerson	CommercientSF21__Aptean_M2M_SLSPNS__c	17	identity_column → CommercientSF21__ExternalKey__c, flastname → Name, fdistno → FDISTNO, flastname → FLASTNAME, fsalespn → FSALESPN
Account	Account	13	identity_column → CommercientSF__Commercient_ArCustomerCode__c, fcompany → NAME, fphone → PHONE, fmstreet → BillingStreet, fccity → BillingCity
Customer	CommercientSF21__Aptean_M2M_SLCDPM__c	73	identity_column → CommercientSF21__ExternalKey__c, fcompany → CommercientSF21__Name__c, fcustno → CommercientSF21__FCUSTNO__c, fcompany → CommercientSF21__FCOMPANY__c, fcity → CommercientSF21__FCITY__c
Address	CommercientSF21__Aptean_M2M_SYADDR__c	32	SFDCID → Aptean_M2M_CUSTOMER, identity_column → ExternalKey1, identity_column → Name, fllongdist → FLLONGDIST, fcaddrkey → FCADDRKEY
Item Master	CommercientSF21__Aptean_M2M_INMAST__c	96	identity_column → CommercientSF21__ExternalKey__c, fdescript → Name, fpartno → FPARTNO, frev → FREV, fcstscode → FCSTSCODE
SalesOrderHeader	CommercientSF21__Aptean_M2M_SOMAST__c	77	identity_column → CommercientSF21__ExternalKey__c, identity_column → CommercientSF21__Name__c, fsono → CommercientSF21__FSONO__c, fcustno → CommercientSF21__FCUSTNO__c, fcompany → CommercientSF21__FCOMPANY__c
SalesOrderDetail	CommercientSF21__Aptean_M2M_SOITEM__c	69	identity_column → CommercientSF21__ExternalKey__c, finumber → CommercientSF21__FINUMBER__c, fpartno → CommercientSF21__FPARTNO__c, fpartrev → CommercientSF21__FPARTREV__c, fsono → CommercientSF21__FSONO__c
InvoiceHeader	CommercientSF21__Aptean_M2M_ARMAST__c	68	identity_column → CommercientSF21__ExternalKey__c, identity_column → CommercientSF21__Name__c, fbcity → CommercientSF21__FBCITY__c, fbcompany → CommercientSF21__FBCOMPANY__c, fbcountry → CommercientSF21__FBCOUNTRY__c
InvoiceDetail	CommercientSF21__Aptean_M2M_ARITEM__c	55	identity_column → CommercientSF21__ExternalKey__c, identity_column → CommercientSF21__Name__c, fbkordqty → CommercientSF21__FBKORDQTY__c, fcinvoice → CommercientSF21__FCINVOICE__c, fcost → CommercientSF21__FCOST__c
Contact SYNC	Contact	8	FirstName → FirstName, LastName → LastName, Fax → Fax, MobilePhone → MobilePhone, Title → Title

6. Community templates

The catalogue carries 182 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: 182
• Default operations: insert on 182, update on 182, delete on 182
• Marked circular-sync: 0
• Licence groups they span: 19
• Destination objects: Account, Product2, Opportunity, Contact, Quote, PriceBookEntry, OpportunityLineItem, QuoteLineItem, Attachment, PricebookEntry, APTEANMADE2MANAGE_Opportunity__c, APTEANMADE2MANAGE_Quote__c, APTEANMADE2MANAGE_QuoteLine__c, ShipTo__c, SOShipToHeader__c, SOShipToLine__c, User and 29 custom objects
• Object display names: Customer, SalesOrderDetail, SalesOrderHeader, Account, Address, InvoiceDetail, InvoiceHeader, Item Master, Account Reverse Lookup, Contact SYNC, SalesPerson, Product, 61 more and 22 further templates
• Template groups: Account, Product, Salesorder, CRM Opportunity and Line, Customer Multi Ship Addresses, Invoice, CRM Quote and Line, Opportunity, Pricebook, Open AR Invoice Header, QuoteLine

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_APTEANMADE2MANAGE_Account:
• vw_APTEANMADE2MANAGE_PaymentTerms:
• vw_APTEANMADE2MANAGE_Contact
• vw_APTEANMADE2MANAGE_Customer:
• vw_APTEANMADE2MANAGE_Address:
• vw_APTEANMADE2MANAGE_Item:
• vw_APTEANMADE2MANAGE_InvoiceHeader:
• vw_APTEANMADE2MANAGE_InvoiceDetail:
• vw_APTEANMADE2MANAGE_SOHeader:
• vw_APTEANMADE2MANAGE_SODetail:
• vw_APTEANMADE2MANAGE_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 Aptean Made2Manage → 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.