-
I found the problem! Incorrect XPath - there was an "@" in front of the people picker fields that did not belong there. Try attached copy.
-
Thanks so much for posting a follow up!
-
I think when you talk about hiding unused sections, you may not be thinking of repeating sections. The only way to have multiple instances of a repeating group (by the way, the data structure for repeating sections & tables is the exact same in IP - both are bound to repeating groups) without using code is to insert the max number of instances ...
-
Maybe try removing the index ([1]) from the formulas. I just created a test form on one of my SharePoint sites for a list there and this worked as anticipated. It also worked in preview....
-
For the People Picker, try the attached (save the file locally, right click, select design to open in design mode, then preview). Instead of using default values, I added rules to the repeating group. However, this is a SharePoint List form, and I recall some issues with setting people pickers via rules in those - If I remember correctly, it ...
-
Oh my goodness. Glad you solved the mystery! How frustrating. :)
-
I am going to guess there is an issue with Owssvr.dll. If you take a new form, no qRules or code, and add an owssvr.dll data connection, and publish it to the browser, does the data connection query without error? If there is an error, what's in the SharePoint logs?
-
You bet. The default formula for the field bound to the textbox would be:
substring-before(fieldwithdate, "-")
XML stores dates in yyyy-MM-dd format. The date picker or other control may display the date differently, but if you open an XML file saved from your form and look at the date field, it will be yyyy-MM-dd. If it ...
-
I'd be happy to help you - any chance you can attach a copy of your template (or a test template) to a reply under the options tab?
-
If you take a look at the XML, is the AccountId still populated as anticipated, with domain\username?