I’m having a discussion with myself that I decided to open up to the community. Four questions have been on my mind:
- How many of you actively use LookML dashboards?
- Do your users get confused when they are dealing with LookML dashboards vs User defined dashboards?
- Is it time consuming to recreate a User defined dashboard as a LookML dashboard?
- Are LookML Dashboards part of Looker’s roadmap? I’m curious because they seem to still use old lookML.
Where I’m coming from:
Since I started using looker, my team has always used looker defined dashboards. It’s GUI and easy. However, I’ve been caught in a situation a few times where I end up updating a dozen looks in a dashboard, which ends up taking a long time & doesn’t have a lot of transparency.
There are some situations where I’m thinking it would be easier to just have a LookML dashboard, so I can quickly make updates via code rather than manually updating Looks, but I don’t have enough experience with Dashboard LookML to know if that will end up being even more time consuming.
Just looking for thoughts from large-brained people.
@IanT mentioned we are not there yet. LookML Dashboards aren’t able to be favorited, they’re technically not considered “content” since they’re not stored in-database and thus don’t live in Spaces. There is work going on it but just not yet completed.
The UI differences between user-generated dashboards and LookML dashboards is an issue for my organization. We are making UI changes in the user-generated dashboards and then finding that the newspaper layout does not translate to LookML. Is there any movement on synchronizing the two, so we can create the layout using the GUI and copy source to the LookML Dashboard?
I’d also like to add that another benefit of the LookML dashboards is that you can actually demo the changes you make in your models in development mode. With user-defined dashboards, you basically have to break all your dashboards either until you publish, or after you publish until you’ve updated them all.
Glad to hear you are working on it. This was seen as a key value proposition for me with Looker.
I definitely like having both options. We offer a baseline set of dashboards, and also want to support user-generated content, and appreciate the GUI/ease-of-use with developing the non-LookML Dashboards.
If there’s an issue tracker where I can up-vote something like this and track progress, that would be nice as well.
Thanks! I’ll do that.
abbywest hows the progress with the 3 phase plan going, any idea about a timeline for this?
Hi Andrew, you got the wrong person here, you want
@Jiro Im ian@king, was looking out for you at Join but don’t think you made it.
Im happy to make a stab at the answer being a NO though.
Is there an update on this? We are embarking on a project where lookml dashboards (at the end of the 3 phases) would be ideal. It would be great to get a feel for if the phases/steps are miles off, some steps will be ready soon or if all steps and phases are going to be released in one big bang. It would really help for planning and putting together processes at this exact moment.
I just checked in with our product team, Phase 1a was released in 4.12, and they are still actively working on the remaining phases. You can expect more pieces to be released over the next few months!
We’re targeting Q3 2018 to complete phase 2 with API functionality.
No, they will be new endpoints.
Thanks for checking in on this; we’re actively working on a solution and will be in touch as soon as it’s ready.
Please write here also, once you get some solution/answer. 🙂
Are there any updates regarding lookml dashboards? They are such a great idea, but lack updates and some core functionality.
Sorry to hear that, Luke— Could you send over some examples (screenshots would be great if possible) to the support team via help.looker.com? That’d help us reproduce and file this issue.
There’s no major update here-- Our plan is, as it has long been, to unite LookML and User Defined Dashboards into one dashboard type.
(I’ve never seen the movie actually, but the pic seemed appropriate)
The project to do that is in the very early planning stages though, so nothing is guaranteed and there’s not much more information to share right now.
There’s also no major update to share on the bug that
@Luke_Parsons submitted-- It’s been prioritized, assigned, and we are planning to complete work on it in May/June.
Is there a timeline for release of phase 2?
Thanks! Are these the same API endpoints I see in now API version 3.1 experimental?
Has anyone built a Python library to make it easier to generate and manage LookML dashboards more scalably?
Some of the pain points we’re trying to solve for:
We’ve recently been testing the sync_lookml_dashboard API endpoint to keep LookML dashboards updated. However it’s been unusable due to the dashboard layout not being synced correctly from the LookML dashboard to UD dashboard.
We require UD dashboards for their discoverability and usage analytics (which LookML dashboards lack). Has anyone else experienced this issue? At the moment it’s a blocker for us continuing to develop LookML dashboards.
Thanks Izzy, I’ve submitted a ticket.
A support engineer and I replicated the bug on our Looker instance, but it couldn’t be replicated outside of our instance. Therefore I think this won’t get any attention unless other people have the same issue. A bug report was filed with the code EMBED-725.
My favourite topic.
Any updates around this?