PROBLEM: When saving an analysis as a DXP or into the library, with the analysis Spotfire saves a snapshot of cached data from the data tables at the point in time that the developer initially loaded/refreshed them. Generally this could be desirable, but in cases where we wish to implement a report with row-level filtering, the net affect of this cached data is that when loading the analysis end-users may momentarily see the cached data saved by the developer (which could include sensitive or restricted rows) until Spotfire autonomously reloads the data tables.
We do not wish to create a splash screen tab to avoid this (since this isn't properly fixing the issue, nor a desired design feature), and the other workaround of marking rows and deleting them before saving the analysis is not self-explanatory for less experienced developers.
SOLUTION: Add a prompt upon saving an analysis to selectively purge cached data from data tables.
Ok, I thought the solution was describing a workaround, but it's not, that's describing the actual fix.
Two other possible solutions:
These solutions would be preferable since you can set them on the DXP and not need to remember to clear the cache every time you save it.
Can you detail the solution in a step by step manner ?