Jump to content
We've recently updated our Privacy Statement, available here. ×

Config block filter is applied before row level security when opening in webplayer


Jesse Small

Recommended Posts

I am currently using row level security by "adding columns" to my main data table and performing an inner join to filter out any data that the user is not supposed to see. This works fine and loads the data as expected. I am caching the analysis in the webplayer and have ensured that my user information link is updated for each new user and not included in scheduled updates.

If I open the analysis with no config block filters all the data is loaded as expected.

The problem occurs when I try to use the SetFilter feature of the config block, it applies the filter to the correct column but it looks as though its being applied to an empty data set.

It says (filtered 0 of # results). If I remove the filter and re-apply it everything works fine.

 

Based on this information it looks as though the config block filter is being applied before the dataset can be correctly filtered based on the personalized information link.

I am wondering if this is a bug or how I can apply my initial filters and ensure they are applied AFTER the dataset has been filtered by the personalized information link.

 

Let me know if you need me to provide any information.

Link to comment
Share on other sites

  • 1 month later...

You can try setting document property value in config block and trigger set filter iron python script on change of document property value (instead of passing filter value in config block)so in the meantime row level security would get applied and then iron python would set appropriate filter value.

Iron Python references:

https://community.spotfire.com/wiki/ironpython-scripting-tibco-spotfire

https://community.spotfire.com/wiki/how-get-or-set-specific-filter-using-ironpython-script-tibco-spotfire

Also, you can try modifying row level security application to be handled only by filters and not by adding any joins/columns so that would reduce execution time on loading of analysis.

https://support.tibco.com/s/article/How-to-Apply-Row-Level-Security-on-multiple-columns-in-TIBCO-Spotfire

This would work for single column as well.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...