Forum Discussion
Using SharePoint List Choice field in PowerApps
I've tried both the ChoiceColumn.Value and Calculated Column alternative and both indeed work for me except I am getting the blue dot/blue squiggly line warning about delegation. As I understand it, it works in test now, but when the list grows over 500 records, it will break. So I need an alternative. The only one I can think of it to use a workflow to copy the Choice field into a text field in SharePoint and put an index on that field. That will certainly work and avoid delegation, but is smacks of a hack. Are there any other solutions? For those who need to see code to understand, this is the phrase that is causing the delegation issue for me.
Filter('Store Task Template',Status.Value="Complete")
Curious if anyone has revisited this since December. I tried the calculated column trick. When I do it, I get the blue dot, PLUS the filter doesnt work!
Additionally, if you use the .VALUE trick, it just says invalid name, and doesnt even let you use it.
Did something change?
Deleted wrote:
I've tried both the ChoiceColumn.Value and Calculated Column alternative and both indeed work for me except I am getting the blue dot/blue squiggly line warning about delegation. As I understand it, it works in test now, but when the list grows over 500 records, it will break. So I need an alternative. The only one I can think of it to use a workflow to copy the Choice field into a text field in SharePoint and put an index on that field. That will certainly work and avoid delegation, but is smacks of a hack. Are there any other solutions? For those who need to see code to understand, this is the phrase that is causing the delegation issue for me.
Filter('Store Task Template',Status.Value="Complete")
Yes, I just retested both methods (Filtering on a choice column as well as on the calculated column). No change. Both work and both display the blue dot and blue squiggle in the code indicating delegation issues. I cannot really put this app into production because I will hit 500 records in about 2 days, at this which, I would have egg on my face.
All,
I recently have started to see this issue, again. I fixed it by using the calculated field trick, but my list got too long,and thus crashed it. Now, for another list, I am searching through an actual choice column; which somehow hasn't crashed, or thrown any errors.
Has anybody got a better fix than random miracles?
- I use a Flow to solve this. When item is updated I write the text value to a text field and then in PowerApps filter on the text field. It can mean a lot of Flow runs so watch your allocation. Also add another field for last updated by Flow and compare that to updated or you will get a looping Flow as the update will trigger the Flow again.
