Form (Combobox) broken after field in datasource changes to allow for multiple values.

[hjaf]

Issue:

A people/person column in a DataSource (SharePoint list) was changed to allow for multiple people instead of just one, the change was done after the powerapps form was created. It was expected that, to make the form also allow for multiple people, the "SelectMultiple" parameter on the combobox must be set to true along with the "Update" parameter specifying the combobox changed from "Selected" to "SelectedItems".  These changes does not solve the error : "The property expects Record values, but this rule produces incompatible Table values".

Re-adding the field to the form still produces the error. However, creating a new form works just fine, the form may, or may not, be complex so creation of a new form is not an acceptable solution.

Speculation:

Some magic going on in the background upon form creation e.g. a property on the form that is statically set upon creation or hidden in the editor.

Is there a reliable way to overcome this issue? Is there some attribute I have missed?
If this is known issue where can I find an existing bug/issue thread that I can add some weight to?

Reproduce:

1. SharePoint: Create list with a person column that allows for 1 person to be selected. 

2. PowerApps: Create a form for the SharePoint list created in step 1, and add the input-field corresponding to the person column.

4. SharePoint: Change the list column to allow for multiple people to be selected.

[RandyHayes]

@hjaf 

Typically when you change a column in the underlying datasource for a form, you will need to delete the datacard from the form and then add it back.  In some cases, depending on the change, you will also need to remove your DataSource and then add it back.

Unfortunately, the Forms do not refresh their structure when the data source is changed.

[hjaf]

I see, i had to remove both the connector and re-add the field. 

It would easy to fix in this way for the most part, but it is a bit disconcerting that such changes to the backend may not always be an easy fix, especially when there is no obvious way to fix it. This is obviously some parameter being hidden or not yet implemented as configurable in the editor. Do you know of any suggestions or bug notifications regarding this? I'd like to give a vote to in that case 🙂 

[RandyHayes]

@hjaf 

Yes, I feel that particular pain quite often.  Many of my apps I need to not only design the app, but in most cases I need to design the data source structures.  So, there are often times where I need to change the data source and then go through the steps to get PowerApps to recognize it.

I will say that, for me personally, I rarely use the EditForms in PowerApps.  Most of my apps are custom designed without them.  So, it's fairly rare that I run into that issue.  But, I still do.

I'm not sure if there is a particular idea posted in regard to that.  You might want to check the idea board and search for something like it, or, if not there, post one.  I do believe that over time, the designer will become more robust and will provide something that solves that.  I only say that because, PowerApps is designed to be a no-code easily used platform.  The more complexities that one "needs to know" (such as removing and refreshing data sources) the farther away from that design if becomes.  So, being that this is a young product, it will have to have such improvements to meet that goal.