-
I'm using Office 365 instead of an on-prem server, but can't replicate this. I have a list with a lot of different column types - I added two Y/N fields. I customized in InfoPath, and my checkboxes worked as anticipated.
-
You can find a code sample here: http://www.bizsupportonline.net/infopath2007/programmatically-select-all-items-multi-select-list-box.htm
-
No, there really isn't. Multi-selects in InfoPath add nodes to the XML - the multi-select is bound to a repeating field, and when you click the checkbox, it adds a new instance of the repeating field. When you deselect, it removes it. You can test this by looking at the XML in a text editor. Unfortunately, InfoPath doesn't have any ...
-
And your new form used the same list & columns?
-
Yah, I'd try that next and see if the form correctly updates those fields on submit.
-
Ok - so this is interesting: "Test Form with q rules injected and button using q-rules to generate guid works correctly when published." That makes it sound like there is something specific with the original form. Is there anything of interest in the SharePoint log files when that form errors?
-
Hey, thanks for posting the solution to the issue - that info may help someone else down the road!
-
That's really odd. Form looks fine. Maybe try refreshing the fields (see screenshot)? There isn't any workflow on the list that might be changing these?
-
Ok, I can probably help with that too. When you submit the form, all values are updated except the fields associated w/ the checkboxes?
-
Did you have a chance to try a new, blank qRules form published to a library? I'm at a loss here - I'd assumed the form with code would also throw an error. Does the GUID get populated in preview in the form with code?