Change theme
Help
Press space for more information.
Show links for this issue (Shortcut: i, l)
Copy issue ID
Previous Issue (Shortcut: k)
Next Issue (Shortcut: j)
Sign in to use full features.
Vote: I am impacted
Notification menu
Refresh (Shortcut: Shift+r)
Go home (Shortcut: u)
Pending code changes (auto-populated)
View issue level access limits(Press Alt + Right arrow for more information)
Request for new functionality
View staffing
Description
What you would like to accomplish:
We've made significant changes to the fields and organizational labels of a critical Explore in Looker, and for some reason, these changes weren't pull through to Looker Studio, so we tried re-adding the data source versus refreshing it. Now we have new and old versions of the same Explore creating confusion when trying to troubleshoot specific dashboard tiles.
How this might work:
When we add the same data source, we may have the option to add that source as another entity, or have the option to overwrite the existing source reflecting the structure/content as in the Looker platform source.
If applicable, reasons why alternative solutions are not sufficient:
I struggle to see how anyone would benefit from Looker Studio using outdated versions of the Explore that are not even in production anymore.
Other information (workarounds you have tried, documentation consulted, etc):
The REFRESH FIELDS button in Looker Studio didn't display the new fields. As a workaround, we used the ADD A DATA SOURCE feature.