Home > User Voice > No private report views in 2024 or higher

No private report views in 2024 or higher UNDER REVIEW
14

We are currently in the process of upgrading from the 2023 to 2025. Unfortunately, we were hit with some very bad news—starting from the 2024 version, the ability to define private views for reports configured on the dashboard has been removed.

This is a significant issue for us, as users rely heavily on this functionality. Once the upgrade is deployed to the production server, it is likely to cause considerable disappointment.

Personally, I don’t quite understand why this feature was removed, and I believe it is a major step backward in terms of UX. Instead of using personalized private views on the dashboard—a place that consolidates data from multiple areas—users will now be forced to reconfigure reports every time they enter the dashboard or navigate between individual reports to access the desired view.

There is no mention of this change in the changelog. Support has informed me that the changelog will be updated to include information about the removal of this functionality.

What makes this situation even more paradoxical is that, from a configuration standpoint, both reports and views (whether application-based or those set up on the dashboard) are stored in the database as identical elements in the same table. The only difference is that the functionality has been stripped from the front-end.

WEBCON: Is there any chance this feature will be reinstated in the future?

COMMUNITY: Do you also find the removal of this functionality to be a major issue?

In reply to: Michal Rykiert

We're reviewing the situation as it's a bit more intricate than you described. We'll update this tread whenever a decision is reached.

We are also very interested in having private views reintroduced. The setting for this feature still appears to exist, but in the frontend it currently doesn’t seem possible for users to create their own private views on reports.

We are not running the latest version on our server yet, so if this issue has already been addressed, we would appreciate knowing from which release onward the fix became available.