Dynamics Community Forum Thread Details

install d365 archive by dataverse long term retention

I am getting the following error when I try to install an app in PPAC (Dynamics 365 Archive with Dataverse Long Term Retention).

We have two different projects in our LCS (two different solutions - each D365 project has its own production, UAT, etc.).

The error I am getting is different for each solution.

From one of the solutions, I am getting the following error:

Raw code

Failed to validate if retention is enabled for FnO VE: GeneralJournalAccountEntryBIEntity. Error Message: FnO VE entity: GeneralJournalAccountEntryBIEntity is not eligible for archival. Error code -2147220970

From another project, the error is about the activation of the configuration key for the call center in the Retail module, even though the configuration key is active.

Does anybody know anything about this?

Br,

Savci

Categories:

Power Platform integration

Hi @SA-23121343-0,

I have encountered these specific errors before. They are known installation blockers documented in the Archive with Dataverse Long Term Retention FAQ. Here is how to fix both:

1. Fix for "GeneralJournalAccountEntryBIEntity is not eligible for archival"
This error occurs because the Virtual Entity metadata in Dataverse is stale or the entity hasn't been flagged as "Refreshed" yet.

Go to the Power Apps Maker Portal (https://www.google.com/search?q=make.powerapps.com) and select the Dataverse environment linked to your F&O.
Go to Tables > All.
Search for the table "Available Finance and Operations Entity" (mserp_availablefinanceandoperationsentity).
Open the data (Edit) for this table.
Search for GeneralJournalAccountEntryBIEntity in the Name column.
Change the Refresh column value to Yes (or ensure the record exists and is active). This forces Dataverse to re-sync the entity properties from F&O, recognizing it as eligible for archival.

2. Fix for "Call center in the Retail module" error
The installation script checks if Change Tracking can be enabled for the MCRSalesTableBiEntity. This entity has a hard dependency on the Call Center configuration key.

Even if you have the "Retail" module active, the specific sub-key might be off.
In F&O, go to System Administration > Setup > License configuration.
Expand Retail > Retail Channels.
Ensure the checkbox for Call Center is explicitly checked.