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.
Hi @rufus. I generated the NDT LookML and noted that all the custom
filter syntax disappeared. I think in this case it was confirming a lead
capture date was prior to a purchase date. This is possible via custom
filter syntax, but I couldn’t figure o...
I was thinking about the “Custom Filter” query syntax (Looker
Expression) in an explore, which is necessary when, e.g. comparing one
dimension to another. Is that possible? It’s not a big deal to define a
derived dimension in a view file somewhere, b...
Thanks, @lloydtabb. I definitely get the potential gotchas here, so it’s
good to hear you guys are being careful. Going by the principle of least
surprise, I’d say I’d expect an explore of a view based on an NDT to
match exactly the results in the ex...
@rufus, I’m not sure if @devwiredau ever wrote into support, but I’m
running into the exact same issue with timezones. Here’s an overview of
the syntax: In view v1: dimension_group: event_time { type: time
convert_tz: yes timeframes: [ time, date, we...
Probably a more important question than my other one. Is it possible to
use a custom filter in an NDT? It doesn’t appear that the syntax
supports it, yet.