Share
Report
124It makes a change to not be seeing a delegation warning where I'd expect one, rather than trying to work around one! Yet I'm a bit confused as to why this is the case.
- I have two SharePoint lists - let's call them Projects and AllContacts - connected together via a Lookup column.
- The AllContacts list is over 2000 records in size.
- My non-delegable query data row limit is 500.
- Documentation states that Choices() and CountRows() are non-delegable in SharePoint.
- I have a PowerApps form that edits records in Projects. I added a card for one Lookup field (let's call it Manager) with a Combo Box to choose the name from the AllContacts list, using the Choices() function - the Items property is set to Choices([@Projects].Manager0).
(incidentally, I don't know why PowerApps added a 0 to the end of the column name - seems to work with and without the 0)
Based on the above, I would have expected the Combo Box to only retrieve 500 records from AllContacts.
However, it looks to me as if the full table is being used to populate the Combo Box. If I set a label to show CountRows(Choices([@Projects].Manager0)), there is no delegation warning, and the full number of records in the list is returned (around ~2700).
By contrast, when I add another card and this time set the Items property to point directly to the SharePoint list (i.e. Items = 'AllContacts'), CountRows('AllContacts') shows a delegation warning and returns 500.
Can anyone explain, please? Is this a known workaround or a new development?
All responses (
Answers (
