web
You’re offline. This is a read only version of the page.
close
Skip to main content
Community site session details

Community site session details

Session Id :
Finance | Project Operations, Human Resources, ...
Answered

Archive with Dataverse long term retention error on Dataverse tables when creating a job

(4) ShareShare
ReportReport
Posted on by 128
Hi !
 
We're trying to implement Archive with Dataverse long term retention in my D365FO Dev environment. This is an UDE environment.
 
On creating a new Long Term Retention Job (General ledger) I follow the wizard steps. After going through the steps successfully, I get this error when the job is being created:
 
An error occurred while creating the long term retention job. mserp_generaljournalentrybientity : Entity is not available for archival.
 
A similar thing happens when I try the Inventory Journal:
 
An error occurred while creating the long term retention job. mserp_inventjournaltablebientity : Entity is not available for archival.
 
I checked all things I can think of:
The tables exists in Dataverse
The tables contains data
Permissions are OK (Admin in all environments)
There are no customizations on any of the tables involved
All versions (D365FO and the dataverse apps) are up to date
The tables have the flag visible = true
 
Did any one see this before and maybe know what could be going on ?
 
Thanks,
Gerard
 
 
Categories:
I have the same question (0)
  • Gerard Verbruggen Profile Picture
    128 on at
    Archive with Dataverse long term retention error on Dataverse tables when creating a job
    Hi All,
     
    Stupid mistake from my side: I overlooked the isArchivalEnabled on one of the entities. After setting it to true, the archival started.
     
    Thanks for your input !
     
    Cheers,
    Gerard
     
     
     
     
  • Suggested answer
    Sagar121 Profile Picture
    354 on at
    Archive with Dataverse long term retention error on Dataverse tables when creating a job
    Hi, Please see exact solution in MSFT FAQ here
     

    Case 3: Virtual entity that isn't eligible for archival

    Error message

    Failed to validate if retention is enabled for finance and operations apps ve : generaljournalentrybientity... entity isn't eligible for archival

    Resolution

    1. In the maker portal, go to Tables > Available Finance and Operations Entity.

    2. Ensure that the Refresh column is visible.

    3. Refresh the previously mentioned entity.

       Note

      If custom fields were added to the backing table of the entity (for example, GeneralJournalEntry), ensure that all custom fields are added to the entity before you refresh it.

     
  • Gerard Verbruggen Profile Picture
    128 on at
    Archive with Dataverse long term retention error on Dataverse tables when creating a job
    Hi Cyrille,
     
    Thanks for your reply. I'm pretty sure I checked that... My environment is down at the moment due to some other issue so I cannot recheck at the moment. I'm of next Monday-Wednesday so I probably get back here end of next week.
     
    Cheers,
    Gerard
     
  • Verified answer
    Cyrille Nembot Profile Picture
    149 on at
    Archive with Dataverse long term retention error on Dataverse tables when creating a job
    The error you're encountering indicates that while the entities exist in
    Dataverse, they haven't been explicitly enabled for the archival
    process within the Long-Term Retention (LTR) framework. In your UDE
    environment, you need to ensure that the specific entities (mserp_generaljournalentrybientity and mserp_inventjournaltablebientity) are not only present and visible but also have the IsArchivalEnabled property set to true
    within their entity definitions in Dataverse. This is a separate
    configuration from general table visibility or permissions and is a
    prerequisite for an entity to be recognized by the archival job creation
    wizard. You will likely need to use a solution-aware tool, like the Solution Explorer in Visual Studio
    or a similar deployment mechanism, to access the entity's underlying
    metadata and verify or modify this property, as it may not be adjustable
    through the standard UI and often requires a solution import to change.
  • Gerard Verbruggen Profile Picture
    128 on at
    Archive with Dataverse long term retention error on Dataverse tables when creating a job
    Thanks André,
     
    I will do so and report back here when I have an answer.
     
    Cheers,
    Gerard
  • André Arnaud de Calavon Profile Picture
    297,331 Super User 2025 Season 2 on at
    Archive with Dataverse long term retention error on Dataverse tables when creating a job
    Hi Gerard,
     
    I haven't seen this behavior myself. In case you don't have customizations in this UDE, you can create a ticket for Microsoft Support.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Andrés Arias – Community Spotlight

We are honored to recognize Andrés Arias as our Community Spotlight honoree for…

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

#1
Sohaib Cheema Profile Picture

Sohaib Cheema 764 User Group Leader

#2
Martin Dráb Profile Picture

Martin Dráb 619 Most Valuable Professional

#3
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 603 Super User 2025 Season 2

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans