Forum Discussion
SPO Thresholds - Major Issue!!
I apologize in advance as I’m about to go off on a rant. Microsoft needs to address the SPO threshold issues. it is impossible to develop an enterprise level solution with a limit of 5000 list items and threshold on lookup lookup columns. Sure you can get around the 5000 items with odata and list views, but once exceed the 5000 item threshold your configuration is locked. I ran into a new error today. I have a lookup column that references item in the current list, so I can tie items together for project management purposes. Out of no where I am receiving a JSON JavaScript max size error. I had to completely reconstruct and reconfigure the lists and Power Automate. Naturally, there’s zero documentation or reference to this unpublished threshold. To make things worse Microsoft’s support is absolutely useless. I’ve contacted them several times on a variety of different issues. Almost all of my issues remain unresolved. On top of it the entire helpdesk community is one of their third-parties located in a different time zone. Good luck getting someone from the US-based support team. How is it that we are in 2023 and Microsoft cannot deliver an enterprise level solution to support businesses. At least give me the pay-for-play option to increase and manage my thresholds. It’s legitimately BS.
I am not looking for an apology. I am looking for Microsoft to fix the problem!!
2 Replies
- First of take a breath and calm down.
Secondly the 5000 item limit is both for the server but also for your computer, it will bog down a hell of alot of resources having all of that loaded into memory. That's why you need to use Pagination, you can that in power automate to get more than 5000 item without needing to redo your whole flow.
This is well documented.NicolasKheirallah thanks for the response. I am already using pagination in Power Automate - note, its limit is 100,000. I have been able to navigate around the limits of PA, it’s SPO where I have my issues. Here are my major issues, which you cannot get around:
- You cannot change the configurations of a list when they’re more than 5000 items in it. I have literally had to re-create my list structure with changes and migrate the data from the old list to the new list to get around. I should not have to do this.
- There are restrictions on the number of look up in people columns you can have in a SharePoint list. And if you don’t carefully navigate it, you will receive threshold issues.- The biggesr issue came up yesterday where we started receive JSON JavaScript issues. Come to find out it’s due to a lookup column that we have looking up into the original list. When I delete this column, everything goes back to normal. When I had the column back, the issue arises again. Bear in mind this was working fine without any changes until yesterday. This unnerving as my team has spent over 160 hours on developing and testing a solution to suddenly not work. This application is in production, so it is having a huge impact on our business.
Thanks,
Scott
