This issue will only happen when there is a user-specific table and the filter you are setting is a column in the user-specific table and it is a scheduled analysis. In the scheduled analysis case, the filter is set before loading the user data, and that will not work for the filter types listbox and checkbox. In this case, the data table is empty when setting the filter configuration block and therefore it fails. Whereas in the case when the analysis is not scheduled, the filter value is set after all data is loaded.

All

To overcome this, you can use another filter type. The text, radio button, range, and item filter should work. These filter types work even if the data value hasn't been loaded.

In case the column is a multi-select column and you cannot provide radio buttons or even text boxes which are less intuitive for the users, you can set a document property using the configuration block instead of using SetFilter. The value of the document property is set to the same value as the SetFilter in the configuration block.
A python script that executes after the analysis has loaded reads the document property and sets the values of the list box filter.

For listbox and checkbox filters, configuration blocks cannot set filter values to a value that doesn't exist in the filter when an analysis in Scheduled updates has a data table that is user-specific. This article explains a workaround to use another filter type in this case.

• Create a Configuration Block in Spotfire,  Spotfire Community article
  • https://community.spotfire.com/articles/spotfire/create-a-configuration-block-in-spotfire/