I’m trying to use Looker’s Conversational Analytics, In my Explore, I have a date filter defined like this:
I want Conversational Analytics to use machine_summary_ssot.shift_start_date_filter as the date field for filtering. Override the default 7-day range if the user asks for a different time period (e.g., “July 2025”, “last month”, “last 3 days”, etc.) Avoid creating any additional or conflicting filters on other date fields :
The challenge is that CA does not know whether or not to add the new date filter or replace the existing one. I imagine if your CA question explicitly mentioned filtering on “Shift start date filter” it would override the default one, but in this case the question was interpreted to mean the “started at date” instead.
This feature is still new so I’m not 100% on what will work, but some things I might try:
Create an agent that is instructed to interpret any date filter mentioned by the questioner as the “shift start date”
…that’s my only good idea actually. Was thinking you could use a parameter to swap out the filter dimension (along with a calendar table at the root of the explore), or perhaps just remove the default or change it to be a “any date” default… but i only really like my first idea.
If CA supports turn-based interactions then you could program your agent to refuse to answer a question on that explore without the user explicitly asking for a date filter. Then, instruct your agent to interpret the filter by either removing the existing one or altering it, then applying the requested filter.
Thanks for the response, Andy! I have already tried your solution with the agent. Still, it is not solving my issue because the agent is ignoring any other date fields mentioned by the questioner (as I informed him), and is not changing the default of “last 7 days” to the requested date range.
@andy4 I’m also experiencing the same issue. Even now that the product is GA, the problem still persists, and it prevents me from being able to use it.
Is there a timeline to fix it?
I have also found that agents do not always respect the instructions I provide around default filters. For example, I have an instruction ‘Unless the user specifies a date range, restrict data to the last 30 complete days. When this happens, display the message “Showing data for the previous 30 days”.’. Yesterday, it was working as expected… until it wasn’t. Now it doesn’t apply any date filter, and returns values for all time.
I find the lack of consistency more worrying than the fact it can’t interpret my instructions. It means that, even with extensive testing, I can’t be sure what business users will be exposed to
