This website uses Cookies. Click Accept to agree to our website's cookie use as described in our Privacy Policy. Click Preferences to customize your cookie settings.
We had the same issue and it is caused by the latest release either
making the timezone parameter on BQ connections mandatory or by the
release somehow dropping the value that is already set. If you check
your BQ connection in Admin (I believe this i...
+1. I’ve also used this approach (invalidate cache via API, hit run_once
API endpoint to trigger PDT rebuilds etc.) in the past and it works
reasonably, although it is a bit clunky.
Hi @shankarr, If your main aim is to affect the values that a user can
filter by then I’d use these options: For scenario 1 I’d use suggest
dimension:
https://docs.looker.com/reference/field-params/suggest_dimension For
scenario 2 I’d use suggestions...