How to model your data in LookML? Tips and hacks Please

Hi all,

Apart from the documentations and blog, I would like to know the best practice of data modeling in LookML with some tips and tricks. Practiced examples from people will help a lot.

And, your view on : single explore with multiple joins, having vast number of explores and creating multiple derived tables.

Thanks

Hey Adai, welcome! This is a big question, and a great one. There’s a lot of modeling best practices out there, but I’ll kick off the conversation by providing @fabio’s “Opinionated LookML & SQL Style Guide”. If you haven’t seen it, it’s a fantastic resource for making sure your model is tidy.

It’s not as high level as the examples that you’re curious about, so there’s still lots of room for others to jump in with their own opinions!

Sharing some of your own ideas and opinions, however loosely held, could help kickstart the discussion as well.

Thanks for the shout out, Izzy!

A more-high level take on my ruleset is definitely on the top of my list of things to write about… :thinking:

1 Like

Thanks @izzy and @fabio.