Dashboard after explore file moved

low_priority
done
reply
#1

If I moved an explore file under project A to project B, can I still keep all the dashboards and looks developed from that explore file working? It seems like I have to recreate everything again. Any suggestions?

0 Likes

(Morgan Imel) #2

Hi @jzyu,

A query is defined by the model and explore that it’s in, not the project. So if the explore and model names are the same, and the model configuration is the same, then you should be good to go! Let me know if that’s not the case for you.

0 Likes

#3

Sorry, actually I said it wrong. I moved an explore to a different model within the same project, so when I open the original dashboard, I got error “Could not find the model or view requested.” Do you know what I can do in this case?

0 Likes

(Morgan Imel) #4

Hey @jzyu,

In this case I recommend using the content validator. The content validator will find the broken looks and you can do a find and replace for the new model name. Let me know if you run into trouble!

Morgan

0 Likes

(Fabiana Tamburrini) #5

I have a similar situation to jzyu. I have used the content validator and it was great to fix the error on individual looks. But the dashboards using those looks are still broken, as the dashboard is still referencing to the old explore name. Also I have a other dashboard that have not looks on it, only tiles, and the errors on that dashboard was not found by the content validator. It looks like it only detect and affect looks.

0 Likes

(Brecht Vermeire) #6

Thanks for letting us know @Fabiana_Tamburrini - I’ve passed this on to our product folks. If you’re renaming the explore for UI reasons, you might want to use label instead.

0 Likes

(Sebastiaan) #7

I am facing the same issue.

Since the Content Validator update (>5.10) lookless tiles can be referred to new model names.

However for me, the dashboard is still referencing to the old model name:

  • In Content Validator, changed the Model reference from old to new model name
  • Tile works individually
  • However on dashboard, tiles display ‘View Not Found’
  • Explore From Here generates URL with old explore name:
    ...looker.com/explore/ [old model] / [label]
  • Changing URL will work:
    ...looker.com/explore/ [new model] / [label]
  • Therefore I think the Content Validator does not update dashboard references

I don’t know an easy way to do this now. For LookML dashboards I can change it there, however these are the dashboards created from the UI in Spaces…

0 Likes

(sami.rubenfeld) #8

Hi Sebastiaan,

Do these tiles in question happen to include Merged Results?

Best,
Sami

0 Likes

(Sebastiaan) #9

Hey Sami we are not using Merge Results… (Content Validator we do).

Only thing I have to check is it might be because I am checking in development mode. You can imagine Im a bit cautious at this stage. I know changes to dashboards take effect in production, so might be something there.

0 Likes

(Jeff Miller) #10

Ya… content validator doesn’t update the Dashboard Filtering. We are attempting to use the SDK to do an update_dashboard using Python to do this. But update_dashboard doesn’t seem to actually update the model names of the filters for some reason. We have entered a case with Looker on it.

0 Likes

(Thomas Brambor) #11

Has this been resolved? I am facing the exact issue after removing an older dashboard and creating a similar one in its place. I would like the old dashboard links (i.e. as a linked dashboard) be replaced by the new version. The content validator does not find the issue.

0 Likes

(Izzy) #12

Thomas, what do you mean by dashboard links? Are these fields you’ve defined that link out to a specific dashboard that’s not around anymore?

If so, I think that’d be out of the scope of the Content validator, since that’s usually done with manually defined URL’s in the html or link parameter. If you’d like, you could open up a feature request for that in the feature requests category.

If not, let me know what you mean!

0 Likes