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
Hi everyone,
I also am having this issue with a datasource that connects to a shared drive. I just reached out to the person who manages the database (large excel file) and asked if he changed anything with that column that was being referenced by the error. He responded that he deleted a space in front of the column (e.g. [ ColumnA] -> [ColumnA]). My PBI Desktop did not detect the difference but I am experiencing this when I refresh from the Service. To test, I had him add the space back and the gateway refresh worked successfully.
It sounds like there's a patch but I wanted to share in case this space may be the root cause...? In the past I have had issues with downloaded SharePoint lists adding a space to the front of the column header after opening the document in desktop excel. This might be why everyone was experiencing this problem with SP lists.
Hope this helps!