Forum Discussion
Changes to Dataset cause error in Live Connect
Hey yamayancha ,
I can't speak for the Microsoft developer mindset but I see both sides of this issue. For example, if I have "renamed" a field in the visual (and just in the visual) I may want that to be the display name no matter what the real field name is. But, if the real field name is changed, I might actually want to use the new field name and not my version of it and this gives me a chance to double check that. Or, I may have my own terminology and don't care what the field
Of course, the other side of the coin is as you state - if I change it in the dataset I want to flow through to everybody that way.
I guess part of it comes down to the business philosophy - is the dataset the "official" terminology?
All that said - it might be good for you to create an idea (or find one) for this issue.
Hi collinq,
thank you for your reply. I understand now that this is how it was intended but what I fail to understand is, why it was intended to work this way. Would it not be much more user-friendly if any visuals or measures would also auto-update when the connected dataset changes? If you have multiple reports connected to the same dataset and some measure is renamed in the original dataset, now you have to go through every single report to change the visualizations that use this measure.
To me, this kind of defeats the purpose of connecting to a dataset as I now have to notify every single report author who uses my dataset for their reports and they have to update their reports before any viewer opens them and only sees error messages. I had hoped this was a bug that was going to be fixed as this revelation will definitely not help to raise my colleague's enthusiasm when working with Power BI.
Hey yamayancha ,
I can't speak for the Microsoft developer mindset but I see both sides of this issue. For example, if I have "renamed" a field in the visual (and just in the visual) I may want that to be the display name no matter what the real field name is. But, if the real field name is changed, I might actually want to use the new field name and not my version of it and this gives me a chance to double check that. Or, I may have my own terminology and don't care what the field
Of course, the other side of the coin is as you state - if I change it in the dataset I want to flow through to everybody that way.
I guess part of it comes down to the business philosophy - is the dataset the "official" terminology?
All that said - it might be good for you to create an idea (or find one) for this issue.