Replies: 2 comments 1 reply
-
|
Hi @MikeStall So using Instead of cheers |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
Will this transition fix the current oops that in Canvas that according to the docs, the Email property actually returns the UPN? If not, this seems like the perfect time. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Power Fx supports a standard
Userobject for describing the current user.In Power Apps, this is the User() function, but that will be migrated to the User object too.
The User object has a curated well-known set of properties with strong semantics. The properties are:
FullNameEmailDataverseUserIdLookUp([@Users], ThisRecord.User = [@User].DataverseUserId).'Primary Email'TeamsMemberIdEntraObjectIdA host provides a derived instance of the Microsoft.PowerFx.UserInfo class. This describes which properties are supported and has virtual getters to allow fetching the properties. The getters are virtual and async to allow lazily fetching values which may require a network call.
BasicUserInfois a derived class that makes it easy to implementUserInfo.For a host to enable User object,
determine which properties the host will support. This can be set on the symbol APIs,
Call
SymbolTable.AddUserInfoObject(..)on symbols and provide a string array of the supported keys.at runtime, passes in the corresponding values via a UserInfo object.
Call RuntimeConfig.SetUserInfo(userInfo)References:
Beta Was this translation helpful? Give feedback.
All reactions