Forum Discussion
Post ProdigyExternal Data Properties
Did you try connecting the Excel table back to powerbi the way I described? This approach works fine within Excel itself.
The main concern with connecting Excel back to PBI is that you would need to immediately refresh the Excell anytime you refreshed the PowerBI. I understand this may not match your work-flow....
I agree that manually copying is error prone and confusing.
Post ProdigyHello PwerQueryKees
The new column is added in the Excel table itself. When the data refreshes, the column doesn't change, and stays in place, meaning if there's a new row in between or if the data lines switches rows, the Comment do not switch with them.
Connecting Power BI to the Excel file in point #3 would not fix it, as the Excel_Table changes with the PBI_Table. For example, if a comment was entered for Line 3, it will show up for Line 3 at first, but if Line 2 is removed, Line 3 will now be the new Line 2, but the comment stays at Line 3, when it should move to Line 2.
The only workaround I can think of right now is to copy the table in Excel (that originates from PBI dataset), and paste it in a new sheet, meaning it is not linked to any sources and is static, and the new sheet will be merged to the PBI dataset. And whenever an update to the comments is needed, user will refresh the Excel file that originates from PBI dataset, copy the table in Excel again, and overwrite the new sheet.
Although this completes the loop of getting data from PBI to Excel, and pushing it back to PBI, it might be rather confusing for the user.
Super UserDid you try connecting the Excel table back to powerbi the way I described? This approach works fine within Excel itself.
The main concern with connecting Excel back to PBI is that you would need to immediately refresh the Excell anytime you refreshed the PowerBI. I understand this may not match your work-flow....
I agree that manually copying is error prone and confusing.