Edit Data Model in Power BI Service (Preview) – My First Experience

[shashiPaul1570_]

Hi Fabric & Power BI Enthusiasts,

Yesterday, while working on a semantic model, I ran into an issue with relationships. Normally, this would mean going back to Power BI Desktop, fixing the model, and republishing — a process that always felt time-consuming.

But this time, I noticed the new Edit Data Model in Power BI Service (Preview) feature. To my surprise, I was able to create the relationships directly in the Service, without switching back to Desktop. It saved me both time and effort, and the workflow felt seamless.

This feature not only supports relationship management, but also offers better error handling in Power Query and native query support, making modeling smoother and more collaborative.

For me, this was a small but powerful productivity win — and a glimpse into the future of cloud-first Power BI modeling.
For more details, this follow the documentation released on July 26, 2025. 

https://learn.microsoft.com/en-us/power-bi/transform-model/service-edit-data-models?utm 

Best Regards

Shashi Paul 

[v-saisrao-msft]

Hi @shashiPaul1570_,

It's great to hear about your experience with the new Edit Data Model in Power BI Service (Preview). Being able to adjust relationships directly in the Service helps avoid the need to republish from Desktop. Please note that changes are autosaved without an undo option, Power Query editing is limited to import tables, and certain models, such as those with incremental refresh or pipelines, are not yet supported. This is a positive development for cloud-based modeling.

Thank you.

[shashiPaul1570_]

Hi @v-saisrao-msft ,
Thanks for the clarification 🙌 — very insightful!

The best part is that with Semantic Model Version History (Preview), we have a safety net. Even though edits are autosaved without undo, we can always restore earlier versions if needed — that really gives confidence while modeling in the Service. Excited to see how this evolves!

Best Regards
Shashi Paul

 

[v-saisrao-msft · Accepted solution]

Hi @shashiPaul1570_,

Version history serves as an effective safety net, making autosave edits in the Service more dependable and helping users feel more confident when modeling.

Thank you.