https://www.infopathdev.com:443/forums/43.aspx enCommunityServer 2007 SP3 (Build: 31118.962)https://www.infopathdev.com:443/forums/thread/117182.aspxTue, 05 Sep 2017 19:49:48 GMT033a2e2d-04e2-4a9d-be01-a4634161eefd:117182GMUDuckman0https://www.infopathdev.com:443/forums/thread/117182.aspxhttps://www.infopathdev.com:443/forums/commentrss.aspx?SectionID=43&PostID=117182I do write code, but since I'm working on a Gov't SharePoint site and computer, I don't have access to any of the code side of things. I just recommended to the client we split out the people picker (since we know it will never be more than two people). Luckily they were cool with doing that. Why does Microsoft make such a cool control, but the make it practically impossible to work with :-(https://www.infopathdev.com:443/forums/thread/117169.aspxFri, 01 Sep 2017 21:38:17 GMT033a2e2d-04e2-4a9d-be01-a4634161eefd:117169Hilary Stoupa0https://www.infopathdev.com:443/forums/thread/117169.aspxhttps://www.infopathdev.com:443/forums/commentrss.aspx?SectionID=43&PostID=117169If you fill out the form manually with multiple users selected in the same people picker, and open the XML with a text editor, you'll see that the pc:Person node actually repeats (see attached screenshot), and I don't think there is going to be any way (outside of code) to get this to behave the way you need it to.... I mean, if you know how many there might be, you might be able to come up with some way to set it with rules - you'd have to include your max # of pc:Person nodes by default, and manually modify the manifest to indicate which one you were setting, and then use substring-before formulas to parse out each ID.... but that would get mighty messy. You write code at all? :)https://www.infopathdev.com:443/forums/thread/117163.aspxFri, 01 Sep 2017 16:08:45 GMT033a2e2d-04e2-4a9d-be01-a4634161eefd:117163GMUDuckman0https://www.infopathdev.com:443/forums/thread/117163.aspxhttps://www.infopathdev.com:443/forums/commentrss.aspx?SectionID=43&PostID=117163So here is the situation - I am using a InfoPath form library in SharePoint in conjunction with promoted fields. There are 4 views one for each role type. The submission view has a cascading dropdown for course and module. After the user selects the course and module (and the rest of the information on the submission view) I have a workflow that is setup to grab the AccountIDs the module content owners from a sharepoint list called modules. The workflow then sets the promoted field to the user AccountID semi-colon delimited so it ends up looking like this: "[domain]\user1;[domain]\user2". On the infopath form in the other views I have set on form load rule to set the people picker in the AccountID = PromotedField. The problem I am running into is the people picker gives me an error that says "No exact match was found. Click the item(s) that did not resolve for more options". When I click into the field, there appears to be a empty line at the top of the field. If I remove that, the names resolve just fine. I feel like I'm missing something here. If there is just one name in the promoted field it all works fine, but once their are multiple names, it stops working. Anyone have insight into the multiple person picker field? SharePoint 2010 InfoPath 2010 This is on a government sharepoint farm so I can't share the infopath file. Any insight would be amazing! Thanks!