Forum Discussion
Power BI doesn't import All Records from SharePoint List with Item-level Permissions
Hi all,
I have a SharePoint list with Item-level Permissions; in this way, each user can only interact with their own records. The owner of the Sharepoint list has full control on it and he is able to see and edit all items. Until 03/14/2024, I had the situation I showed you before: reading the list via Power BI and setting the connection with the owner account, I was able to read all the records in the list.
From the 15th, the situation changed and I have this problem: on Power BI, only the records created by the owner account are import and those created by other users aren't visible.
Why doesn't Power BI inherit the Cancel checkout permissions anymore? How can I solve this issue?
Thanks,
Fern_21
Hi all,
Update:
SharePoint team applied the mitigation, and the issue has been resolved.
Please check. If there are still issues, please feel free to contact me.Best Regards,
Gao
Community Support TeamIf there is any post helps, then please consider Accept it as the solution to help the other members find it more quickly.
If I misunderstand your needs or you still have problems on it, please feel free to let us know. Thanks a lot!How to get your questions answered quickly--How to provide sample data in the Power BI Forum--China Power BI User Group
21 Replies
Hmm you scared me for a second so I went back and checked some of my reports where I use this same feature and they are all still working normally. Are you sure that the account you are using has full control permission on the list? I'm not familiar with "cancel checkout" in the way you mention, but full control permission should bypass the item-level permissions.
I didn't have any problems for three years and I have full control permission on the list.
On Sharepoint it is ok, but on Power BI I have this problem now.I have the same problem. Has anyone solved it?
I have the same problem from 15/03/2024, I am using connections 1.0 and 2.0 , I have same issue. I have full access control but it now work properly using power query on Excel, Power Bi and Dataflow.
Same issue, this needs sorting fast. Tried many ways as other posters. We have many dahsboards and teams using this and it is massivley impacting our business. MS needs to get this sorted with a mater of urgency,
- For me the issue is resolved by now.
Same here. Looks like it works as it should now.
Hi all,
Update:
SharePoint team applied the mitigation, and the issue has been resolved.
Please check. If there are still issues, please feel free to contact me.Best Regards,
Gao
Community Support TeamIf there is any post helps, then please consider Accept it as the solution to help the other members find it more quickly.
If I misunderstand your needs or you still have problems on it, please feel free to let us know. Thanks a lot!How to get your questions answered quickly--How to provide sample data in the Power BI Forum--China Power BI User Group
For me the issue is resolved , thank you by support
Hi Fern_21 ,
Does Power BI here mean Power BI Desktop or Power BI Service?
Could you provide a version of Power BI?
Have you or the organization done anything before this that might affect permissions?
I will try to investigate and reproduce the problem.Best Regards,
Gao
Community Support TeamIf there is any post helps, then please consider Accept it as the solution to help the other members find it more quickly.
If I misunderstand your needs or you still have problems on it, please feel free to let us know. Thanks a lot!How to get your questions answered quickly--How to provide sample data in the Power BI Forum--China Power BI User Group
I've the same problem in both Power BI Desktop and Power BI Service.
I'm using the Version: 2.124.2028.0 64-bit (December 2023) but also reports in PROD Environment for years have this problem.
Same issue here, independent of PBI Desktop version, same issue happens with Excel Power Query, must be a recent change made to the SPO connector. Please fix urgently!
Same problem here... The issue started today on our tenant, probably a late roll out.
This happens with lists AND libraries not inheriting parent web permissions OR using the item level setting ("Read Items that were created by the user", "Create items and edit items that were created by the user") is not loaded into the model, even using an "almighty acc" for the connection.
Is this an issue, "a new feature" or a new setting?
