I have a PowerApps app which uses the Office365UserProfileV2 connector.
This message appears at runtime but not in preview.
How do I go about finding more information about this error?
Solved! Go to Solution.
For your information I've solved it in this way:
If(
!IsBlankOrError(glryDirectory.Selected.Mail),
Office365Users.UserProfileV2((glryDirectory.Selected.Mail))
)
------------------
Note that glryDirectory has as its Item property a Office365Users call of its own:
Sort( Filter( Office365Users.SearchUser( {searchTerm:Trim(PeopleSearchBox1.Text), top:75}), AccountEnabled,), DisplayName,Ascending)
============
My theory is that this is an 'order of operations' problem -- that the UserProfileV2 runs before the value of glryDirectory.Selected.Mail finishes processing - so it runs with a blank value for mail, which of course is invalid.
Notice the ! NOT operator before IsBlank.
Hi @GeorgeWinters,
Can you share more details with your apps?
What is your formulas with Office365.UserProfileV2 function?
Which control do you apply that function to?
Have you ever tried to delete Office365 connection and re-add it to check if the issue is gone?
Also i think you should post more information, so that we can be easier to helo you.
Best regards,
Sik
For your information I've solved it in this way:
If(
!IsBlankOrError(glryDirectory.Selected.Mail),
Office365Users.UserProfileV2((glryDirectory.Selected.Mail))
)
------------------
Note that glryDirectory has as its Item property a Office365Users call of its own:
Sort( Filter( Office365Users.SearchUser( {searchTerm:Trim(PeopleSearchBox1.Text), top:75}), AccountEnabled,), DisplayName,Ascending)
============
My theory is that this is an 'order of operations' problem -- that the UserProfileV2 runs before the value of glryDirectory.Selected.Mail finishes processing - so it runs with a blank value for mail, which of course is invalid.
Notice the ! NOT operator before IsBlank.
@GeorgeWinters, I have an app that was running great with the implementation of your solution. However, a few months ago, the error popped-up again without making any changes to the code. Do you know if there has been an update that has made your solution stop working?
Thanks!
No, I don't, sorry. I'm not using this workaround presently.
The first Microsoft-sponsored Power Platform Conference is coming in September. 100+ speakers, 150+ sessions, and what's new and next for Power Platform.
Power Platform release plan for the 2022 release wave 2 describes all new features releasing from October 2022 through March 2023.
User | Count |
---|---|
200 | |
96 | |
56 | |
51 | |
42 |
User | Count |
---|---|
263 | |
157 | |
83 | |
80 | |
57 |