Forum Discussion
Strange Sharepoint List integration question
- 10 years ago
After pulling my query into Power Query in Excel to troubleshoot, I found out the following:
The RoleAssignments issue that it was running into is actually a column automatically generated by Sharepoint. In order to access that column, and see what roles have access to it, you need admin rights - which I didn't have. So it wasn't an issue with not having access to the data in the list, or the list itself, the issue was not having permission to see who else had permission for that column.
By simply removing that column "RoleAssignments" from the query, it was no longer trying to access it, and the query worked fine. I also removed a bunch of the other columns I didn't need to query, including that mysterious duplicate "Id" and "ID" column.
I'm going to mark as solved for anyone else who might have the same issue.
After pulling my query into Power Query in Excel to troubleshoot, I found out the following:
The RoleAssignments issue that it was running into is actually a column automatically generated by Sharepoint. In order to access that column, and see what roles have access to it, you need admin rights - which I didn't have. So it wasn't an issue with not having access to the data in the list, or the list itself, the issue was not having permission to see who else had permission for that column.
By simply removing that column "RoleAssignments" from the query, it was no longer trying to access it, and the query worked fine. I also removed a bunch of the other columns I didn't need to query, including that mysterious duplicate "Id" and "ID" column.
I'm going to mark as solved for anyone else who might have the same issue.