Hi Vu,
Thanks for the response! Here’s a modified version of what you sent, with a few things clarified:
- With Canvas Dashboards
- Does reporting validation work on canvas dashboards? I thought reporting validation only worked for legacy dashboards, and canvas dashboard validation would fall under AML validation based on this other thread I was having with holistics? This specific request for find and replace was entirely for legacy dashboards, apologies if the mention of canvas dashboard made that unclear! I was just trying to explain why we can’t fully switch over to canvas dashboards. We can already do find and replaces in code for canvas dashboards fairly easily so I’m not concerned about that.
- With Legacy Dashboards
- Non-technical users will continue to use legacy dashboards, though they won’t need to do the find and replace. Doing find and replace will be done by technical users who are making the code changes that would otherwise break the dashboards
- Right now, the Reporting Validation feature has helped locate the errors, so you can resolve them one by one, but this is unrealistic if we have hundreds of dashboards (which we currently do in looker and are in the process of migrating over)
- Even with reporting validation, once something is broken, it’s sometimes hard to tell exactly how it was set up before (ex. broken filters won’t let you see the values they were filtering on, I’m not sure how easily I could check formatting of a broken field, etc) which a find and replace should help with
- To help with both of the above bullets, 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)
All the best,
Anya