Looker Connect Training
Help Center
Documentation
Community
Cloud Certifications
Yes, depending on how your lookml is modeled. Our solution is: Store one copy of this as a lookml dashboard, we save these template dashboards as “common.dashboard_name”. If you’re using the GUI to generate your dashboard LookML, remove the “model” parameter from each of your individual elements. We also have all of our communal views named in the same format, so the dimensions and measures you hope to access across all connections are in "common.view_name" We have a model.base.lkml file that we created which contains all of the necessary explore definitons, we do not include connection name here. You would then have a different model for each of your connections e.g. we have a customer1, customer2 model, In each of these model files we have at the top: connection: "customer_connection_name" include: "model.base.lkml" include: "common.*.dashboard" include: "common.*.view" This will then create a separate dashboard for each of your connections from this dashboard template file. This us
I see the use in this also, particular for a support/monitoring instance we’re planning to set up. Would be good to be able to easily flit between the 25 connections we have for each of our customers. @ima.adesi if your dashboard is a LookML dashboard, you can use something along these lines to maintain one dashboard definition, that generates a different dashboard based on the different models/connections you have set up. It doesn’t solve the problem, but makes maintenance much easier when you need to update anything on the dashboard: Extending Model to Include Sensitive Information Modeling For security purposes, I’d like to limit access to the email address field to only those users who need it for their day-to-day work. I’d like them to have the exact same models/explores/views as everyone else, but with the email address field unhidden. There does not seem to be a straightforward way to do this. My first thought was to create a new model, include the
Thanks so much brettg!
It took me awhile to find this thread, but it theoretically could solve a huge issue we’ve had for the last year whereby we need to change a generically named connection any time we wanted to use a different database as the source for our dashboards. It is a terrible setup when you have multiple developers developing on one instance who need different data sources simultaneously. It also causes a lot of issues with PDTs when we change this connection as frequently as we need to. It would definitely help our use case a lot if this was something that was integrated into the UI, as even you guys attest that editing lookml files outside the UI is not recommended.
Hi abbywest, A few questions - You’ll no longer have to use the Import to Space functionality (which breaks the association with its LookML) to expose LookML dashboards in Spaces Will this association with a Space be done in the LookML definition of a dashboard? Or will there be some other UI action to be performed? We roll out our LookML dashboards to 30+ instances and it would be great if this was all source controlled too. The ability to expose LookML Dashboards in Favorites & Top Content Will this also allow usage monitoring of these dashboards via i__looker? I’ve raised this feature request: https://discourse.looker.com/t/usage-monitoring-for-lookml-dashboards/4787 as it’s a very big issue for us.
+1 Also a huge issue for us
Thans @Morgan I did actually get this working with help from one of your colleagues - unfortunately the fact that it has to be a measure didn’t work at all with our use case. It meant that the field which we normally kept on the left hand side of a large (20 column) table report had to go to the end - due to Looker’s measure/dimension grouping. And it also couldn’t be used with our pivoted reports - as it tried to also pivot the linked measure. Is there any plan to update this so that it can be used on dimensions?
There’s a typo in this example. should be: Old LookML - dimension: took_test sql_case: 'Yes': ${TABLE}.boolean_field = 'true' 'No': ${TABLE}.boolean_field = 'false' 'Null': ${TABLE}.boolean_field = NULL New LookML ``` dimension: took_test { case: { when: { sql: ${TABLE}.boolean_field = 'true' ;; label: "Yes" } when: { sql: ${TABLE}.boolean_field = 'false' ;; label: "No" } when: { sql: ${TABLE}.boolean_field = NULL ;; label: "Null" } } } </details>
Already have an account? Login
No account yet? Create an account
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
