Renaming dataset measures can't break client reports (change reference from name to ID)

[ja32575]

When splitting my Power BI into a dataset with N thin reports (dataset clients), and I change a column or measure name, all N reports will break because they reference dataset's column/measure by name. The Measures I build *should have unique IDs* - so if I change the name, as long as the original measure is the one used, it should just *updated on the reports themselves*. For now, the only "solution" available is to open all N reports one by one and *rebuild them manually*. Very painful! More dangerous and tricky is opening pbix like @parra described here: Modifying the Layout file that is embedded in a pbix file https://community.powerbi.com/t5/Desktop/Modifying-the-Layout-file-that-is-embedded-in-a-pbix-file/m-p/1616614/highlight/true#M652387 More details about this problem were exposed by @TO_CB and discussed on this community forum post https://community.powerbi.com/t5/Desktop/Modifying-Layout-file-inside-pbix/m-p/2095628

[Adam_Grisdale]

100% agree. Dataflow entities are also referred to by name, and not a unique ID, and therefore also break when re-named.

[samnseir]

Or at the very least, allow us the option to replace missing/broken fields in visuals and filters.

If this can be done globally for a report then that would be really helpful. Something like a "fix broken/missing fields/measures" type wizard/form.

[fbcideas_migusr]

This seems to be handled by ID (and therefore gracefully) in a report that is in pbix Import mode. So why not thin reports? A single table name change can break dozens of visuals in each of hundreds of reports so there is an extreme penalty for such a change. No third party software can break/fix, as far as I've been able to see. If PBI is a DIY tool, then these types of changes should be seamless.

I wonder if the lack of votes indicates a lack of DIYers in the forum? Developers might not appreciate the pain and thus the value of a solution. How can we elevate/escalate???

[huangj]

Total agree. ID-oriented logic should apply to table name, column name change as well...

The current situation is once we change the name of a table or column or measure, it breaks reports everywhere... Not only it's hard to fix them manually, but also hard to manage and plan.