Unanswered

Delegation warning on using "in"

(0) Share

Report

Posted on by AnubhaKumari

We are building a Ticket management Queue with PowerApps. Users can select multiple items in the gallery and then update status for all.

Problem Statement: When one user updates the Status for some items and at the same time the second user who does not see the most recent updates tries to work on the same items with Multiple selection.

Current Implementation: To Avoid the multiple user updates, at the time user clicks Submit we are looking into the Data Source(SharePoint List) and validating if the Status for the ID's are different from the Status visible on the users screen and based on that we are notifying user that they do not have the updated data and hence the change failed.

We are using "in" to look into the data source which gives us a Delegation warning. Is there any Alternative Solution to avoid the Delegation issue as the data will definitely keep growing in the SharePoint List.

Categories:

Building Power Apps

I have the same question (0)

All responses (2)

Answers (0)

Yogesh Murugan 443 Moderator on at

Like (0)

Report
Copy link

Link copied!

Try this method
Add Datasource into the collection
Eg:SPlist
Clearcollect(ColSplist,SPlist);
To replace that source to collection will avoid Delegation

Was this reply helpful? Yes No
TheRobRush 11,128 Moderator on at

Like (0)

Report
Copy link

Link copied!
The above will not work when, as you mentioned, your splist grows above the maximum threshold.

Just do something like this with multiple items something like this should work

With( {tempList: ForAll(put the selected items IDs here) As idList, LookUp(yourSPList, ID=idList.Value))}, If(CountRows(Filter( ForAll( idsYouAreWokringOn as checkList, If( checkList.Status = Lookup(tempList, ID=checkList.ID).Status, true, false)), Value=false))=0, what to do if everythign matches, what to do if it does not))

something similar to that would work since it is prefiltered, typed on my cell so may have some typos to fix but it should be close.

Was this reply helpful? Yes No