SharePoint integration issues recently

[zarski]

Hi,

I have noticed issues recently with two of my SharePoint custom forms after publish. Forms have been working just fine before, but now after publish, it won't open the SharePoint item to the main SharePointform1. It only shows "Getting your data..." and the item won't open. I have only "SharePointIntegation.Selected" in the SharePointform1 Item property.

My SharePoint lists are quite large, both have more than 500 items. I noticed if change the app settings and raise the non delegable item limit from the default 500 to 2000 items and publish the app, it starts working again and the item opens! But this shouldn't be like this, I shouldn't have to raise that limit. The studio show's no delegation warnings or errors. What an earth is going on?

[poweractivate]

---

@zarski wrote:
...raise the non delegable item limit from the default 500 to 2000 items...

...The studio show's no delegation warnings or errors. 

---

I wouldn't rely on the yellow triangle warning always showing. There is no such thing as a "non delegable item limit".

The limit you refer to is called the Data row limit.

The data row limit is not limited to the context of delegation. When you use a formula, like say, ClearCollect , Set or any other function, the number of items returned by this function is going to be, at most, the data row limit. No warning is shown when this happens, because there is no delegation issue here, just the data row limit - so no warning is issued if something, e.g. a Collection, or anything else, is expected to have more Records than the data row limit - and yet it doesn't. Each time Collect is called, for example, the amount of Records processed each time it is called, would be no more than the Data row limit. Also consider the example of ForAll which itself returns a Table. The Table returned by ForAll would itself also have no more records than the data row limit, and no warning is shown when this happens

While using the Items property of a Gallery may cause there to be some different behavior, since Galleries themselves just work differently, and certain aspects of Galleries cause them not to have the data row limit applied to them - the rules described above, generally apply anyway.

However, if you are saying the behavior has changed then there may be an issue. 

I would recommend in your case to 

Create a new Power Platform Support Ticket

in case there is some issue for you and to get more personalized help on your issue.

[WarrenBelz]

Hi @zarski ,

Try as the Item

LookUp(
   YourSPListName,
   ID = SharePointIntegration.Selected.ID
)

or (a bit of overkill)

With(
   {wID: SharePointIntegration.SelectedListItemID},
   LookUp(
      SPListName,
      ID = wID
   )
)

I have noticed the same thing myself recently.

Please click Accept as solution if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider giving it Thumbs Up.

Visit my blog Practical Power Apps

[zarski]

Thanks @poweractivate for the "Data row limit" clarification. I've got everything in Finnish so I made a wild guess 🙂

Thanks @WarrenBelz , I'll try those with the LookUp function, but we really shouldn't have to do this..

[Mithrandil · Accepted solution]

This seems to be an issue with the latest Power Apps release. I've had the issue with multiple tenants, where Sharepoint Integration fails to connect to the data with Power Apps version 3.22102.32.
If you go to Settings > Support, and change the Authoring Version to 3.22092.25 and publish with this version, it should work again.

[zarski]

Thank you @Mithrandil so much, this did the trick!!!

[poweractivate]

@Mithrandil @zarski 

Those are temporary troubleshooting measures. They may stop working in the future.

You both should do these steps, or ask your admin to do them, as soon as possible:

Create a new Power Platform Support Ticket 

[zarski]

Thank you @poweractivate , I've already made a power platform support ticket and I'll share this discussion with them.

[Sgalle]

Thank you, that solved my issue too.

Strange, my app never complained about it before...

[KenSprNC]

We saw the same issue starting last week. A Power App update auto applied to apps this week and seems to have solved the issue. Our current authoring version is 3.22102.33 as of 10/25/22 (GCC/government platform).