Register now to learn Fabric in free live sessions led by the best Microsoft experts. From Apr 16 to May 9, in English and Spanish.
I have a pbix file that successfully loaded data and everything worked. The next day I tried refreshing it, and got this peculiar error:
Column ‘MAMUserPercent’ in Table ‘CapacityReport_ASUDeviceRatios’ contains a duplicate value ‘0.5’ 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.
I could not find any reason for the error, either in the table itself or in any references to the table. Since I was out of ideas, I duplicated the table, changed all references to the new copy, and deleted the old one, and the refresh then failed with a similar error but on a different table:
Column ‘Total Device Check-ins Per Day’ in Table ‘CapacityReport_MonthlyCapacity’ contains blank values 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.
I repeated the process and the next refresh succeeded. I'm worried that I will continue to hit this randomly when i refresh. Any ideas on what's going on?
Solved! Go to Solution.
Thanks. I took a look at Manage Relationships and discovered that for some reason it had created a couple of very strange relationships automatically for some reason. Those relationships were based on a seemingly random property between two tables that were related but based on completely different properties. No idea why those were created, but I disabled them and hopefully that will keep the problem from recurring.
I faced the exact same issue. And when I clicked "Manage Relationships" on the Home tab, I found that automatically two tables were joined, and it made no sense to join them both. Once I deleted the relationship, and published the changes, I was able to refresh the tables data!
Super, it really worked for me. I had the same issue and i was struggling to get resolved this issue.
I had no idea what was the wrong in my table and all.
thanks for this!
take a look at relationships; you may find join lines that shouldn't exist; this can occur in my experience if one is adding tables/columns and there is an identical column name - sometimes it seems a join line is made automatically....
the error messages definitely indicate inappropriate join lines; the only join line should be between fundamental key fields
Covering the world! 9:00-10:30 AM Sydney, 4:00-5:30 PM CET (Paris/Berlin), 7:00-8:30 PM Mexico City
Check out the April 2024 Power BI update to learn about new features.
User | Count |
---|---|
115 | |
100 | |
88 | |
68 | |
61 |
User | Count |
---|---|
150 | |
120 | |
100 | |
87 | |
68 |