People Picker filter not working in a sudden

[evanzhang]

Hello Team,

Please repro the issue with the following steps:

a. From any SharePoint online list, create a users&Groups column.

b. Go with customize forms in PowerApps.

c. Edit anything and Save.

d. Press F5 and you'll find people picker is not loading anydata with autofill.

e. Pulish the change to SharePoint, the same issue is happening with SharePoint forms (PowerApps) when you create an item or edit existing items.

f. This is reproduced with multiple SharePoint Online sites on my end.

This was working perfectly yesterday.

[dinusc]

@andrewFiveP, Can you please provide the steps to reproduce this issue? I could not reproduce it by binding a ComboBox control to a SP List Person/Group column with multiple selections enabled. I use the following formula: 

Choices(SPListName.MultipleSelectPerson)

Please also make sure the proper Title, SubTItle, SearchField and Picture fields are configured on the ComboBox control.

[dinusc]

The current ETA is for the middle of September.

[maverick17]

@dinusc - that ETA is unacceptable. People pickers are a key part of our applications. This seems to have showed up as of version 3.18083.31.

[andrewFiveP]

@dinusc Happy to reproduce. Steps are Fairly simple.

Create a new custom list.

Add a person column to that list.

Select Customize Forms with powerapps.

Add the person column to the form via the data source:

From there publish the form or even test it inside the designer and the people picker does not return results or even brings up suggestions.

I will open a service request to chase this up further with the official channels. As the OP said this started happening Monday morning and worked last Friday.

[dinusc]

According to the provided steps, this is the issue that is neing descissed in this thread. The ComboBox works fine in "multiple selection" mode and I was confused about "multiple tenants" which in yhour case probably means multiple ComboBoxes in a single selection mode.

[dinusc]

@maverick17, please do so. That it will help tracking the issue.

Thanks,

[Anonymous]

Just throwing this out there in case it relates to or helps provid information for this issue.

I am also having an issue similar to this, though I am not positve if they correlate.

We noticed this issue a couple of days ago. Using a SQL View as the datasource, we have a lookup on a dropdown control that won't always pull the correct information. It seems like it occansionally can't see certain records.

[dinusc]

Please note that the fixed version should be available in the next couple of days.

[scotthanks]

Thank you, @dinusc.  The issue just started for us today, so I'm guessing it will be another week after it's released before we get the fixed version.

The workarounds others have suggested didn't work for me.  Here's the workaround I came up for any of my apps that can't wait for the fix.  I added the Office365Users data connection to the app and text input and list box controls to the card with the people field. The text input is visible in place of the combo box and defaults to ThisItem.PeopleField.DisplayName. The list box Items property is set to:
Office365Users.SearchUser({searchTerm: TextInput1.Text})

I changed the Update property of the card to:
({'@odata.type':"#microsoft.Azure.Connectors.SharePoint.SPListExpandedUser",Claims:"i:0#.f|membership|" & Lower(ListBox1.Selected.UserPrincipalName),Department:"",DisplayName:ListBox1.Selected.DisplayName,Email: ListBox1.Selected.Mail,JobTitle:".",Picture:"."})

When you start typing a name in the text input control, the list box populates with matches. Selecting a name in the list box control will update the SharePoint people field.

I took it a step further by configuring the text input control to replace your search text with the selected name when you select one. I set the list box control to be visible only when the text input control text isn't blank, doesn't match the current value in the list item, and doesn't match the selected name in the list box. This is completely unnecessary, but I think it keeps the form cleaner.

[andrewFiveP]

Microsoft has confirmed this is a known issue and it has gone to the product team to resolve.