Office365User.UserProfileV2 Error Message

[tagustin2020]

Hello,

I'm seeing the following error message when a user is on the first screen of a multiscreen form experience and was wondering if anybody could help me figure it out. The logged in user's name prepopulates the Requestor field as intended and the issue doesn't prevent the user from submitting the form, but obviously it is not a good user experience to see the banner prominently displayed while they are filling in the form.

This is the Items formula of the combobox:

This is the DefaultSelectedItems formula which I understand returns a record that is compatible with the Items property of the combobox, but is not a SharePoint person record per se. The reason for the Coalesce statement is that we want to provide for scenarios where someone may be filling in the form on behalf of someone else.

Office365Users.SearchUserV2({searchTerm:Coalesce(ThisItem.Requestor.Email,User().Email)}).value

Thank you in advance for your help.

Teresa

[Alex_10]

@tagustin2020 

from the error text it looks like there is no connection to the combo box (different functions).
i would try to find 'Office365Users.UserProfileV2' code usage in the app first.

[tagustin2020]

@Alex_10 

Thank you for the advice, Alex. I'm not sure how to implement it. Can you provide a little more detail?

Kind regards,

Teresa

[Alex_10]

@tagustin2020 

i mean you need to find in your app all controls/places that use Office365Users.UserProfileV2 function.
your dropdown uses Office365Users.SearchUserV2() which is not Office365Users.UserProfileV2  displayed in the error.

[tagustin2020]

@Alex_10 

Do you mean in the OnStart of the app somewhere? I'm afraid I am still too new at this to understand what you mean without specifics.

Thanks,

Teresa

[Alex_10]

@tagustin2020 

if that error appears only once when you open the app, then it may be in App.OnStart or your first screen.OnVisible.

there is also a search icon (magnifier) on the very left vertical panel when you edit the app.

You may try to search there by typing Office365Users.UserProfileV2

[tagustin2020]

@Alex_10 

Hi Alex,

The error appears after I click the New Request button and am taken to the first form screen. I already have one user variable that is used throughout the app:  Set(varUser, User()) which is why you see the varUser2 experiment below. I came up with the following syntax based on a video from Dave's Tech Tips since I still wasn't clear on how to implement your advice - PowerApps User() function & Office365Users - YouTube

I am still getting the same banner error message on the first form screen with this formula inserted into the OnStart of the app. Perhaps I am close, but just off a little? Any advice on how to tweak either the OnStart formula or the Items and DefaultSelectedItems formulas?

    Set(
        varUser2, {UserProfile:Office365Users.UserProfileV2(User().Email)}
    ),

This is the OnSelect formula for the "New Request" button in the app. Is there something I need to add to this formula?

Set(
    varRecord,
    Defaults('Drafting Request List')
);
ResetForm(frmMasterNew);
Navigate('New Request Screen');

Thank you for hanging in there with me.

Teresa

[Alex_10 · Accepted solution]

@tagustin2020 

So the button 'New request' is on one screen (eg Home Screen).
When you click on that button, it navigates you to another screen (New Request Screen).
Once the screen with the form (New Request Screen) pops up, you get the error.
Is that right?

If yes, you need to find a control on that screen (New Request Screen) that uses code Office365Users.UserProfileV2.
Basically, this error says that Office365Users.UserProfileV2() gets a blank input parameter.
And setting varUser2 in onstart likely does not cause that error.

[tagustin2020 · Accepted solution]

@Alex_10 

Hi Alex,

To answer your questions:

1) Yes, the New Request button is on the home screen and when you click on that button, it navigates you to the New Request Screen.

2) Yes, the error appears once the New Request Screen is visible.

I added the following variable to the OnStart of the app:

    Set(
        varFormUser,
        {Profile: Office365Users.MyProfileV2().id}
    ),

Here are the Default and Update properties for the data card:

Default: ThisItem.Requestor
Update:
If(cbRequestorNew.Selected.Mail <> ThisItem.Requestor.Email,
    // If the selected person in the combobox is different than the underlying record, then
    // use a record that is a valid SharePoint person schema record made from the combobox
    { 
      Claims:"i:0#.f|membership|" & Lower(cbRequestorNew.Selected.Mail), 
      Department:"", 
      DisplayName: cbRequestorNew.Selected.DisplayName, 
      Email: cbRequestorNew.Selected.Mail, 
      JobTitle:"", 
      Picture:""
    },
    // If the selected person is the same as the underlying record, then just use that record...
    // ...it is already a record with the proper schema.
    ThisItem.Requestor
)

I provided this in an earlier post, but for the sake of keeping everything together here are the Items and DefaultSelectedItems for the ComboBox:

Items:
Office365Users.SearchUserV2({searchTerm:cbRequestorNew.SearchText,top:100}).value

DefaultSelectedItems:
// This will return a record that is compatible with the Items property of the combobox...but not a SharePoint person record
Office365Users.SearchUserV2({searchTerm:Coalesce(ThisItem.Requestor.Email,User().Email)}).value

I have a hidden data card in the form that collects the user's email address. Here are the data card properties:

Default: ThisItem.'Requestor Email'
Update: txtRequestorEmailNew.Text

Here is the Default property of the text value field:

If(
Office365Users.UserProfileV2(cbRequestorNew.Selected.Mail).mail <> ThisItem.'Requestor Email',
Office365Users.UserProfileV2(cbRequestorNew.Selected.Mail).mail, ThisItem.'Requestor Email')

I see your advice, "you need to find a control on that screen (New Request Screen) that uses code Office365Users.UserProfileV2". I added a UserId single line of text column to my SharePoint list and added the data card to the form. Here are the Default and Update properties of the data card and the text field within it.

Default: ThisItem.UserID
Update: txtReqUserID.Text

Text value field Default: Office365Users.UserProfileV2(varUser.Email).id

The UserID is a long string of numbers and hyphens.

I thought this was the solution, but I'm still getting the id error message. I think it is because of the way the DefaultSelectedItems of the combo box is set up. Note the comment that the schema is compatible with the Items property of the combobox, but not a SharePoint person record. Any ideas on what adjustment I could make to that formula? 

Teresa