This document (including, without limitation, any product roadmap or statement of direction data) illustrates the planned testing, release and availability dates for Spotfire products and services. It is for informational purposes only and its contents are subject to change without notice. Planning to implement - generally 6-12 months out. Likely to Implement - generally means 12-18 months out.
Copyright © 2014-2023 Cloud Software Group, Inc. All Rights Reserved.
Cloud Software Group, Inc. ("Company") follows the EU Standard Contractual Clauses as per the Company's Data Processing Agreement.
Terms of Use |
Privacy Policy |
Trademarks |
Patents |
Contact Us
Customer wants to capture all document properties with bookmark, rather than only those used in current active page(current behavior).
Thanks Christof, that makes sense, now I get it.
By property, I mean "Document Property". Sorry for the confusion. So title should be "Set certain document properties by Bookmark".
Hi Christof,
I may not get the full picture here, but you can already define what aspects to capture at the time of Bookmark creation: Use Add bookmark Special (right click on the + in the bookmark panel) and select the aspects you want to capture in the bookmark. See screenshots attached.
It is also possible to select what aspects to apply from a given bookmark, by using the Apply Bookmark special (right click on the bookmark in the bookmarks panel and select apply special).
If I misunderstood something in your request we should probably get on a phone call to resolve it faster.
Hi Niklas,
I think the Name of the idea is still valid. Also the description is still valid. There should be a good way to do this, the way it is done at the Moment (save what is used on the active page) is not a good one.
So what would be good is to have the possibility to adjust which properties are save at the time of Bookmark creation. Furthermore it would be good to have the possiblity to adjust which properties are set at the time of applying a Bookmark.
Christoph and Oliver, thanks for sharing your thoughts here. As you identified at least part of the Idea is possible today, so I think we have two options:
1. Close this Idea and if you feel there is something missing add a new one
2. Change this Idea description and name to reflect what is missing
I'll leave it to Christoph to decide since you created the Idea on the first place. Let me know how you want to proceed?
OK, got me.
For applying manually it is there, but for automation service it is missing.
Anyway, it is much better if the unwanted properties are not stored in the bookmark. Then no one can make a mistake by accident if he applies the bookmark without knowing...
Hi Oliver, what you want to achieve should be possible with "Add Bookmark special".
I understood this request different:
E.g. if you save a bookmark for an active page SP saves the filter setting and other visualisation details like data limitation, expressions for the axes and so on. What I'd like to have is the possibility that only filters are saved. This separation is possible when you apply bookmarks in action controls, but not when saving bookmarks, applying them manual or using them for automation services. These are the places where I'd like to have the same selections as for applying bookmarks in action controls.
We use the bookmarks to have different filters for automation services. When I change a simple expression or even a name on an axis I have to update 40 (!) bookmarks with all their different filter settings. This takes me one hour each time! It would be much easier if I could say "save only filters in bookmark". The I can make changes to the visualization independently.
I actually looked into this a bit more. In principle this is possible because (as the manual says, RTFM), only properties which are "used on the active page" are saved. So you can make a page with input fields for the properties you want to save and then create the bookmark there. However I think this is annyoing.
Furthermore, there's no way to save ALL properties (contrary to what I though). This is a problem because we have analysis files where users can (and have to) adjust properties. When a bookmark is created, the fact that properties "used on the active" page only are save creates confusion, because for some users saving the properites worked, for others not.