Is delegation still not available for Dynamics 365? It says that it is in this post: https://powerapps.microsoft.com/en-us/tutorials/delegation-overview/ however, I have tried doing a row count for a filtered datasource and I still don't get all of my records.
If I try this I get a result of 500:
and if I apply this filter on my data I would expect a count of 6, but I only get 3:
CountRows(Filter(Leads, firstname = "Aaron"))
The queries above were just tests, but the main thing I am trying to do is LookUp a specific record from the DataSource using a LeadId and then show a few values from that Lead in a form (name, email, etc.). I've tried three different Lead Ids, one of them works, while the other two do not return any data (even though I can see values in CRM). I'm guessing that the 500 record limit is in place still and that these records are not in my DataSource.
So I'm guessing that delegation isn't working or I'm doing something wrong?
Hi @Shannon, in regards to the first part of your question, a CountRows will only ever return a maximum value of 500 irrespective of whether the data source is delegable or not. This is because CountRows is not (yet!) a delegable function.
However, FIlter is a delegable function so you should get all 6 of your Aarons back and not just 3. In your expression, the CountRows comes logically after the Filter so that it should not affect the delegation of the filter operation.
I hope someone from the PowerApps team will pick up on your question.
I agree with what @Meneghino said that CountRows is not yet a delegable function. About this, you can submit this idea in the PowerApps Ideas forum, so it might be considered for future releases.
About that the filter is not working correctly either, would you please change another record to test if this is record specific issue?
Yes as @Meneghino stated, I had another thread that turned into this same conversation here: https://powerusers.microsoft.com/t5/PowerApps-Forum/Unable-to-filter-data-outside-of-500-records/m-p...
An MS user replied and said they would notify on their side. I've tried a few different filters on a few different Dynamics 365 environments/entities, and I have the same issue.
Keep your eyes open for our upcoming T-shirt design contest!
Fill out a quick form to claim your user group badge now!
Find out where you can attend!
Features releasing from October 2019 through March 2020