Earn a 50% discount on the DP-600 certification exam by completing the Fabric 30 Days to Learn It challenge.
I got two reports that have been working for 6 months or so, no I am getting either "canceled by user" or the below error when trying to use the schedule update option for these reports.
"FirstUniqueAncestorSecurableObject' column does not exist in the rowset. The 'FirstUniqueAncestorSecurableObject' column does not exist in the rowset."
They are both SharePoint lists Online. No changes has been made, the schedule refresh just suddenly "broke". ? any suggestions. If I open the report in the desktop tool the refresh is working fine for that source/report.
EDIT: seems to only affect connections that use "SharePoint" as connection/data source. I have other similar reports in the same tenant that use oData, and they work fine.
Solved! Go to Solution.
Seems to be working now.
- Reentering credentials did not help
- Renaming report, upload/republish and refresh worked
Tried that as well yesterday but today at least it worked.
Thanks 🙂
PS: a small minus is that you have to recreate all "links" in your dashboards since the old reports don't work anymore.
Appears to have been fixed as my reports refreshed overnight today.
Still not working for me.
The error disappears as of now in my side, can you try to re-enter the credential or just re-create a new report and try to refresh?
Seems to be working now.
- Reentering credentials did not help
- Renaming report, upload/republish and refresh worked
Tried that as well yesterday but today at least it worked.
Thanks 🙂
PS: a small minus is that you have to recreate all "links" in your dashboards since the old reports don't work anymore.
I have the same problem...even though I did everything
I'm also having the same error on a dataset using a SharePoint list that has been working for months:
Data source error: | The 'HasUniqueRoleAssignments' column does not exist in the rowset. |
Cluster URI: | WABI-NORTH-EUROPE-redirect.analysis.windows.net |
Activity ID: | af12d896-c66c-49a8-910c-9c3b37ecfc36 |
Request ID: | 31ae2671-3e24-0e44-bfbe-c4776e9d11d8 |
Time: | 2017-05-12 07:19:37Z |
I've not managed to work around it. I've recreated the dataset and republished, but get the error as soon as I republish.
Regards, Tony
I am also having the same issue. I'm receiving the following error - The 'FirstUniqueAncestorSecurableObject" column does not exist in the row set. I have loaded the report several times with no resolution. Can someone with microsoft look into this?
I too have the same error on all mye reports.( They originate from the same SharePoint list)
Any news from Microsoft ?
Anyone from the PowerBi team that could look into this issue? Quite time consuming having to refresh and upload a new version just to get updated data from SharePoint.
I've already escalated this problem internally and would post back if there comes any update.
Is there any update on this by any chance? It's becoming difficult to refresh the reports manually daily.
I am seeing the same issue and it just surfaced recently for me as well. I find that I can do a refresh and republish through the tool, but it kinda defeats the point. However it is the only workaround I have right now. Any thoughts on a fix?
I am getting exactly the same issue.
I am getting the exact same error. All my reports which use Sharepoint Online lists are failing. They have been working fine for montths. The issue started on Friday 24th June. They refresh fine in Power BI Desktop. Tried to publish them again but the same error appears.
Please can someone advise?
Thanks
Hello
i hae exactly the same issue "The 'FirstUniqueAncestorSecurableObject' column does not exist in the rowset"
the refresh worked perfectly before but now no way.
regards
I am experiencing the exact same problem - and the issue only appears to be with Sharepoint Online Lists. Started on Friday 24th June. Refresh works fine in Power BI Desktop. Tried to publish again but same problem. Anyone any ideas?