We currently embed looks and dashboards in iframes in our application, but the method for looks is limited compared to LookML dashboards, and it causes us a few problems.
For example, I set up the app config in our UAT environment and make sure everything (including Looker) is set up just right. Then, I deploy to Production when we are happy with everything. High-fives all around … except, WAIT! The link to embed the dashboard is the same in both environments
/embed/dashboards/model::dashboard, but for the Looks we have something like
/embed/looks/123. Because UAT and Prod are on different servers, the Look # for UAT and the Prod have different numbers. I now need to release a change against Prod to update our config.
If you could “name” the look something, it would mean this wasn’t a problem. Anyone else have this issue?
If so, does anyone have a way around it, or does anyeone know of a way to interrogate the Looker database to get the Look # based on the space & name it’s been saved with?
This is a perfect opportunity to use i_looker!
Here’s some information about using i__looker’s history explore.
You can do a query on Look ID, Look Title and Space Name to get the data you are looking for.
thanks! I wasn’t aware of i_looker and it looks like it could be useful, although I don’t think it helps me with my case (please correct me if I’m understood!).
This will help me find the correct Look ID, and I can query on the title etc of the look, but we have a table in our app’s database that has the embed link in, e.g.
/embed/looks/123, and what I’m really looking to do is have something like
/embed/looks/look_titleas the link, but I don’t think that’s possible
Anyway, thanks again for the info on i_looker! 🙂
You’re right, /embed/looks/look_title as the embed link won’t be possible, because Looks don’t have to have unique names. You could, however, use i__looker to get a list of all Look IDs to populate the table!