View - Read Only Mode
Idea Logged
Hello,
sometimes you want to look at a View, the Fields and other options to get a better understanding of the Data. There are two options for this:
Option 1: View Clone
Option 2: View Edit
The idea is a Read Only Mode. With this you can read through every option in the view, without customizing any field, tables, joins or other options by accident. This pretend some problems from the clone and edit view:
- Biggest Problem: To much View (Clones) in the DB to fill up -> Performance Issues
- Edit Mode blocks every report change
- Accidents happens and saves wrong options
- 2 Admins can not look into 1 view -> Read Only Mode so all Admins can look into it at the same time
This is a new good option for views.
I like this idea
Hi Janus,
Many thanks for contacting Yellowfin with your Idea! This looks like a great potential enhancement. I'll raise a task for the developers to review and hopefully we can see this added as a future feature in Yellowfin!
Kind regards,
Chris
Hi Janus,
Many thanks for contacting Yellowfin with your Idea! This looks like a great potential enhancement. I'll raise a task for the developers to review and hopefully we can see this added as a future feature in Yellowfin!
Kind regards,
Chris
Hi Janus
I also like the idea of opening a view in read only mode.
With regard to filling up the repository with cloned versions of your view, you can minimise this if you remember to delete your cloned version rather than just closing the view editor:
I was reluctant to do this for a long time, but I promise you that as long as you see "Delete Version" you will only be deleting your clone. If you edit the view directly instead of cloning it you will see this instead:

In this case, DON'T do it (unless you really want to delete the original view).
Hi Janus
I also like the idea of opening a view in read only mode.
With regard to filling up the repository with cloned versions of your view, you can minimise this if you remember to delete your cloned version rather than just closing the view editor:
I was reluctant to do this for a long time, but I promise you that as long as you see "Delete Version" you will only be deleting your clone. If you edit the view directly instead of cloning it you will see this instead:

In this case, DON'T do it (unless you really want to delete the original view).
Hey Robert, hey Chris,
thank you for your positive feedback on the idea :).
Regarding the deletion of the clone: we proceeded that way with the "Delete Version". However the issues mentioned above still persists. In addition, a long time ago one employee accidentally deleted a view, as you pointed out in your warning.
So, how do we continue with this Idea?
Best Regards,
Janus
Hey Robert, hey Chris,
thank you for your positive feedback on the idea :).
Regarding the deletion of the clone: we proceeded that way with the "Delete Version". However the issues mentioned above still persists. In addition, a long time ago one employee accidentally deleted a view, as you pointed out in your warning.
So, how do we continue with this Idea?
Best Regards,
Janus
Hi Janus,
I've created an internal enhancement post for the developers to review. Once they've had a look they'll put it into a feasibility review and determine whether it'll be a good fit for Yellowfin. As I said, this does seem like a good idea so hopefully we'll see it added to the roadmap soon!
When I have some news to share, I'll let you know.
I'll move this to Idea Logged for now.
Kind regards,
Chris
Hi Janus,
I've created an internal enhancement post for the developers to review. Once they've had a look they'll put it into a feasibility review and determine whether it'll be a good fit for Yellowfin. As I said, this does seem like a good idea so hopefully we'll see it added to the roadmap soon!
When I have some news to share, I'll let you know.
I'll move this to Idea Logged for now.
Kind regards,
Chris
Hey Chris, hey Robert,
any progress on this topic?
If we get this imported this year, I get a pizza for free 😄.
Best regards,
Janus
Hey Chris, hey Robert,
any progress on this topic?
If we get this imported this year, I get a pizza for free 😄.
Best regards,
Janus
Hello Janus Engler
We would like to inform you that the issue reported under this ticket has been marked for resolution in the upcoming release version. Please note that while this is the current plan, there is a possibility of change depending on any unforeseen technical considerations.
That said, we are pleased to confirm that, as of now, the fix is scheduled for the next release. We will continue to monitor the progress closely and ensure you are promptly updated with any changes or further communication from the product team.
Thank you for your patience and understanding.
Thank you,
Yamini Naidu
Yellowfin Technical Support
Hello Janus Engler
We would like to inform you that the issue reported under this ticket has been marked for resolution in the upcoming release version. Please note that while this is the current plan, there is a possibility of change depending on any unforeseen technical considerations.
That said, we are pleased to confirm that, as of now, the fix is scheduled for the next release. We will continue to monitor the progress closely and ensure you are promptly updated with any changes or further communication from the product team.
Thank you for your patience and understanding.
Thank you,
Yamini Naidu
Yellowfin Technical Support
Replies have been locked on this page!