How to keep the dashboard and Looks ID same across multiple looker instace

[tuddin]

Hi,

We have two looker instances. We have dashboards from where we drill out to another dashboard or looks. The problem is the dashboards and looks are referenced by number (e.g. looker_dev.com/looks/9 and looker_dev.com/dashboards-next/7 etc). When we migrate to prod, the number changes. So the custom drilling will break. 

Is there any way to reference the looks or dashboards by name/path? or a way to keep the ID same across instances? 

Please share your suggestions.

Regards,

Tanveer.

[margaret_abercr]

Hi Tanveer! 

The best way to have static dashboard references is to use LookML dashboards. Since the LookML dashboard is referenced by `model::dashboard` that will not change moving from one instance to the next.

There currently isn’t a way to have “LookML Looks,” but you can have single tile LookML dashboards to serve the same purpose. 

Definitely share your feedback with the product team using this process!

[tuddin]

Thanks Margaret. yes the only problem is with the Looks. but maybe lightweight dashboards is the way to go.

[margaret_abercr]

And do submit the idea to our product team! 

[Michael_Jassows]

The problem with "Lightweight" (i.e. single tile) dashboards is that they are not handled the same way in the API.  For example: a run_look will return the data in a json structure, however there isn't the same capability for a dashboard in the API.

Ideally, Looker would allow a vanity look id to be defined.  This would have several nice effects:

1. You could have the same vanity id used in each Looker environment, eliminating the need to add clumsy case statements into apps and liquid into links to detect which environment the code is in and setting the look value appropriately.
2. api calls could be created which would make it clear what the API is returning.  Instead of:

response = sdk.run_look(
look_id="31963",
result_format="json")

You'd be able to have:

response = sdk.run_look(
look_id="LastQuarterSalesByUser",
result_format="json")

Look_id is even already a string!