Source ERP · 77 of 105

CRMPro → Salesforce — Sage 100 Premium: what the shipped templates set up

Read it in the terminal with "dlake skills show dlake-crmpro-salesforce/erps/sage-100-premium". It extends the dlake-crmpro-salesforce skill, which holds what is true whatever the source ERP.

CRMPro → Salesforce — Sage 100 Premium: 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/sage-100-premium.md, and that skill’s ERP table is what points at it. What follows is only what the shipped Sage 100 Premium → Salesforce templates themselves set, read from their Insert_Query, CreateViewQuery and MappingJson. This page grows as the catalogue does.

1. What the templates deliver

GroupBusiness outcomeObjectsSource tables and views
GET USERThe templates push users to Salesforce. New records are created, existing ones updated, and records removed in the ERP are deleted.users
AccountIn 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, CommercientSF8__AR_CUSTOMER__c, CommercientSF8__SAGE100_SalesPerson__cSF_ERP_Salesforce_Clone_AR_CUSTOMER, SF_ERP_Salesforce_Clone_AR_CUSTOMERCONTACT, SF_ERP_Salesforce_Clone_AR_SALESPERSON
CRM Opportunity and LineERP SO_SALESORDERHEADER, SO_SALESORDERDETAIL data becomes Opportunity, OpportunityLineItem in Salesforce. New records are created and existing ones updated; none are deleted.Opportunity, OpportunityLineItemSF_ERP_Salesforce_Clone_SO_SALESORDERHEADER, CommercientFlags, SF_ERP_Salesforce_Clone_SO_SALESORDERDETAIL
CRM Quote and LineThe templates push Quote, Opportunity to Salesforce. New records are created and existing ones updated; none are deleted.Quote, OpportunitySF_ERP_Salesforce_Clone_SO_SALESORDERHEADER, CommercientFlags, SF_ERP_Salesforce_Clone_SO_SALESORDERDETAIL
Customer Multi Ship AddressesIf 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.CommercientSF8__SO_SHIPTOADDRESS__cSF_ERP_Salesforce_Clone_SO_SHIPTOADDRESS
ProductERP CI_ITEM data becomes CommercientSF8__SAGE100_CI_Item__c, Product2 in Salesforce. New records are created and existing ones updated; none are deleted.CommercientSF8__SAGE100_CI_Item__c, Product2SF_ERP_Salesforce_Clone_CI_ITEM
InvoiceBoth 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.CommercientSF8__AR_INVOICEHISTORYHEADER__c, CommercientSF8__AR_TRANSACTIONPAYMENTHISTORY__c, CommercientSF8__SAGE100_AR_INVOICEHISTORYLOTSERIAL__c, CommercientSF8__AR_INVOICEHISTORYDETAIL__cSF_ERP_Salesforce_Clone_AR_INVOICEHISTORYHEADER, SF_ERP_Salesforce_Clone_AR_CUSTOMER, SF_ERP_Salesforce_Clone_AR_OPENINVOICE, SF_ERP_Salesforce_Clone_AR_SALESPERSON, CommercientFlags, SF_ERP_Salesforce_Clone_AR_TRANSACTIONPAYMENTHISTORY
SalesorderCommercient 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.CommercientSF8__SO_SALESORDERHEADER__c, CommercientSF8__SO_SALESORDERDETAIL__c, CommercientSF8__SAGE100_SALESORDERHISTORYHEADER__c, CommercientSF8__SAGE100_SALESORDERHISTORYDETAIL__cSF_ERP_Salesforce_Clone_SO_SALESORDERHEADER, SF_ERP_Salesforce_Clone_AR_CUSTOMER, CommercientFlags, SF_ERP_Salesforce_Clone_SO_SALESORDERDETAIL, SF_ERP_Salesforce_Clone_SO_SalesOrderHistoryHeader, SF_ERP_Salesforce_Clone_SO_SalesOrderHistoryDetail

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 nameCRM_Object_API_NameCRM_PK_API_NameSync_OrderTimeStamp_PrefixSQL_Query targetfield prefix / postfixSync_Operation_Type
GET USERusers0vw_SAGE100PREMIUM_User1=0'' / ''1
Sales PersonCommercientSF8__SAGE100_SalesPerson__cCommercientSF8__ExternalKey__c1vw_SalesPersonvw_SAGE100PREMIUM_SalesPersonCommercientSF8__ / __c
AccountAccountCommercientSF__Commercient_ArCustomerCode__c2vw_Accountvw_SAGE100PREMIUM_Account'' / ''
Customer MasterCommercientSF8__AR_CUSTOMER__cCommercientSF8__ExternalKey__c3vw_Customervw_SAGE100PREMIUM_CustomerCommercientSF8__ / __c
Customer to Account Reverse LookupAccountCommercientSF__Commercient_ArCustomerCode__c4vw_CustomerToAccountLookupvw_SAGE100PREMIUM_CustomerToAccountLookup'' / ''
Item MasterCommercientSF8__SAGE100_CI_Item__cCommercientSF8__ExternalKeys__c5vw_Itemvw_SAGE100PREMIUM_ItemMasterCommercientSF8__ / __c
ProductProduct2CommercientSF__ExternalKey__c6vw_Productvw_SAGE100PREMIUM_Product'' / ''
Product to Item Master Reverse LookupCommercientSF8__SAGE100_CI_Item__cCommercientSF8__ExternalKeys__c7vw_ProductToItemLookupvw_SAGE100PREMIUM_ProductToItemReverseLookupCommercientSF8__ / __c
Sales Order HeaderCommercientSF8__SO_SALESORDERHEADER__cCommercientSF8__SALESORDERNO__c11vw_SalesOrderHeadervw_SAGE100PREMIUM_SalesOrderHeaderCommercientSF8__ / __c
Sales Order LineCommercientSF8__SO_SALESORDERDETAIL__cCommercientSF8__ExternalKey__c12vw_SalesOrderLinevw_SAGE100PREMIUM_SalesOrderLineCommercientSF8__ / __c
Sales Order History HeaderCommercientSF8__SAGE100_SALESORDERHISTORYHEADER__cCommercientSF8__ExternalKey__c13vw_SalesOrderHistoryHeadervw_SAGE100PREMIUM_SalesOrderHistoryHeaderCommercientSF8__ / __c
Sales Order History LineCommercientSF8__SAGE100_SALESORDERHISTORYDETAIL__cCommercientSF8__ExternalKey__c14vw_SalesOrderHistoryLinevw_SAGE100PREMIUM_SalesOrderHistoryLineCommercientSF8__ / __c
Invoice HeaderCommercientSF8__AR_INVOICEHISTORYHEADER__cCommercientSF8__ExternalKey__c15vw_InvoiceHeadervw_SAGE100PREMIUM_InvoiceHeaderCommercientSF8__ / __c
Invoice LineCommercientSF8__AR_INVOICEHISTORYDETAIL__cCommercientSF8__ExternalKey__c16vw_InvoiceLinevw_SAGE100PREMIUM_InvoiceLineCommercientSF8__ / __c
ContactContactCommercientSF8__ExternalKey__c17vw_Contactvw_SAGE100PREMIUM_Contact'' / ''1
Invoice PaymentCommercientSF8__AR_TRANSACTIONPAYMENTHISTORY__cCommercientSF8__ExternalKey__c17vw_InvoicePaymentvw_SAGE100PREMIUM_InvoicePaymentCommercientSF8__ / __c
Invoice LotSerialCommercientSF8__SAGE100_AR_INVOICEHISTORYLOTSERIAL__cCommercientSF8__ExternalKey__c18vw_InvoiceLotSerialvw_SAGE100PREMIUM_InvoiceLotSerialCommercientSF8__ / __c
ShipToAddressCommercientSF8__SO_SHIPTOADDRESS__cCommercientSF8__ExternalKey__c19vw_ShipToAddressvw_SAGE100PREMIUM_ShipToAddressCommercientSF8__ / __c
Opportunity HeaderOpportunityExternalKey__c23vw_Opportunity_Headervw_SAGE100PREMIUM_Opportunity_Header'' / ''1
Opportunity LineOpportunityLineItemExternalKey__c24vw_Opportunity_Detailvw_SAGE100PREMIUM_Quote_Line'' / ''1
Quote_HeaderQuoteExternalKey__c25vw_Quote_Headervw_SAGE100PREMIUM_Quote_Header'' / ''1
Opportunity HeaderOpportunityExternalKey__c30vw_Opportunity_Headervw_SAGE100US_Opportunity_Header'' / ''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. Get_SOQL_Query carries a query on GET USER — those rows read records back from Salesforce as well as pushing. On Opportunity Header the SQL_Query names a view the same template’s CreateViewQuery does not create (vw_SAGE100US_Opportunity_Header against vw_SAGE100PREMIUM_Quote_Line), so check the view exists under the name the row selects from before activating it.

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.

ViewChange detectionRepository keyReads other prefixesIdentity columnSource tables
vw_SAGE100PREMIUM_SalesPersoninsert + updatevw_SalesPerson:ExternalKeySF_ERP_Salesforce_Clone_AR_SALESPERSON
vw_SAGE100PREMIUM_Accountinsert + updatevw_Account:vw_SalesPerson:, vw_SAGE100PREMIUM_User:SF_ERP_Salesforce_Clone_AR_CUSTOMER
vw_SAGE100PREMIUM_Customerinsert + updatevw_Customer:vw_Account:, vw_SalesPerson:SF_ERP_Salesforce_Clone_AR_CUSTOMER
vw_SAGE100PREMIUM_CustomerToAccountLookupinsert + updatevw_CustomerToAccountLookup:vw_Customer:SF_ERP_Salesforce_Clone_AR_CUSTOMER
vw_SAGE100PREMIUM_ItemMasterinsert + updatevw_Item:ExternalKeysSF_ERP_Salesforce_Clone_CI_ITEM
vw_SAGE100PREMIUM_Productinsert + updatevw_Product:vw_Item:SF_ERP_Salesforce_Clone_CI_ITEM
vw_SAGE100PREMIUM_ProductToItemReverseLookupinsert + updatevw_ProductToItemLookup:vw_Product:SF_ERP_Salesforce_Clone_CI_ITEM
vw_SAGE100PREMIUM_SalesOrderHeaderinsert + updatevw_SalesOrderHeader:vw_Customer:, vw_Account:, vw_SalesPerson:SF_ERP_Salesforce_Clone_SO_SALESORDERHEADER, SF_ERP_Salesforce_Clone_AR_CUSTOMER, CommercientFlags
vw_SAGE100PREMIUM_SalesOrderLineinsert + updatevw_SalesOrderLine:vw_SalesOrderHeader:SF_ERP_Salesforce_Clone_SO_SALESORDERDETAIL, SF_ERP_Salesforce_Clone_SO_SALESORDERHEADER, SF_ERP_Salesforce_Clone_AR_CUSTOMER
vw_SAGE100PREMIUM_SalesOrderHistoryHeaderinsert + updatevw_SalesOrderHistoryHeader:vw_Customer:, vw_Account:SF_ERP_Salesforce_Clone_SO_SalesOrderHistoryHeader, SF_ERP_Salesforce_Clone_AR_CUSTOMER, CommercientFlags
vw_SAGE100PREMIUM_SalesOrderHistoryLineinsert + updatevw_SalesOrderHistoryLine:vw_SalesOrderHistoryHeader:SF_ERP_Salesforce_Clone_SO_SalesOrderHistoryDetail, SF_ERP_Salesforce_Clone_SO_SalesOrderHistoryHeader, SF_ERP_Salesforce_Clone_AR_CUSTOMER
vw_SAGE100PREMIUM_InvoiceHeaderinsert + updatevw_InvoiceHeader:vw_Customer:, vw_Account:, vw_SalesPerson:SF_ERP_Salesforce_Clone_AR_INVOICEHISTORYHEADER, SF_ERP_Salesforce_Clone_AR_CUSTOMER, SF_ERP_Salesforce_Clone_AR_OPENINVOICE, SF_ERP_Salesforce_Clone_AR_SALESPERSON, CommercientFlags
vw_SAGE100PREMIUM_InvoiceLineinsert + updatevw_InvoiceLine:vw_InvoiceHeader:, vw_Item:SF_ERP_Salesforce_Clone_AR_INVOICEHISTORYDETAIL
vw_SAGE100PREMIUM_Contactinsert + updatevw_Contact:vw_Account:CommercientSF8__ExternalKey__cSF_ERP_Salesforce_Clone_AR_CUSTOMERCONTACT
vw_SAGE100PREMIUM_InvoicePaymentinsert + updatevw_InvoicePayment:vw_Customer:, vw_Account:, vw_InvoiceHeader:SF_ERP_Salesforce_Clone_AR_TRANSACTIONPAYMENTHISTORY, SF_ERP_Salesforce_Clone_AR_INVOICEHISTORYHEADER, A, CommercientFlags
vw_SAGE100PREMIUM_InvoiceLotSerialinsert + updatevw_InvoiceLotSerial:vw_InvoiceHeader:, vw_InvoiceLine:SF_ERP_Salesforce_Clone_AR_INVOICEHISTORYLOTSERIAL
vw_SAGE100PREMIUM_ShipToAddressinsert + updatevw_ShipToAddress:vw_SalesPerson:, vw_Account:, vw_Customer:SF_ERP_Salesforce_Clone_SO_SHIPTOADDRESS
vw_SAGE100PREMIUM_Opportunity_Headerinsert + updatevw_Opportunity_Header:vw_Customer:, vw_Account:, vw_SalesPerson:SF_ERP_Salesforce_Clone_SO_SALESORDERHEADER, CommercientFlags
vw_SAGE100PREMIUM_Quote_Lineinsert-onlyvw_Quote_Header:, vw_Product:, vw_Quote_Detail:SF_ERP_Salesforce_Clone_SO_SALESORDERDETAIL, SF_ERP_Salesforce_Clone_SO_SALESORDERHEADER
vw_SAGE100PREMIUM_Quote_Headerinsert + updatevw_Quote_Header:vw_Customer:, vw_Account:, vw_Opportunity_Header:, vw_SalesPerson:SF_ERP_Salesforce_Clone_SO_SALESORDERHEADER, CommercientFlags
vw_SAGE100PREMIUM_Quote_Lineinsert-onlyvw_Quote_Header:, vw_Product:, vw_Quote_Detail:SF_ERP_Salesforce_Clone_SO_SALESORDERDETAIL, SF_ERP_Salesforce_Clone_SO_SALESORDERHEADER

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

  • 0 — GET USER
  • 1 — Sales Person
  • 2 — Account
  • 3 — Customer Master
  • 4 — Customer to Account Reverse Lookup
  • 5 — Item Master
  • 6 — Product
  • 7 — Product to Item Master Reverse Lookup
  • 11 — Sales Order Header
  • 12 — Sales Order Line
  • 13 — Sales Order History Header
  • 14 — Sales Order History Line
  • 15 — Invoice Header
  • 16 — Invoice Line
  • 17 — Contact, Invoice Payment
  • 18 — Invoice LotSerial
  • 19 — ShipToAddress
  • 23 — Opportunity Header
  • 24 — Opportunity Line
  • 25 — Quote_Header
  • 30 — Opportunity Header

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_SAGE100PREMIUM_Account reads vw_SalesPerson:, vw_SAGE100PREMIUM_User:
  • vw_SAGE100PREMIUM_CustomerToAccountLookup reads vw_Customer:
  • vw_SAGE100PREMIUM_Contact reads vw_Account:
  • vw_SAGE100PREMIUM_Opportunity_Header reads vw_Customer:, vw_Account:, vw_SalesPerson:
  • vw_SAGE100PREMIUM_Quote_Line reads vw_Quote_Header:, vw_Product:, vw_Quote_Detail:; no template in this set writes vw_Quote_Detail:
  • vw_SAGE100PREMIUM_Quote_Header reads vw_Customer:, vw_Account:, vw_Opportunity_Header:, vw_SalesPerson:
  • vw_SAGE100PREMIUM_Quote_Line reads vw_Quote_Header:, vw_Product:, vw_Quote_Detail:; no template in this set writes vw_Quote_Detail:
  • vw_SAGE100PREMIUM_Customer reads vw_Account:, vw_SalesPerson:
  • vw_SAGE100PREMIUM_ShipToAddress reads vw_SalesPerson:, vw_Account:, vw_Customer:
  • vw_SAGE100PREMIUM_ProductToItemReverseLookup reads vw_Product:
  • vw_SAGE100PREMIUM_InvoiceHeader reads vw_Customer:, vw_Account:, vw_SalesPerson:
  • vw_SAGE100PREMIUM_InvoicePayment reads vw_Customer:, vw_Account:, vw_InvoiceHeader:
  • vw_SAGE100PREMIUM_InvoiceLotSerial reads vw_InvoiceHeader:, vw_InvoiceLine:
  • vw_SAGE100PREMIUM_InvoiceLine reads vw_InvoiceHeader:, vw_Item:
  • vw_SAGE100PREMIUM_Product reads vw_Item:
  • vw_SAGE100PREMIUM_SalesOrderHeader reads vw_Customer:, vw_Account:, vw_SalesPerson:
  • vw_SAGE100PREMIUM_SalesOrderLine reads vw_SalesOrderHeader:
  • vw_SAGE100PREMIUM_SalesOrderHistoryHeader reads vw_Customer:, vw_Account:
  • vw_SAGE100PREMIUM_SalesOrderHistoryLine reads vw_SalesOrderHistoryHeader:

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.

TemplateObjectMapped fieldsFirst ERP → Salesforce pairs
Sales PersonCommercientSF8__SAGE100_SalesPerson__c25SalespersonDivisionNo, SalespersonNoCommercientSF8__ExternalKey__c, SalespersonName, SalespersonDivisionNo, SalespersonNoname, SalespersonDivisionNoSalespersonDivisionNo, SalespersonNoSalespersonNo, SalespersonNameSALESPERSONNAME
AccountAccount15ARDivisionNo, CustomerNoCommercientSF__Commercient_ArCustomerCode__c, CustomerName, ARDivisionNo, CustomerNoName, TelephoneNoPhone, SalespersonDivisionNo, SalespersonNoCommercientSF8__SAGE100_SalesPerson__c, AddressLine1, AddressLine2, AddressLine3BillingStreet
Customer to Account Reverse LookupAccount2ARDivisionNo,CustomerNoCommercientSF__Commercient_ArCustomerCode__c, SFDCIDCommercientSF8__Sage_Customer_Record__c
Item MasterCommercientSF8__SAGE100_CI_Item__c82ItemCodeCommercientSF8__ExternalKeys__c, ItemCodeCommercientSF8__ItemCode__c, ItemCodeCommercientSF8__Name__c, ItemTypeCommercientSF8__ItemType__c, ItemCodeDescCommercientSF8__ItemCodeDesc__c
ProductProduct26SFDCIDCommercientSF8__SAGE100_CI_ITEM__c, ItemCodeCommercientSF__ExternalKey__c, InactiveItemIsActive, ItemCodeDescName, ItemCodeProductCode
Product to Item Master Reverse LookupCommercientSF8__SAGE100_CI_Item__c2ItemCodeCommercientSF8__ExternalKeys__c, SFDCIDCommercientSF8__Product__c
Sales Order LineCommercientSF8__SO_SALESORDERDETAIL__c64SalesOrderNo, LineKeyCommercientSF8__ExternalKey__c, SFDCIDCommercientSF8__Sage100_Open_Sales_Orders__c, SalesOrderNo, LineKeyName, SalesOrderNoCommercientSF8__SALESORDERNO__c, LineKeyCommercientSF8__LINEKEY__c
Sales Order History HeaderCommercientSF8__SAGE100_SALESORDERHISTORYHEADER__c88SalesOrderNoCommercientSF8__ExternalKey__c, SalesOrderNoCommercientSF8__Name__c, SFDCIDCommercientSF8__Account__c, SFDCIDCommercientSF8__Customer__c, OrderStatusCommercientSF8__OrderStatus__c
Sales Order History LineCommercientSF8__SAGE100_SALESORDERHISTORYDETAIL__c63SalesOrderNo, SequenceNoCommercientSF8__ExternalKey__c, SalesOrderNo, SequenceNoCommercientSF8__Name__c, SFDCIDCommercientSF8__Salesorder_History_Header__c, SequenceNoCommercientSF8__SequenceNo__c, LineKeyCommercientSF8__LineKey__c
Invoice HeaderCommercientSF8__AR_INVOICEHISTORYHEADER__c87InvoiceNo, HeaderSeqNoCommercientSF8__ExternalKey__c, InvoiceNo, HeaderSeqNoName, ARDivisionNo, CustomerNoAccount, ARDivisionNo, CustomerNoSage100_Customer_Record, SalespersonDivisionNo, SalespersonNoSalesPerson
Invoice LineCommercientSF8__AR_INVOICEHISTORYDETAIL__c59InvoiceNo,HeaderSeqNo,DetailSeqNoCommercientSF8__ExternalKey__c, InvoiceNo,HeaderSeqNoCommercientSF8__Sage100_Invoice__c, ItemCodeCommercientSF8__Sage100_Item__c, InvoiceNoCommercientSF8__INVOICENO__c, HeaderSeqNoCommercientSF8__HEADERSEQNO__c
ContactContact14CommercientSF8__ExternalKeyCommercientSF8__ExternalKey__c, AccountIDAccountID, LastNameLastName, FirstNameFirstName, EmailEmail
Invoice PaymentCommercientSF8__AR_TRANSACTIONPAYMENTHISTORY__c32SFDCIDAccount, SFDCIDSage100_Customer_Record, SFDCIDSage100_Invoice, ARDivisionNoCommercientSF8__ARDivisionNo__c, CustomerNoCommercientSF8__CustomerNo__c
Invoice LotSerialCommercientSF8__SAGE100_AR_INVOICEHISTORYLOTSERIAL__c9InvoiceNo,HeaderSeqNo,DetailSeqNo,LotSerialNoCommercientSF8__ExternalKey__c, InvoiceNoSAGE100Invoices, InvoiceNo,HeaderSeqNo,DetailSeqNoSage100_Invoice_Line_Items__c, DetailSeqNoDETAILSEQNO, HeaderSeqNoHEADERSEQNO
Opportunity HeaderOpportunity7SalesOrderNoExternalKey__c, SalesOrderNoName, SFDCIDAccountId, TaxableAmtAmount, SFDCIDPricebook2ID
Opportunity LineOpportunityLineItem8SalesOrderNo, LineKeyExternalKey__c, SFDCIDQuoteId, SFDCIDProduct2Id, SFDCIDPricebookEntryId, PromiseDateServiceDate
Quote_HeaderQuote22SalesOrderNoExternalKey__c, SalesOrderNoName, T4.SFDCIDOpportunityId, T3.SFDCIDSAGE100_SalesPerson__c, T5.SFDCIDSAGE100V5_Term__c
Opportunity HeaderOpportunity8SalesOrderNo, LineKeyExternalKey__c, SFDCIDQuoteId, SFDCIDProduct2Id, SFDCIDPricebookEntryId, PromiseDateServiceDate

6. Community templates

The catalogue carries 104 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: 104
  • Default operations: insert on 104, update on 104, delete on 104
  • Marked circular-sync: 1
  • Licence groups they span: 13
  • Destination objects: Account, CommercientSF8__SAGE100_CI_Item__c, CommercientSF8__AR_INVOICEHISTORYHEADER__c, Product2, CommercientSF8__AR_CUSTOMER__c, CommercientSF8__AR_INVOICEHISTORYDETAIL__c, PriceBookEntry, CommercientSF8__SAGE100_AR_INVOICEHISTORYLOTSERIAL__c, CommercientSF8__SAGE100_SALESORDERHISTORYDETAIL__c, CommercientSF8__SAGE100_SALESORDERHISTORYHEADER__c, CommercientSF8__SAGE100_SalesPerson__c, CommercientSF8__SO_SHIPTOADDRESS__c, Contact, CommercientSF8__AR_TRANSACTIONPAYMENTHISTORY__c, CommercientSF8__SO_SALESORDERDETAIL__c, CommercientSF8__SO_SALESORDERHEADER__c, CommercientSF8__SAGE100_ItemWarehouse__c, CommercientSF8__SO_LotSerialHistory__c, OpportunityLineItem, PricebookEntry and 12 more
  • Object display names: Product to Item Master Reverse Lookup, Account, Customer to Account Reverse Lookup, Customer Master, Invoice Header, Invoice Line, Product, Contact, Invoice LotSerial, Item Master, Sales Order History Header, Sales Order History Line and 28 more
  • Template groups: Account, Product, Invoice, Salesorder, Customer Multi Ship Addresses, CRM Opportunity and Line, CRM Quote and Line, Invoice History Headers

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_SAGE100PREMIUM_User
  • vw_Account
  • vw_CustomerToAccountLookup
  • vw_Contact
  • vw_Opportunity_Header
  • vw_Opportunity_Detail
  • vw_Quote_Header
  • vw_Customer
  • vw_ShipToAddress
  • vw_Item
  • vw_ProductToItemLookup
  • vw_InvoiceHeader
  • vw_InvoicePayment
  • vw_InvoiceLotSerial
  • vw_InvoiceLine
  • vw_Product
  • vw_SalesOrderHeader
  • vw_SalesOrderLine
  • vw_SalesOrderHistoryHeader
  • vw_SalesOrderHistoryLine
  • vw_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 Sage 100 Premium → 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.