Forum Discussion
New column in entity
Hi All,
I understand that when adding new column, the schema is considered to be changed. So, the refresh won't take effect on downstream dataflow which refer to the schema updated dataflow.
In dealing with the changing need of end-user, you probably has to add column into the entity to pull out enough information for reporting purpose, then how would you solve the issue?
Kindly suggest!
Thanks and best regards.
Rich
When data structures change, you need to update your dataflows and Power BI datasets. Even if the column did flow through and show up, the report has to be changed to reflect whatever data you want. So unless you are unpivoting columns (like where dates are in columns and not as a row value) new columns have to be properly accounted for. I would hope that is a rare occurance in a mature report.
If it is a frequent occurance, I would look at doing some manual M code that will dynamically handle this kind of thing.
2 Replies
When data structures change, you need to update your dataflows and Power BI datasets. Even if the column did flow through and show up, the report has to be changed to reflect whatever data you want. So unless you are unpivoting columns (like where dates are in columns and not as a row value) new columns have to be properly accounted for. I would hope that is a rare occurance in a mature report.
If it is a frequent occurance, I would look at doing some manual M code that will dynamically handle this kind of thing.Hi rdnguyen ,
As edhans said, when the data structure changes, the data flow and the Power BI dataset need to be updated. Also if you are targeting data that is constantly updated, I think you can use incremental refreshes.
If the problem has been solved you can mark the reply for the standard answer to help the other members find it more quickly. If not, please point it out.
Looking forward to your feedback.
Best Regards,
Henry
