Splunk version 10.4 Victoria: I'm experiencing inconsistent filtering behavior in a Dashboard Studio table that uses a text input token. The table contains multiple pages of results. If I enter a filter value that is visible on the first page of the table, the filter works as expected. However, if I navigate to a later page (for example, page 5), copy a value from one of the displayed rows, and immediately use that value in the filter, the table returns no results. Interestingly, if I first navigate back to page 1 and then apply the exact same filter value, the expected result is returned correctly. Similarly, if I reload the dashboard and apply the filter again, it works as expected. What makes this confusing is that the value definitely exists in the dataset and the filter logic itself appears to be correct, since the same value can be found after returning to page 1 or after reloading the dashboard. This makes me suspect that the behavior may be related to table pagination, datasource refresh, or Dashboard Studio's handling of the current table state when a filter token changes. Has anyone encountered an issue where token-based filtering behaves differently depending on the currently selected page of a paginated table? Is there a way to force the table to reset to the first page whenever a filter is applied? I checked a few articles and it seems to be a bug previously Solved: Tokens: Why is the search element with depends att... - Splunk Community, is this bug resolved?
... View more