Our Explores have a conditionally_filter where by default it will only show values with a createdDate of 30 days or newer unless the user already has a createdDate filter specified (so they can query for data older than 30 days. E.g.
explore: my_explore {
conditionally_filter: {
filters: [createdDate_date: "30 days"]
unless: [createdDate_date]
}
}
However, when one adds an explicit createdDate filter with a different value, and adds an additional field to filter on, if one clicks on that filter field to see suggestions they only see values limited to the default conditionally_filter and not the user specified createdDate filter.
So imagine if I have a table and today's date is 2024-12-30:
name | createdDate |
Jack | 2024-12-15 |
Jill | 2024-11-01 |
And in my explore I add a filter on name - if I click on the filter suggestions I will only get Jack as a suggestion even if I add a createdDate filter to my explore with a time range that would include Jill. The suggestion query ignores it.
Solved! Go to Solution.
Are you seeing this behaviour in the context of a dashboard, or an explore? (I see you mention explores in your post, just confirming)
Dynamically updating filter suggestions based on changes to filters is only a functionality that is available in the context of linked filters in dashboards, I don't believe it is expected to work at the explore level.