delegable alternative for 'IN' operator

(0) Share

Report

Posted on by IMathur

291

Hi Folks.

below is the formula, i want to implement, in Gallery>Items>

AddColumns(changepoint, ItemSort, LookUp(changepoint,useremail in changepoint.TeamLead || useremail in changepoint.ProjectManager,true));

useremail is variable for user().email

It is not working, please help

Categories:

Building Power Apps

I have the same question (0)

All responses (8)

Answers (1)

mdevaney 29,989 Moderator on at

Like (0)

Report

@IMathur

I think you should use equals (=) here instead of in. My assumption is you have only one Team Lead and one Project Manager. If these fields are people fields do not allow multiple selections. That way you can use the equals operator.

There is no true delegation workaround for IN within SharePoint. You must change your data’s structure.

---
Please click "Accept as Solution" if my post answered your question so that others may find it more quickly. If you found this post helpful consider giving it a "Thumbs Up."

Was this reply helpful? Yes No
Pstork1 68,697 Most Valuable Professional on at

Like (0)

Report

Is the ChangePoint.TeamLead a user/person column? And is it set for one entry or multiple? If its a single entry user/person field then you need to use StartsWith() instead of In and reference the email address of the TeamLead (TeamLead.email) since TeamLead would be an object not a string.

Was this reply helpful? Yes No
IMathur 291 on at

Like (0)

Report

Hi @Pstork1 , ProjectManager is a Single entry person/group column and TeamLead is Multiple entry person/group column

Was this reply helpful? Yes No
IMathur 291 on at

Like (0)

Report

Hi @mdevaney , if i use = operator , below is issue that arises.

and useremail is text
and TeamLead is multi select person column

Was this reply helpful? Yes No
mdevaney 29,989 Moderator on at

Like (0)

Report
@IMathur
The equals operator will not work with a multi-select person column. DataTeamLead would have to include only 1 person. Then the code would be:

useremail = DataHubTeamLead.Email

---
Please click "Accept as Solution" if my post answered your question so that others may find it more quickly. If you found this post helpful consider giving it a "Thumbs Up."

Was this reply helpful? Yes No
Pstork1 68,697 Most Valuable Professional on at

Like (1)

Report

Startswith() can be used on the single user column and it is delegable, but there is no alternative for the multi user column. Also the user returned is actually an object so you need to specify the .email property wehn using StartsWith(). See @mdevaney 's comment.

Was this reply helpful? Yes No
IMathur 291 on at

Like (0)

Report

Hi @Pstork1 and @mdevaney , I have to include this multi user column as this column is quite important, can there be a work around that can be implemented?

Was this reply helpful? Yes No
Verified answer

Pstork1 68,697 Most Valuable Professional on at

Like (0)

Report
There is no workaround for a multiuser column. For that you would need the IN operator which is non-delegable. The only real workaround for this is to find some other way to pre-filter the data source using a delegable operator which will get it below the delegation limit. Then you can ignore the warning. To do that just replace the use of the data source in your statement with a Filter() function that is delegable and will get the record set below 500 (2,000 if you've increased the limit to the max). For example, imagine your list included a department entry. You could then use the following statement.

AddColumns(Filter(changepoint,Dept = "some department"), ItemSort, LookUp(Filter(changepoint,Dept = "some department"),useremail in changepoint.TeamLead || useremail in changepoint.ProjectManager,true));

Was this reply helpful? Yes No