Hi everyone,
I’m noticing a pretty bad regression in Looker Studio that’s essentially breaking the entire workflow for anyone who needs to scale dashboards.
The issue happens when duplicating a report and trying to swap the data source for another instance of the same connector. Instead of a smooth transition, I’m getting the “We’ve updated your report to fix some errors” pop-up. This “update” is actually a disaster: it systematically disconnects metrics and completely corrupts the dashboard configuration.
I’ve noticed this happening especially with partner connectors, but it seems to be a broader issue with how Looker is handling schema mapping during file duplication lately. I even ran some isolation tests on a completely blank report with a single chart to rule out complexity, and the result was the same: the data integrity was lost. It’s like Looker is failing to recognize identical field IDs during the transition, treating them as incompatible and forcing a “fix” that just destroys the report’s logic.
Is anyone else dealing with this recently? If you have a moment, could you try to reproduce this on your machine (specifically copying a report and swapping the source)? I’m trying to figure out if this is a widespread platform bug or something more specific. It’s making it impossible to deploy dashboards for new clients right now.