As of 3.48 the now()
table calculation will evaluate in the user or query timezone, falling back to the application timezone when no query timezone has been set. As a reminder, this is what those different timezones mean:
This change ensures that now()
gives you the same timezone as the results you’re combining it with. This should help to avoid confusion and the general tedium that comes with managing timezones.
One thing to keep in mind is that
now()
might not match the time that you see on your computer if it just so happens that your Looker timezone and your computer’s timezone don’t match. This is the sort of thing that could happen if, for example, your company is based in California (and converts everything to PST) but you happen to be working from New York.