About MikeD

MikeD · 06-04-2018

The ProblemUser Defined Content (Dashboards and Looks) are not easily portable across Looker instances, nor can they be backed up and restored to a known state easily. It is not easy to monitor content creation, user activity, etc. In particular, it ...

MikeD · 04-29-2020

My preference is to have a file per view. The main benefit is that it reduces the chance that two developers might make changes to the same file that are in conflict. Merges become easier. If you have multiple models in the same project, you can indi...

MikeD · 06-22-2018

Not at the moment, Levi. But I will look into adding that!

MikeD · 04-27-2016

The load_configuration needs to be set through the API, not in the LookML.

MikeD · 04-12-2016

Here is a handy shell script that can be used to set up a prefetch from a command line. #!/bin/bash CLIENT_ID=YOUR_CLIENT_ID_HERE CLIENT_SECRET=YOUR_CLIENT_SECRET_HERE END_POINT=https://learn.looker.com:19999/api/3.0 DASHBOARD=73 DASHBOARD_FILTER='[ ...

MikeD · 09-02-2015

Just a note on this… I had a value with embedded characters so the generated url wouldn’t work. I needed to do this…

My Stats

MikeD's Bio

Badges MikeD Earned

Recent Activity

Gazer - A Command Line Tool for Looker Content Management

Re: As per best practices, is it advisable to have different files for all views or have them added to a single file?

Re: Gazer - A Command Line Tool for Looker Content Management

Re: Prefetching (3.36+)

Re: Prefetching (3.36+)

Re: Using URLs and Query Parameters