Format of measures is lost when model is edited in the service

[mriedmuell]

I created a report based on a semantic model belonging to a fabric warehouse.

I published the report in the same workspace and opened it in the browser.
I wanted to make changes and opened the data model in the browser.
The storage mode was automatically converted for large models, without any question or possibility to stop that.
After editing a measure, I noticed that the formats of all my measures was deleted, rendering percentages as decimal number and without the thousands separator e.g.
This is quite an unexpected behaviour and I consider this a bug.

After some time spent searching for a variant to submit a bug report, I resorted to this forum.
If this is not the rigth place, please improved the discoverability of the correct way to report bugs.

[v-pagayam-msft · Accepted solution]

Hi @mriedmuell ,
Thank you @andrewsommer  and @Akash_Varuna  for the prompt reponse.
 As the provided solutions doesn't solve your problem.I reccomend you to raise a Microsoft support ticket, this will allow a dedicated team to investigate and provide a resolution.

To raise a support ticket for Fabric and Power BI, kindly follow the steps outlined in the following guide:

How to create a Fabric and Power BI Support ticket - Power BI | Microsoft Learn

If this post helps, please give us Kudos and consider marking it Accept as solution to assist other members in finding it more easily.
Thank you for being a part of Microsoft Fabric Community Forum!

[andrewsommer]

The model edit feature in the service has greatly improved over the past year, but it still has some needed improvements before it is on par with desktop.  On our teams we still recommend editing semantic models in desktop and republishing. 

[Akash_Varuna]

Hi @mriedmuell Editing a data model in Power BI Service can reset measure formatting (percentages or separators) if storage mode changes for large models. To avoid this, make edits in Power BI Desktop and republish , this issue might be a potential bug and it would be good to provide feedback to Microsoft 

[mriedmuell]

Hi @Akash_Varuna and @andrewsommer , thank you for your comments.
As this effect results in a loss of information and as it is performed automatically, this schould be considered a bug.
Thus I will not mark any of the responses as solution, as it doesn't solve my problem.