Answered

ClearCollect is Blank

(0) Share

Report

Posted on by Robert_

Hi all,

I'm using the following code on OnStart (App) to collect SP data since my list is greater than 2K. However, although PowerApps recognizes the new name "ViewAllRequests", the data is empty. RowID is a number column, copied from ID and I've indexed in SP. Maybe I need to wait for the Index to complete? There's no delegation or any other warnings with this code.

Concurrent(
ClearCollect(ViewRequestsA,Filter(Requests,RowID < 2000)),
ClearCollect(ViewRequestsB,Filter(Requests,RowID >= 2000 And RowID < 3000))

);
ClearCollect(ViewAllRequests,ViewRequestsA,ViewRequestsB);

Categories:

Building Power Apps

I have the same question (0)

All responses (5)

Answers (1)

Drrickryp Super User 2024 Season 1 on at

Like (0)

Report
Copy link

Link copied!

@Robert_

Concurrent(
ClearCollect(ViewRequestsA,Sort(Requests, ID, Ascending),
ClearCollect(ViewRequestsB,Sort(Requests,ID, Descending));

Collect(ViewAllRequests,Filter (ViewRequestsA,!(ViewRequestsB in ViewRequestsA);

Works for up to 4k records.

Was this reply helpful? Yes No
Robert_ 36 on at

Like (0)

Report
Copy link

Link copied!

Thanks. I get an error on the last Collect:
Invalid schema, Expected a one-column table

I still do not understand why my first code did not work. What happens when I get to 5,000 rows? Why is the original clearcollect blank and is there a way I can backtrace the code to see what it's doing?

Was this reply helpful? Yes No
Robert_ 36 on at

Like (0)

Report
Copy link

Link copied!

Thanks. I get an error on the last ClearCollect:
Invalid schema, Expected a one-column table

I still do not understand why my first code did not work. What happens when I get to 5,000 rows? Why is the original clearcollect blank and is there a way I can backtrace the code to see what it's doing?

Was this reply helpful? Yes No
Verified answer

Drrickryp Super User 2024 Season 1 on at

Like (0)

Report
Copy link

Link copied!

@Robert_

Sorry, it should be

Collect(ViewAllRequests, ViewRequestsA, Filter(ViewRequestsB, !(ID in ViewRequestsA.ID);

Works for up to 4k records

Using collections is not the answer to delegation in large datasets as the various workarounds will cause performance hits. Either use delegatable SharePoint functions and operators or move your data to Sql or Dataverse.

Was this reply helpful? Yes No
Robert_ 36 on at

Like (0)

Report
Copy link

Link copied!

Thanks so much @Drrickryp ! Worked like a charm.

Was this reply helpful? Yes No