There should be a better way to list / find the dependencies within a file so the consequences of changes can be foreseen.
What stuff in my file will break if I decide to remove or change a:
- (calculated) column
- document property
- marking
- visualization
- ...?
Currently you need to go through all the plots and all the different places where expressions can be used to find if, for example, a document property is used anywhere. It makes it very trick to clean up files and remove functionality so the files tend to grow in complexity.
Hi,
I'm happy to announce that extended and improved library search expressions for dependencies have been implemented in Spotfire 14.8:
New library search operators (ANCESTOR_OF and DESCENDANT_OF) allow searches for ancestors or descendants of items.
It is now possible to search the library using prefixed library item type labels (for example {{type::spotfire.sbdf}}, not only {{type::sbdf}}).
Note this is a stepping stone in the direction towards an easier library lineage understanding.
For more information, see the What's new in Spotfire 14.8 and the release notes and product documentation.
Thanks!!