Hello,
I would like to know what is the behavior(executed query) at the time I want to pick some value from a filter which is not part of the dashboard(main query), because it is taking too long and it does not work at the end. Thank you.
Regards!
Hi Isma! Filter suggestions will run a select * against the field being filtered to populate the suggestion list Building point-and-click queries - Omni Docs
There are other ways to get that list to appear, such as
Suggestion List - describe a list of suggestion options
Suggest From Field - populate suggestions from a different field
Happy to take a closer look if you don’t mind reaching out to Support via your Teams/Slack channel or by email support@omni.co
Thank you for the reply, but unfortunately what you suggested is using hard coded data right?, and I want it to be dynamically, so I am still facing an issue at the time I want to pick some value in the filter, this is the story:
There is a topic that looks for 1 year of data. While it performs well and handles adding new columns as expected, I’ve encountered an issue with data filtering.
When applying a new filter and trying to pick a value, Omni appears to ignore any existing dashboard filters. Instead, it retrieves filter values based solely on the initial “always_where_sql” setting of one year. This doesn’t make sense to me, especially since I have already limited the dashboard view to two days, as shown in the image below. The filter continues to query the full year regardless of those active constraints, but it never loads the values.
Regardless of the filters applied on the dashboard, the query Omni executes to fetch filter values remains structured like this:
Thank you.
Hi Isma, I’m having trouble viewing those images, would you mind reaching out to Support via your Teams/Slack channel or by email support@omni.co? Happy to continue the thread there and take a closer look.
Hi James,
Sure, let me send this by email. Thank you so much for your response.
Regards!