Find and replace in legacy dashboards

Feature Suggestions
1

Hello!

One of the features that we used a lot in looker is their find and replace as part of content validator:

I had thought holistics has similar functionality as part of the report validator but now I think I was misreading the documentation which says:

  • Find and replace names of fields, models, or datasets: If you want to change the naming convention of your fields, models, or datasets, Reporting Validation can help you locate all instances where they are referenced and replace them with the new names.

It seems like this just helps you locate the errors, but they still need to be manually changed. Is this accurate, or did I miss how to do this? Manually updating each spot is not feasible when we have hundreds of dashboards (which we soon will). It would be AMAZING if this could work on either a branch or on production.

We are using canvas dashboards (which makes find and replace a breeze) but all our non-technical users will be using the legacy dashboards since git has a steep learning curve.

Thanks so much in advance,
Anya

P.S. It looks like the “learn more” link is broken in the reporting validation popup that says “Reporting Validation detects and validates broken items in Reporting page caused by changes in Modeling page. Learn more”

2

Thank you for raising this request, @anya.conti!

Indeed that our Reporting Validation only helps locate the errors at the moment. That being said, this is an area that we want to improve in the upcoming time.

May I summarize your request, to make sure that I understand and address it completely:

1/ With canvas dashboards

  • Right now, the Reporting Validation feature has helped locate the errors, so you can resolve them one by one
  • However, it would be more ideal to have (a) a list of errors by groups for overview, and (b) the capability to resolve errors in bulks (similar to the Looker reference above)?

2/ With legacy dashboards

  • You’d like to know how your non-technical users can resolve these errors (i.e. remap their legacy dashboards to other datasets), yes?

Please let me know if I missed anything.

Also, I really appreciate you identifying the wrong link to our document, Anya! Our team will fix it right away :pray:

Cheers!