Friday, 11 May 2018

D365 On-Premise Packages exclude models

Developers usually follow these steps for deployment

  1. Complete development on 1-box VM
  2. Check-in code on TFS 
  3. Checkout code on build machine resolve conflicts.
  4. Build model + Sync Database (this needs to be successful)
  5. Create deployment package from build machine.
  6. Upload it on asset library on LCS.
  7. Apply updates from LCS.

Above package might fail when deploy on premise because on-premise has few model missing.

For on-premise deployment, we need to be careful, Don't add yellow highlight model in your package neither your custom model create reference from yellow highlight model, because yellow highlight models are not present in on-premises environment.

Exclude Yellow Highlight Models

1 Box VM On-Prem Machine
AccountsPayableMobile AccountsPayableMobile
ApplicationCommon ApplicationCommon
ApplicationFoundation ApplicationFoundation
ApplicationFoundationFormAdaptor
ApplicationPlatform ApplicationPlatform
ApplicationPlatformFormAdaptor
ApplicationSuite ApplicationSuite
ApplicationSuiteFormAdaptor
ApplicationWorkspaces ApplicationWorkspaces
ApplicationWorkspacesFormAdaptor
BankTypes BankTypes
Bin bin
BusinessProcess BusinessProcess
Calendar Calendar
CaseManagement CaseManagement
ContactPerson ContactPerson
CostAccounting CostAccounting
CostAccountingAX CostAccountingAX
Currency Currency
DataExpansionTool DataExpansionTool
DataImpExpApplication DataImpExpApplication
DataSharing DataSharing
Datastack
DataUpgrade DataUpgrade
DataUpgradePlatform DataUpgradePlatform

Dimensions Dimensions
Directory Directory
DirectoryUpgrade DirectoryUpgrade


DOM DOM
ElectronicReporting ElectronicReporting
ElectronicReportingAppSuiteIntegration ElectronicReportingAppSuiteIntegration
ElectronicReportingCore ElectronicReportingCore
ElectronicReportingDotNetUtils ElectronicReportingDotNetUtils
ElectronicReportingForAx ElectronicReportingForAx
ElectronicReportingMapping ElectronicReportingMapping
ExpenseMobile ExpenseMobile
FinancialReporting FinancialReporting
FinancialReportingAdaptors
FinancialReportingEntityStore FinancialReportingEntityStore
FiscalBooks FiscalBooks
FiscalBooksFormAdaptor
FleetManagement
FleetManagementExtension
FleetManagementUnitTests
GeneralLedger GeneralLedger
GeneralLedgerFormAdaptor
InstallationRecords InstallationRecords
InventoryDimensionConversion InventoryDimensionConversion
Ledger Ledger
Measurement Measurement
Personnel Personnel
PersonnelCore PersonnelCore
PersonnelManagement PersonnelManagement
PersonnelMobile PersonnelMobile
PersonnelUpgrade PersonnelUpgrade
Plugins Plugins
Policy Policy
Project Project
ProjectMobile ProjectMobile
PublicSector PublicSector
PublicSectorFormAdaptor
RegulatoryServices RegulatoryServices
Retail Retail
RetailFormAdaptor
SCMMobile SCMMobile
SelfHealing SelfHealing
SelfHealingRules SelfHealingRules
SourceDocumentation SourceDocumentation
SourceDocumentationTypes SourceDocumentationTypes
StaticMetadata StaticMetadata
Subledger Subledger
SystemHealth SystemHealth
Tax Tax
TaxEngine TaxEngine
TestEssentials TestEssentials
Tutorial Tutorial
UnitOfMeasure UnitOfMeasure
WMSAdvancedMigration WMSAdvancedMigration


Once deployment is complete on-premises. you can check installed model from following folder of AOS node.

example.

C:\SF\AOS_1\Fabric\work\Applications\AXSFType_App19\AXSF.Code.1.0.20180510102853\Packages