During the installation of the Long Term Data Retention application on Dataverse for Finance and Operations, the setup process validates the existence and status of supported tables. However, if a table is not present due to a disabled configuration key, the installation fails entirely.

For example, if the Retail or Call Center configuration key is disabled, the installation will be interrupted with an error such as:

Correlation ID: 2f6fd346-2449-4cda-96a7-365a53163f33

Error Details:

msdyn_ArchiveServiceAnchor: NotProvided

msdyn_SalesOrderArchiveTablesVirtualEntities: Import Failed

Error Code: 0

Description: Unable to complete updates to the Track Changes option for table 'MCRSalesTableBiEntity'.

Exception Details:

Change tracking cannot be enabled because the data source 'MCRSalesTable' in the data entity 'MCRSalesTableBiEntity' references the disabled table 'MCRSalesTable'. Please enable the configuration key 'MCRCallCenter' associated with the table.

Suggestion:

Enhance the installation logic of the Long Term Data Retention app to gracefully skip (or optionally log) entities referencing tables that are unavailable due to disabled configuration keys, rather than causing a full installation failure. This would make the application more robust and compatible with environments where certain features are intentionally turned off.

Benefits:

• Increases the flexibility of installation across various D365FO configurations
• Reduces setup errors and support tickets for standard installation scenarios
• Aligns with modular deployment best practices by supporting partially enabled configurations