cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
ruth
Helper IV
Helper IV

Collection not collecting all rows

I'm creating a very basic collection from a contacts sharepoint list. the list contains approximately 10k records. For some reason, not all the rows are being "collect". The records that are not being included are random. I know there are issues when working with a table greater than 2000 rows, but my understanding is that collections do not have the same limations.  

 

My code is in fact basic - ClearCollect(ccContact, tblContact)

 

Any ideas?

 

ruth

21 REPLIES 21

@CNT I'm using Sharepoint. I do have the internal ID that sharepoint creates as the unique column.  For this dataset, it is actually 5856 rows.  

@ruth Please make sure that this setting is correct,

CNT_0-1622556079136.png

 

Could you try this,

 

Add a button and place this code in the OnSelect property ,

ClearCollect(cEventLog, Filter(tblEventLog,ID >3856 && ID<=5856))

 

Place this code in the Text property of the Button,

"Count: " & CountRows(cEventLog) & " LastID: " & Last(cEventLog).ID

 

What do you see when you click the Button?

Settings confirmed:

ruth_0-1622557198629.png

Result 0 and blank

 

I event created a new app, modified my table to include a column w my own id, populated 200 rows w my own sequential id, changed the settings in the new app to 100 and only 100 rows is retrieved.

 

I am using Sharepoint Online. 

@ruth what you say is right. If you set the limit to 100 you will get only 100. If its 2000, you will get 2000. So you have to collect them in batches of 2k.

@CNT , right but that's what I was trying to do. I was trying to collect 200 rows - populated 200 rows w the unique id and then tried to load in batches using the same samples in this chain. And it's only retrieving 100.  So in all situations, I cannot access beyond the the data row limit.  It's consistent.

@ruth I understand your struggle.

Each batch should fetch 100 records. Then we put them together to get 200. Isn't that happening? 

 

No, that's not happening. It's consistent. I can't imagine this is a limitation of Sharepoint Online. Unless there is something I'm completely missing - which I hope to be the case.

 

ruth_0-1622560297487.png

 

ruth_1-1622560363247.png

 

ruth_2-1622560494434.png

 

ruth_3-1622560543815.png

 

 

@ruth the second image with the formula is not clear. Would you mind copying the formula into the chat box please. 

@CNT , actually there was an error in that code. Once I corrected it, that test scenario worked!!! So, it seems as if I cannot use the internal ID in Sharepoint as I would get a delegation warning and it won't work.  However, if I do use my own internal id defined as a number and use the same logic/approach, I won't get a delegation warning and it will work.

@ruth Yea, I tested it and can confirm that when Collecting from a SP List based on the Built in ID it returns only the maximum number of records set in the Data Row Limit, even when collected in batches. But when we use another column (our own ID) to collect the records, we can go past the Data Row Limit and get all the records in batches.

 

To me this looks like a BUG. If possible, try and raise a ticket with Microsoft.

Helpful resources

Announcements
Power Platform Call June 2022 768x460.png

Power Platform Community Call

Join us for the next call on August 17, 2022 at 8am PDT.

Power Platform Conf 2022 768x460.jpg

Join us for Microsoft Power Platform Conference

The first Microsoft-sponsored Power Platform Conference is coming in September. 100+ speakers, 150+ sessions, and what's new and next for Power Platform.

Users online (4,085)