Hi everyone,
While gathering information about Conversational Agents, one of the best practices is to reduce the explore and limit the amount of fields the agent will look into to get the precise information. It’s suggested to use the parameter hidden to hide all those fields you won’t be using. However, if you hide fields that explore will not be reusable.
We tried to add tags such as tags: [“CCV_Gemini”] in all fields in our explore and try to use them in the context of the agent as an alternative to hiding.
Could anyone confirm if agents can’t read ‘tags’? If so, does anyone know an alternative to avoid creating new explores?
Thanks in advanced
I am intending to follow the approach recommended in the LookML best practices for Conversational Analytics documentation by Extending a base Explore to use in Conversational Analytics (with an agent). While this does create a new Explore, it is based on an existing Explore, so I don’t have to duplicate and maintain code that is shared by both.
I have only just started this process, but my plan is to create extended Explores specifically for use in Conversational Analytics / self-service exploration via Explores, and use a naming convention to differentiate them: name_of_base_explore_ssa.explore.lkml (sse = self-service exploration). We have very large Explores, so I’m going to trial creating smaller, curated Explores specifically for Conversational Analytics. I don’t want to be adding synonyms etc. to hundreds of fields, which I only want end users to focus on key fields.
I don’t know if this will end up being our final approach, but it seems like a good approach to take while testing capabilities.
1 Like
Hey,
Hope you’re keeping well.
In Looker, tags are metadata for organization and search within the Looker UI, but they aren’t parsed or used by Looker’s conversational agents (including the new Gemini integrations) to filter fields in an explore. Agents rely on the explore definition and field visibility settings, so hidden fields are excluded from query contexts. If you want to limit what the agent can access without creating entirely new explores, you can create a derived explore using extends in LookML, include only the needed fields, and keep the original explore intact. This approach lets you control the agent’s scope while avoiding duplication of complex definitions.
Thanks and regards,
Taz
1 Like