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

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Finance | Project Operations, Human Resources, ...
Suggested Answer

Feature Management Workspace Not Opening on Dev Machine, Keeps Loading

(2) ShareShare
ReportReport
Posted on by 1,044
Hi dear community!
 
After I moved an old AxDB of version 32 to an 45 version environment, the feature management workspace is not opening.
It keeps on loading giving me the "Please wait, we're processing your request." dialog.
Screenshot:
  
 
When I try to debug on the Feature Management form "init()" method, it reaches to last line in method the debugger does not follow anymore. The code line is as follows:
SysDataverseUtility::NotifyUserToLinkDataverseEnvironment();
I tried on another dev env of version 45, I moved the 32 AxDB and did a full build and still I faced the same issue where I couldn't open the feature management form.
 
If anybody is familiar with this issue, please advise.
 
Any advice is appreciated !
 
My regards.
 
 
Categories:
I have the same question (0)
  • André Arnaud de Calavon Profile Picture
    305,173 Super User 2026 Season 1 on at
    Hi Momochi,

    What is the reason to put a 10.0.32 database into an 10.0.45 environment? Did you synchronize the database after the restore action?
  • Momochi Profile Picture
    1,044 on at
     
    It has historical data for our custom model that is valuable for training, debugging and integration development.
     
    And yes, I did a full build and sync.
     
    Though after applying the 32 AxDB, modern D365FO apps which will be available on the dashboard were removed.
  • André Arnaud de Calavon Profile Picture
    305,173 Super User 2026 Season 1 on at
    Hi Momochi,
     
    It is hard to make any suggestion as it is not clear what exactly is causing this. Maybe you can start the FeatureManagement update logic manually first by starting the class FeatureManagementCheckForUpdates.
     
    You can do that by changing the url to: ?mi=sysclassrunner&cls=FeatureManagementCheckForUpdates
     
    If that is not helping, you can export the data from your custom model in case the features are supported with data entities. Until what version of Dynamics 365 was this working correctly? I recommend to have the environment and related data updated regularly.
  • Suggested answer
    Deepak Agarwal Profile Picture
    8,994 on at
    I would suggest to first update old environment from .32 to .45 (if feasible) and than take DB back to use in your another environment which is already on .45

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

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Meet the Microsoft Dynamics 365 Contact Center Champions

We are thrilled to have these Champions in our Community!

Congratulations to the April Top 10 Community Leaders

These are the community rock stars!

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

#1
Giorgio Bonacorsi Profile Picture

Giorgio Bonacorsi 722

#2
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 605 Super User 2026 Season 1

#3
Subra Profile Picture

Subra 547

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans