InfoPath Dev

This one is weird... I have a "person/group" column in SharePoint 2010 that allows selection of multiple people and is set to optional. When I use the Customize Form button in SharePoint to create an InfoPath input form, InfoPath wants to make that field required. I can uncheck the required box in the field's properties or the same box in the control's property list and save either of them, but on reopening those, the box is checked again. Then when I publish the form, the field definition in SharePoint is updated to required. I deleted and recreated the input form, the list, the site collection, and the site column, sometimes with the same name, sometimes a different name, but always with the same result, an unwanted requirement on that field. I have not yet tried deleting the SharePoint site... When I have created the list with no required fields other than the title, InfoPath still checks the box on this field as required, but doesn't seem to update SharePoint to match. The moment I go and set the requirements on the various fields, I get the problem. There is another people picker in the list (single selection only) that when it is set to optional, it stays optional. (but of course, that one I really want to be required... ) Oddly when the form displays, and in the InfoPath fields list, there is no red star next to this field name. But I still have to fill it in in order to save the form. My best guess is that there is a bug that having one people picker that is required and a second that optionally allows multiple selections is causing the behavior. Does anyone out there know of any workarounds or solutions? Thanks! Richard

That is really odd - I'm sorry to tell you this, because I'm sure it isn't terribly helpful, but I just tried this and it didn't happen on my ShP 2010 site & list - so whatever is going wrong seems like it may be specific to your environment.....

Sigh... Thanks any how. I just tried creating a brand new site and it forced it required again...

I think I have this figured out as to under what conditions this happens. • Create a custom SharePoint list. • Add a People/Group Column, set it for multiple selections. • Add any (or no) other columns desired. • Create a form in InfoPath and publish it. • Make ANY change to the list that involves adding or deleting columns or modifying column properties. • Modify the InfoPath form. When it opens you will get the message: “One or more fields in the SharePoint list have changed. Do you want InfoPath to update the set of available fields?...” • Say Yes • The People/Group column is now set to required (property dialog has the “Cannot be blank” box checked.) • If the form is published, this required setting is propagated back to SharePoint. The only way out of this that I have found is to use SharePoint list settings, Form Settings, “Use the default SharePoint form” and check the “Delete the InfoPath Form from the server”. This “solution” is obviously a pain in the *** for complex forms. Any ideas now how to get around InfoPath’s bug? Thanks! Richard

I have a problem very similar to this and I just can't find any info on it. I started InfoPath form editing from within SharePoint (2010) list menu, put validation on some of the fields. After I publish back the form they all appear as required (red starred) in the browser and I don't know why. I have checked that the corresponding checkboxes on the ribbon bar and/or field properties window are unticked. These fields appear as non-required in the field list (on the right by default). So these fields are optional on both list and gui level. Even when I check form in Infopath's own builtin form tester it looks OK it's just the published web form is faulty. At the same time the validations I've made are working on the web form so there must be no problem with publishing, it's just they seem required despite they aren't. I simply have no idea what the hell is happening.

I've been noticing this issue a lot on my more complex SharePoint listforms. We are on SP2010 and IP2010.

The issue seems to manifest itself on a publish but we may not notice it for a while. I've had a few theories as to the course, but it never seems to repeat under the same variables.

I don't think I line up quite with rckurschner's experience. I've seen it happen on ists without people and group columns. I think there is some relationship with inconsistently modifying columns in both InfoPath and SharePoint, rather than just at one end - I am sure you all know that there are often reasons why you must make a change in one app or the other so you see the problem.

Most recently our 'title' column was remarked as mandatory - interesting given its an OOTB on every SharePoint list.

I've not had to delete the form in any of these cases. I am able to untick 'cannot be blank' and republish successfully. I take it that it's not that simple for you guys?

 No solution, but wanted to chime in that there definitely is a problem!

I have this same issue!  It seems like no one has quite resolved his post, so I am hoping it will be picked up again.

I can keep the error from occuring by deleting the field in both infopath and on the SP list, and republishing.  Then I make all other changes required and publish.  Then I recreate the field/column in SP, add the people picker to the form (ensuring that it is still for multiple selections and not a required field), and publish, then readd all of the data that was deleted by editing the field.  But this workaround is a total pain!

For what it's worth, I ran into the same issue.  All my people picker fields were set to allow multiple entries at the request of the user.  I changed them to a single entry on the list and which fixed the problem.  But I have no idea how to avoid this with multiple entries activated.