Spotfire Ideas Portal
ADD A NEW IDEA

Library

Showing 178

Enable `search-query` parameter in `delete-library-versions` CLI to accept multiple values

Per reference , the delete-library-versions CLI has a parameter search-query. Currently, it doesn't support searching for multiple file types using a single command - e.g., --search-query="item_type::sbdf OR "item_type::dxp". Enabling the said par...
23 days ago in Spotfire / Library 0 Already exists

Allow Preconfigured Library Shortcuts on Files and Data Flyout

Just as the Files and Data flyout contains a Spotfire Library and (optional) Data Catalog link, it would be ideal if administrators could pre-configure library searches (using existing library search functionality) and park them in the Files and D...
about 1 month ago in Spotfire / Library 0 Future Consideration

Add "Search" as Permission Level

Add another level of folder permission to control whether or not the contents of the folder will be included in library search results. This would allow library administrators to limit visibility to simplify searching (for ad-hoc, testing, archive...
about 1 month ago in Spotfire / Library 0 Future Consideration

Other default button when deleting files/folders

Currently the default button after choosing 'Delete' (Spotfire Client and Web) is Yes [instead of No] resp. Proceed [instead of Close]. That can cause unwanted delete actions, especially when using a keyboard to navigate through the Library Admini...
about 1 month ago in Spotfire / Library 0 Future Consideration

Searching chart information in Library

I wish there were the ability to search for chart information (type, description, title..) in the library without opening Spotfire dxp. If we have a chart search function, we can refer to similar charts created by others and avoid creating duplic...
about 2 months ago in Spotfire / Library 0 Likely to implement

Need help for setting an alert for new report/infolink created in PRD

We are working on a topic for the spotfire metadata completeness check. Which means, report/infolink descriptions should be always available. If any new report/Infolink is created directly in Production or transported from Test, and if the descrip...
5 months ago in Spotfire / Library 1 Future Consideration

Support simultaneous working on same Spotfire file as e.g. in Google suite

This might be limited to Business Authors as it would most probably not work in the client. Idea would be to be able to truly simultaneously collaborate on the same Spotfire analysis as you know it from Google Docs or Office 365. This would includ...
6 months ago in Spotfire / Library 0 Future Consideration

Improved API to read metadata and lineage for library items

From my external application, I want to call a Spotfire Library API (preferrably REST) to read metadata for library items and their dependencies. This can be seen as an enhancement to the current LibraryService API (SOAP), but more detailed met...
7 months ago in Spotfire / Library 0 Likely to implement

Ability to "publish" a version of an analysis file for others, and continue to modify it for myself

I would like to be able to publish a version of an analysis file for my colleagues, so they can view it. but at the same time I want to continue developing the analysis file with the next improvement without having my colleagues see the intermedia...
8 months ago in Spotfire / Library 1 Future Consideration

Fix Analyst Client and Web Player error when Spotfire Library Folder is too big.

When the Spotfire Library has a large folder, the clients are unable to display the folder contents, because the API request is bigger than 64Mb. The workaround is to increase this SOAP request configuration. One solution would be to page the outp...
9 months ago in Spotfire / Library 2 Future Consideration
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