People picker control not always writing to data source list

[OneWinPlease]

My app is running mostly fine, but sometimes the people picker control for one of the fields doesn’t write to the SharePoint list. Users say they DID enter a name, but it doesn’t stick on the back end. This people picker column has an Items property using a Choices formula. (The field in the SharePoint list is a people/groups column.) See screen shots below.  Any ideas? A colleague mentioned maybe creating a variable for the OnChange property of my people control, but I don't quite understand how to do that. (Especially when I have a varFormData set at the start of the app.)

[BCBuizer]

HI @OneWinPlease ,

Could it be the users typed in a name, but then did not select an option? If no options are selected, nothing will be saved.

From personal experience: be sceptical of what users say in these scenarios, ask them to show what they are doing and try building in validation, such as a disabled submit button if nothing has been selected for mandatory fields.

[OneWinPlease]

@BCBuizer  - thanks, but the submit button is disabled if nothing is in that field. It also won't accept a start/backspace blank, or a partially typed name. (I am one of the users who tested this and found it wasn't always working. )

[BCBuizer]

Hi @OneWinPlease ,

Can you then please share:

•  What data source you are using
• What is the type of the column that is having the issues
• The Items property of DataCardValue1
• The DisplayMode property of the submit button

[OneWinPlease]

@BCBuizer  -

• data source is SharePoint list. 
• Column type is a People column.
• DataCardValue1 Items property is :  Choices([@'New Service Request List'].'2nd contact')
  
• Display Mode property of submit button:
  
  If(

      (CountRows(DataCardValue55.Attachments) = 0 && DataCardValue10.Selected.Value = "Yes"|| CountRows(DataCardValue55.Attachments) = 0 && DataCardValue14.Selected.Value = "Refund Exception")  || IsBlank(DataCardValue1.Selected),

      DisplayMode.Disabled,

      DisplayMode.Edit

  )

  
  
  

[BCBuizer]

Hi @OneWinPlease ,

Although I can't replicate the issue, I'm aware that sometimes people report these type of issues when using comboboxes. The fix that is usually applied you can find below:

If(
	(
		CountRows(DataCardValue55.Attachments) = 0 &&
		( DataCardValue10.Selected.Value = "Yes" || DataCardValue14.Selected.Value = "Refund Exception")
	)  || 
	IsBlank(DataCardValue1.Selected.DisplayName) ||
	IsEmpty(DataCardValue1.SelectedItems.DisplayName),
    DisplayMode.Disabled,
    DisplayMode.Edit
)

This formula can be applied to the DisplayMode property of the Submit button.

[OneWinPlease]

@BCBuizer  - thanks. Can you tell me what is it about this new submit button formula that fixes the writing-to-list error? Just trying to understand since my brain doesn't think well in formula-speak.

Edited to say: I am testing your suggestion out but it didn't work, unfortunately. The Power App Monitor is saying that datacardvalue during the session is "successful" but it's not writing to the sharepoint list. Maybe it's a  bug in the list. .... Second edit:  I decided to put a duplicate version of the Backup Contact datacard in the form. Then I submitted the form and it was successful. So I deleted the 'bad' datacard and went ng with the newer one.  I did notice now that the Items property for the combo box is slightly different, with OData info now added to the column name. (This change also broke 3 connected automated flows, and I had to remove the Apply to Each action in them before the flows would work again. So... once more, it does seem buggy. Or if it makes sense, I don't have the depth of knowledge to understand why.  At any rate, here it is a few hours later and the problem has cropped up again. 

Choices([@'New Service Request List'].OData__x0032_ndcontact)

[BCBuizer]

Hi @OneWinPlease ,

Did you check your Dataverse table to see if anything in there happened that may cause the issue? To me it sounds like, although hard to believe, the column names have changed. 

[OneWinPlease]

@BCBuizer  - I created that column just before I made the power app and have not changed the name. Investigating why this might be happening, I discovered that OData can be used with SharePoint. (I don't normally work in this area, so it's all foreign to me.)  Why they are connected in my case is unknown. Our central IT department deploys back-end settings across the organization that I have no knowledge of, but could be influencing this.  

My SharePoint list was copied and adapted from a large, 35-column list that I think was originally exported from InfoPath years ago, by people who no longer work here. Maybe something weird happened with the export, or whomever finalized the original SharePoint list set things up in a way none of us can figure out. My column was brand new, though. I've asked my IT unit to investigate but so far, no progress.  

(Another example of weirdness: I recently noticed the Locations Choice column in SharePoint was set to checkboxes, which allows multi-selections. Since we don't want multiple Locations, I changed it to single choice.  But then the app started inconsistently writing to that list field. (The app's combobox was set to NOT allow multiples.)  So I had to go into the SP list, turn checkboxes (multiples) back on, and writing to the list became consistent. Clearly, changing settings long after your list and app are operating together can cause all kinds of instability. I haven't changed anything with that Backup contact field, but am making a lot of changes and additions to the app even though it's live. Building the airplane while we are flying it.)

[BCBuizer]

Hi @OneWinPlease ,

Always fun to get the responsibility over a solution with a lot of history. Hopefully your IT unit can help clarify things.