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.
I have not seen a direct solution to this (although advanced string
user_attributes support wildcards, I don’t think that’s an applicable
solution). I have seen the use of additional dimensions used as Yes/No
filters to accomplish this though. My col...
Hi!If you are just moving one Look or piece of content, you can
manipulate the
URL:https://help.looker.com/hc/en-us/articles/360001288308-Changing-the-Model-or-Explore-of-a-LookIf
you have multiple pieces of content and the old project is no longer
g...
I would check out the link documentation, as it is explained in more
depth there than I ever could!But, taking their example from the
“Example: Passing an existing filter value to linked content” section, I
think your measure would look something lik<!-- -->...
Hello!It looks like this might be due to how Looker names the child
dimensions from a dimension group.The name of the dimension you defined
is “actual_del”. Looker will add “_timeframe” for each dimension created
in this group (as specified by the ti...
Sounds like a perfect fit for a CASE statement.If you’re not too
familiar with the SQL syntax for this, there’s an easy LookML
version:https://docs.looker.com/reference/field-params/casefor your
fruit example, assuming “grocery” is a dimension alread...
