Spotfire Ideas Portal
Currently a multitude of changes to a visualization can affect (break) a bookmark, these include changes to:
We would like the option of a bookmark ‘light’ feature where only the filters are bookmarked and changes not related to filters and their underlying data do not break the bookmark ‘light’. This must be available for the web client users. We currently have 6000+ bookmarks in our environment and it’s becoming very unwieldy to manage and a source of annoyance for our users when they break.
0
Future Consideration
This is also a version control issue. We have DXP files in the library that have been used for several years with bookmarks having been created since the beginning.
As new versions of the file are rolled out, we often change visualizations, create new functions that rely on document properties, etc. Unfortunately full-featured bookmarks will rollback many of these changes! Thus when the user opens Spotfire from the bookmark they are effectively not seeing the later version of the DXP file. We have a python script that can modify a users bookmarks to only contain Page and Filter setting, however this is not a solution.
For us this is a barrier to making a Spotfire DXP file function as an enterprise application.
Agreed, the ability to select what aspects to include in a bookmark and the ability to define a default such that the users would click a + and get those defaults would work.
That would largely work for us...yes. However the Default aspect is the key so that they can simply click the + sign to add a new bookmark and by default it would only save filters, active page and properties.
Paul, Jeremy - OK, so if web player users could create bookmarks in the same fashion as Analyst users, that is selecting what to include in the bookmark, that would work? Possibly with the addition of being able to specify what the default aspects to capture are?
Jeremy and I are both in the same boat. Are users are web player only and we don't have the same option we have in the client. So for us this feature should not be 'already exists'
This solution actually doesn't work for us, as I understand the proposal. Our end users use only the Web player and when we create bookmarks we don't have a special option and our users aren't power users. Preferably we would be able to change the default or be able to create our own task which will create a bookmark with only Filters and Active Page set. This would ensure users only set bookmarks which would not get broken with future updates to our reports.
As I understand the above will work. I will set the Idea to "Already Exists" , but if I have missed something just get back to me and I will reopen it.
Please let me know if that works for you.
Paul
sorry for the untimely response here, I must have missed the notification. It is possible to CREATE a bookmark that only contains filtering. If such a bookmark is set by Automation services it only affects filtering. I attach a screenshot.
Frank,
In our situation we use the Automation Services task “Apply Bookmark,” which doesn’t give you any options about how to apply the bookmark (see screenshot below). In this scenario to handle “normal” bookmarks, we would have to write our own custom “Apply Bookmark” task that only applied certain bookmark options. Correct?
Hi Paul, please let us know if Franks suggestion works for you. Thanks to you Frank for helping out!
Hi Paul,
you can create a "special bookmark" (either via CTRL+SHIFT+B or by right-clicking on the "Add bookmark" button) where you can customize what the bookmark should store (see attached screenshot). Does this fit your needs?
Kind regards,
Frank