Answered

Delegation and lookup using User().Email

(0) Share

Report

Posted on by Community Power Pla... Microsoft Employee

OK, So I seemed to have solved this problem, I'd like to know more about how the lookup function is handling User().email

In my application i need one of my global variables to show the user roll. This user roll is determined by a SharePoint list with roughly 10000 rows.

To do this i initially did the following:

Delegation 1.jpg

This is flagging that the User().Email function has a delegation issue (even though it shows 'Data type: text') This should be able to delegate it, but it wasn't.

So i changed it to:
Delegation 2.jpg

This clears the delegation warning, but still does not retrieve anything beyond the set limit (of 2000)

The solution I have found to this is:

Delegation 3.jpg

Setting User().Email as a variable in itself solves the problem.

Is anyone able to tell me
A) if this is a good work around
B) what is actually happening with User().Email - is it showing text, but actually is first evaluating a record?

Thanks!

Categories:

Building Power Apps

All responses (5)

Answers (2)

Sort by

Verified answer

WarrenBelz 156,774 Most Valuable Professional on at

Like
a
(2)

Report
Copy link

Link copied!
Hi @Anonymous
User().EMail is not delegable, however a Variable is, so set a Global Variable at App OnStart
Set(vUser,User().Email)
Then do
Set(Var_User_Role, Lookup( 'User Roles', vUser = User_Profile_Email, User_Role ) )

Please click Accept as solution if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider giving it Thumbs Up.
Community Power Pla... Microsoft Employee on at

Like
a
(0)

Report
Copy link

Link copied!

Thanks @WarrenBelz!

Why does it not allow the delegation of the User().Email in this situation? even though it returns a text value?
Verified answer

WarrenBelz 156,774 Most Valuable Professional on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @Anonymous ,
You would have to ask Microsoft that one (like a lot of Power Apps anomalies to what we are used to).
I use the workaround on every app and it works fine.

Please click Accept as solution if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider giving it Thumbs Up.
Community Power Pla... Microsoft Employee on at

Like
a
(1)

Report
Copy link

Link copied!

First, thanks for your help!
I've found the reason why my original method didn't work!

The reason User().Email can't be used within this function is that, in this case, we are trying to nest a function that is actually retrieving a record "User().", then filtering to give a text record "User().Email".

When you do the lookup function it evaluates the user "User()" element first, this produces a record. This cannot be delegated, so it never goes beyond this point
WarrenBelz 156,774 Most Valuable Professional on at

Like
a
(1)

Report
Copy link

Link copied!

Ok thanks @Anonymous - a pleasure.
PowerApps is always a joy when you are used to SQL . . .