This time we’re going bigger than ever. Fabric, Power BI, SQL, AI and more. We're covering it all. You won't want to miss it.
Learn moreLevel up your Power BI skills this month - build one visual each week and tell better stories with data! Get started
Hi,
When working with shared datasets, we are planning to rename a few columns and tables for the sake of readability. However some reports have already been build and put into a production environment.
Running a few tests, it seems that renaming columns and table names in the power BI shared dataset makes sure that the visuals break in the reports that are connected to that dataset. This is really inconvenient when you need to rebuild several reports. Am I doing something wrong or is this standard behaviour?
Thank you in advance,
Hendrik
Solved! Go to Solution.
Hi, @HSpeelman
Yes, it is standard behaviour. Some visuals may be broken when you rename some table names and field names.
You have to rebuild the report manually, although this is really inconvenient.
Best Regards,
Community Support Team _ Eason
Hi, @HSpeelman
Yes, it is standard behaviour. Some visuals may be broken when you rename some table names and field names.
You have to rebuild the report manually, although this is really inconvenient.
Best Regards,
Community Support Team _ Eason
Thank you for your response!
Really a pity that this is standard behavior... I would have expected more from Power BI, as Microsoft claims it's a best practise to split dataset and report in a self-service environment.
Check out the April 2026 Power BI update to learn about new features.
Sign up to receive a private message when registration opens and key events begin.
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
| User | Count |
|---|---|
| 12 | |
| 11 | |
| 8 | |
| 7 | |
| 7 |
| User | Count |
|---|---|
| 38 | |
| 27 | |
| 25 | |
| 22 | |
| 22 |