Looker Randomly Deleting Calculated Fields

Looker Q&A Looker Studio
, , ,
1

There seem to be a number of serious bugs with calculated fields. I think most people are familiar with the issue of creating a calculated field and then it’s not actually created, or only being able to create one calculated field at a time. This issue is probably caused by lag; Looker can’t sync with the changes fast enough and reverts to its most recent version. Sure I can understand that in the free version, but feels unacceptable when you’re paying for the pro version. Raise prices if you have to. I just want a reliable product.

The bigger issue with calculated fields is when they are randomly deleted out of the blue. I created some calculated fields a few weeks ago and this morning, a few of them were deleted. The others were similar calculations and were fine. Not sure why those alone disappeared. It’s really annoying when this happens and all your visualizations break.

Looker team, this is embarrassing. Having calculated fields feels like one of the absolute most basic functions of your product. Please get it working.

1 Like
2

I am not allowed to write a new post, but calculated fields just stopped working. No data showing. Whiles it was working for a many years.

1 Like
3

Hey,

Hope you’re keeping well.

Calculated fields in Looker Studio are stored at the report level, so unexpected deletions usually point to either a sync conflict with the underlying data source or overwrites from concurrent edits. If you’re working in a shared report, changes from other collaborators can overwrite fields without an explicit delete action. To reduce risk, try duplicating the report as a backup before making large edits, and ensure all calculated fields are saved by clicking Apply and reloading the report to confirm persistence. If the issue persists, capture the report ID and timestamps when fields disappear and file a ticket via Cloud Support, as this will help the Looker team trace backend sync logs.

Thanks and regards,
Taz