u/sheik_sha_ha — reddlx

Looker Studio is being renamed back to Data Studio.

So Google just announced that Looker Studio is reverting to its original name, Data Studio.

Not just a rename though. They are positioning it as a central hub for Google Data Cloud assets, meaning you can browse BigQuery conversational agents, Colab data apps, and reports all in one place.

The free tier stays free. Data Studio Pro still exists for teams that need enterprise features.

Honestly the rename makes sense. Looker Studio always felt like an awkward name after the acquisition. Data Studio was familiar, simple and people already knew what it meant.

What I am watching closely is whether this "single place for data assets" vision actually delivers or just becomes another Google product that sounds great in a blog post and ships half-finished.

The existing reports, data sources and assets are supposed to carry over automatically which is good. Last thing anyone wants is to rebuild dashboards because Google decided to reorganize its product lineup again.

For anyone using this daily for client reporting, the core functionality looks unchanged for now.

Has anyone seen anything beyond this announcement? Curious if there are actual UI changes or if this is mostly a branding and positioning update at this stage.

Now I think I need to rebrand myself as a Data Studio User 😅

https://cloud.google.com/blog/products/data-analytics/looker-studio-is-data-studio

Has anyone else run into this in Looker Studio?

I was building a calculated field today and got the "Invalid Formula" error.

Formula looked fine to me. Syntax was correct. Logic was solid.

But the editor was flagging it as invalid so I assumed something was broken.

Then I just clicked Apply anyway.

It worked perfectly. Calculated Fields pulled the right data, dashboard updated exactly as expected.

So the formula was never actually broken.

The #LookerStudio formula validator just told me it was.

This is a real problem because most people see that red error and stop. They second guess their formula, rewrite it, go down a rabbit hole trying to fix something that was never wrong.

I have seen this happen on CASE statements, date functions and regex formulas.

The error message is misleading. The formula validator does not always catch up with what the engine can actually process.

If you are working in Looker Studio and see "Invalid Formula" on something that looks correct, try clicking Apply before assuming it is broken.

It might just work.

Has anyone else run into this? Would be good to know if this is consistent across different Google Cloud accounts or just isolated cases.

*I faced this same issue two years back.