On this Page
Docs Menu

Go to Field Parameter List


Whenever sql_always_where or access_filter are used on an explore, Looker applies those restrictions to the filter suggestions it makes to users. This prevents users from seeing a filter suggestion that does not apply to them.

For example, you might be using access_filter to limit users to their company’s data. If one of those users added a Project Name filter, you might not want them to see the names of projects from other companies.

However, you can also simply turn off suggestions in these situations, if they are not needed. To do so, turn off full_suggestions like this:

- dimension: project_name sql: ${TABLE}.project_name full_suggestions: false

Alternatively, if you don’t need to add the sql_always_where or access_filter limits to your suggestions, you may want to use the bypass_suggest_restrictions parameter instead. It is a more performant option in these situations. When you use bypass_suggest_restrictions the full_suggestions default value is automatically switched to false so that the parameters won’t conflict.

Please note that the the suggestions presented to a user for a sql_case dimension will not be restricted when using full_suggestions. Any option that you include in a sql_case parameter will be visible to all users.

Still have questions?
Go to Discourse - or - Email Support