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 moreDid you hear? There's a new SQL AI Developer certification (DP-800). Start preparing now and be one of the first to get certified. Register now
I started working with version control and encountered the following error while loading a report from a historical commit.
"There's a problem with the definition content in your Power BI Project.
Column ‘X’ in Table ‘TableX’ contains a duplicate value ‘’ and this is not allowed for columns on the one side of a many-to-one relationship or for columns that are used as the primary key of a table.
The current operation was canceled because another operation in the transaction failed"
Using version control doesn’t make sense with errors like this. The historical commit contained a different table layout that joined to the fact table via a different column, which made sense and worked in the previous version. In the latest commit, I made changes—the table was restructured in Power Query, and the join is now performed via a different column. The model has been changed. After closing the report and setting the checkout to the historical commit, the report does not open and returns an error, as it was unable to recreate the model and connections saved in the historical commit.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.