User Voice

Lovely! :)

Confirmed to be introduced in 2025 R2 :)

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?

Hi Michał,

I did some testing and it looks like it is possible to set row coloring based on a calculated column, but it requires a bit of a workaround.
So in short, the row coloring is working without any issues for all the types of calculated columns (text, number etc.) except for the "Lamp" type.
How to make it work for lamp:
-change the configuration of the calculated column - from type Lamp to type Number
-configure your row coloring based on this calculated column and save the changes
-go back and change the type of the calculated column from Number back to Lamp

It should work just fine.
We'll make sure this is fixed in one of the next releases.

Cheers
Dawid

We didn't receive any other voices regarding this case. Therefore, I'm closing the thread.

Hey Martin, as such we won't be introducing the alternating table row colors functionality. However, we work on other functionalities that should address your case. Stay tuned for updates.
For now, I'm marking the thread as "closed" since we need to wait for new functionalities to be introduced.

It's exactly as Daniel stated. The intoduction of phases and actors in a sense enforced such change and we'll stick to it.

Thanks for noticing. It should be all right now.

This case is inderictly poses a question where is the optimal balance between standardization and customization. After internal discussion, we believe standardization is more important for a unified UX for all of our users. Therefore we plan on sticking with the default indicators of repors and dashbaords.

I'm closing the thread then :)