LinkedIn
Twitter
In the past week and a half I've seen charts built on data blends consistently failing. Prior to this time period these charts were working without any issue, but I have IDd some common factors that could be part of this bug which is that the charts are built on data blends.
I'm noticing that the chart will work fine, then if you close the dashboard and re-open or reload it, the chart will break with a generic error message:
"System Error
Looker Studio has encountered a system error.
Sorry, we encountered an error and were unable to complete your request."
The underlying data source is from BigQuery and is a very small data source before we even filter it in the custom query. The data blends are simple ones (3-4 dimensions + 1 measure in each table) primarily used to create a % to total.
When we open a dashboard and the charts include this error message, rebuilding the chart in exactly the same way fixes the issue temporarily, showing to me that the issue is not the underlying data or how the chart is built, but once the dashboard is closed and reopened we get this same error message.
One of our charts (the bottom chart in my example image) is a pivot table that uses a calculated field at the chart level, since you can't created calculated fields in data blends. I've noticed that even after adding in the calculated field, it won't save the name, format (e.g. percent), or decimal precision. Sometimes it won't save those formatting items AND the formula. I've also noticed that the measures I use to sort the rows and columns keep defaulting to the calculated field, even when I explicitly set them to another measure from the blend.
Another pivot table built on a blend will look blank (not that the chart doesn't load, it loads but dimensions/measures are blank) but if you export the chart to CSV all of the data is there, another indicator that the issue isn't the underlying data or way the chart was built.
These dashboards were built several weeks ago and had no issues until mid last-week. I first assumed it was an issue on our end but after rebuilding several dashboards entirely from scratch (to prevent any previous edits or old data sources from causing issues) I'm continuing to see this behavior.
