Forum Discussion
The 'HasUniqueRoleAssignments' column does not exist in the rowset.
Nothing back from microsoft, but... i a pretty crappy solution, but i was able to make it work.
In order to avoid referencing the columns that are magically put into the report, use the "Remove Other Columns" feature in the Query Editor. If you select the ABSOLUTE minimum number of columns you are using for your report across ALL data sets synced, (ctrl + shift + click) to select only the columns you are using... and then right click and select remove other columns the steps reference only the used columns.
Thus you get something like this:
#"Removed Other Columns" = Table.SelectColumns(#"Renamed Columns1",{"Column 1", "Column 2", "Column 3", "Column 3")
instead of:
#"Removed Columns" = Table.RemoveColumns(#"Removed Other Columns",{"ERROR CAUSING COLUMN 1". "ERROR CAUSING COLUMN 2". "ERROR CAUSING COLUMN 3". "ERROR CAUSING COLUMN 4". })
Once you remove them with this method, the Web application does not know that the bad columns exsist and completes a full refresh.
It's complete bull**bleep** and i have multiple reports with 5-10 data sources with 30+ columns each.... but it works. And this is a total work stopper for my org.
Let me know if this works for you or not
mzikraJust tried uploading the report through the "Get Data" options. I still receive the same error when trying to refresh. Do you know if Microsoft has offered any documentation that this is a Known Issue?
I've been unable to reach them over the weekend on this ticket. As of now, i have not seen any official notification that it is a known issue, however there is a patch being released on 5/15 (US). I am curious to see if this will fix this issue.
I should be hearing more on Monday for sure
Nothing back from microsoft, but... i a pretty crappy solution, but i was able to make it work.
In order to avoid referencing the columns that are magically put into the report, use the "Remove Other Columns" feature in the Query Editor. If you select the ABSOLUTE minimum number of columns you are using for your report across ALL data sets synced, (ctrl + shift + click) to select only the columns you are using... and then right click and select remove other columns the steps reference only the used columns.
Thus you get something like this:
#"Removed Other Columns" = Table.SelectColumns(#"Renamed Columns1",{"Column 1", "Column 2", "Column 3", "Column 3")
instead of:
#"Removed Columns" = Table.RemoveColumns(#"Removed Other Columns",{"ERROR CAUSING COLUMN 1". "ERROR CAUSING COLUMN 2". "ERROR CAUSING COLUMN 3". "ERROR CAUSING COLUMN 4". })
Once you remove them with this method, the Web application does not know that the bad columns exsist and completes a full refresh.
It's complete bull**bleep** and i have multiple reports with 5-10 data sources with 30+ columns each.... but it works. And this is a total work stopper for my org.
Let me know if this works for you or not
This worked for me!
Wow! Great find mzikra...this worked for me as well. Hopefully MSFT will come up with a more robust solution to this problem but this workaround will do just fine for the time being!
Hi, I have tried the solution "remove other columns", but with no success. My data appears valid & exists in Data & Query Editor.
When I open PBI Desktop sometime I get the error message "Something's wrong with one or more fields" it appears to lose references to a long integer col "WorkOrder". It looks like a bug to me as it is random. Sometimes it works, sometimes not.
I can fix in desktop by adding back in "WorkOrder" where the issues are, but this is in around 20 graphs & tables etc - so very painful.
When I repeatedly save and close PowerBI desktop (after fixing the lost WorkOrder detail) when it does open successfully, I can then publish to our company sharepoint workspace, where I can then add my dashboard from various reports.
I am at the stage where I think I will do a new rebuild of my powerBI desktop. I also think this issue may be affecting the online refresh of the Dashboard - but cant confirm until I fix this.
Does anyone have any suggestions before I try new rebuild of desktop file?
Thanks in advance.
Hi, an update: I have found a work around. The issue for me on current version (Oct17) is that PBI appears to fall over with intimittent failure of using a count of field "WorkOrder" as a long integer form ms access. When I change it to text, it works fine.
As an interim, I have formatted my table that I connect to as text, & everything works fine. (I tried zero decimal & it didnt work, so experienced some funnies with numbers for some reason)
I hope this helps someone else.
