I have had a lot of success eliminating the delegation issue with many of my statements. There is one that perplexes me a little. Well, I suppose I dont need to know the reason, but people picker fields used in searches dont seem to be delegation friendly. I would like to understand a little of the consequences of this. My question, if there is a delegation issue with a statement, is the ENTIRE thing subject to my 500 (default) record limit? Or, is there some limit with regards to the number of people in the database?
Statement:
Filter('Engineering Change Notice', Engineer.DisplayName=User().FullName, ECN_Status_PowerApps_Value<=3 || ECN_Status_PowerApps_Value=99), "ECN_Status_PowerApps_Value", Descending, "Part_x0020_Number", Ascending))I'm guessing, as written, this limits these seach to the first 500 items in 'Engineering Change Notice'?
All that is marked blue is this:
My hope is that the delegation issue does not affect record limit to 'Engineering Change Notice'. I guess I would like to know the specific consequences here.
I am also thinking... if I nest the people picker filter outside of the other filter, will that allow all items to be searched in the database, but then those results are then limited to 500 for the people picker filter?
Filter((SortByColumns(Filter('Engineering Change Notice', ECN_Status_PowerApps_Value<=3 || ECN_Status_PowerApps_Value=99), "ECN_Status_PowerApps_Value", Descending, "Part_x0020_Number", Ascending)),Engineer.DisplayName=User().FullName)
Thank you.
