InfoPath Dev

I've created an InfoPath 2010 form  and one of my fields is set as a PERSON/GROUP PICKER. RIGHT-CLICK on the PEOPLE PICKER box and select PROPERTIES. Then on the GENERAL tab,  check the box next to ALLOW MULTIPLE SELECTIONS. Click OK and publish form to site. Then when I go to the SP site and try to add a new item to my list, I try to choose more than one person in this field but the error I receive is: The form cannot be submitted because of an error. The form cannot be submitted.
The user does not exist or is not unique.An entry has been added to the Windows event log of the server.Log ID:5567 Correlation ID:617b1783-98bc-4fec-b4c2-1764ae045d30

Then when I click the LIST tab at the top and choose LIST SETTINGS, I select the corresponding column and check its properties. In the "Additional Column Settings" field, the "ALLOW MULTIPLE SELECTIONS" is set to NO. Now clearly in InfoPath this option is set to allow. When I change this setting in the SP site and save it, and then try to add a new list item, it tells me that this column conflicts with the InfoPath form setting.

 I am confused as to why this happens and am growing to despise SP greatly.

 

 

Hi Selmore,

I'm not sure if you are using a list form or not, but neither list forms nor library forms support repeating items.

Here's what you should do.

1. Create a full fledged InfoPath form template from scratch (not a list form)
2. Add a repeating group to your form and add a non-repeating Person field underneath it.
3. Add a data connection to your site that looks up the user from UserProfileService or use the PeoplePicker and set rules to copy values over to the current item
4. Layout your form to make it look good.
5. Publish it to SharePoint form library
6. Set up a mapping from the repeating person group to a separate list.
7. Create a dashboard form that will show you multiple people per form via an InfoPath Web Part on your site.

I know there are quite a few steps and this will probably take you an hour or so to do it. But, it is the preferred design pattern when dealing with parent-child repeating structures. The hierarchical structure of XML is very powerful and you can map it onto the flat SharePoint list and library structures and you can then create reports and dashboards that mash-up the data to make powerful user interfaces.

We have recently done several webinars on dashboards and have samples that show this. Check out Qdabra's channel on YouTube. There were two videos done in the last month on dashboards. The techniques covered in those webinars are described on this site and we can send you the samples if you contact Support <at> Qdabra <dot> com.

Good luck!

Thanks for the tips, Pat. However, what I am trying to do is a bit different. I have a field where I can choose a userid from our AD database. What I need is to be able to enter more than one entry in this field. The field is set for multiple entries in SP Designer but when I try to enter more than one user in the SP site itself, I get the error mentioned above.

I had a similar issue today, but I'm not using SP designer. I'm using only SP and Infopath to customise my list. From my experience, you will need to: - go to LIST SETTINGS in sharepoint and tick "YES" for the option "Allow multiple selections" - save the list - open it in infopath - you'll get an alert the list was modified and it has to be updated in infopath (or something similar) - click Yes - republish your list from Infopath Hope it helps!

~sigh~   Thank you!!!