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.
Hello Pete, System Activity can be used to show which fields are being
used. I would use system_activity.history explore with query.model,
query.explore and query.fields_used to start. Caveats: - History data is
from queries run in last 90 days- I th...
Hello Ashish, It would probably be helpful if you provide some
additional context or example. I'm not sure what you mean by 'global'
filter here (i can imagine that referring to a dashboard/report level
filter that is applied to all visuals on that d...
Hello jcdufault, I love to see these clever approaches in the spirit of
DRY. TLDR: I was able to test and confirm that you should be able to use
liquid likein the derived table to pull in raw sql from a dimension.
sql: select * from schema.table_b wh...
Glad you found that approach for average. If it works in some cases but
not on other places (e.g. depending on filter as you mentioned), I'm
guessing this is still a case like I described above where we have cells
where there's actually no data at al...
Hello ryukiman07, If I understand correctly, your issue is with the end
date: the logic is not including the end date entered by the user. I
would note that this is the standard way that date ranges are used in
looker filters: the end date is typical...
