-
Okay, here is a sample that I think has the outcome you need - check it out & let me know if you need help w/ the correct XPaths for your form. :)
-
Hey, Gwen - can you send your form my way so I can take a look?
-
Hey, that's great news! Glad that fixed it.
-
In your repeating table, where you currently have your text boxes bound to the fields with the defaults, put a calculated value instead. For the XPath for the calculated value, use the formula editor to select the secondary data source & add the same filtering. XPath will look something like this (for example): ...
-
I don't see anything in the form - as you said, there aren't any rules or other defaults that use these values. So - what happens if instead of having defaults in these fields, you just use an expression box to display the info from the secondary data source? Do you still get an error with that approach?
-
Which button causes the issue?
-
So - when users open an existing XML, it is from this SharePoint Document Library, where it is saved to? I would probably look into using the web services for Check In / Check Out - if you aren't on Office 365. I think those are blocked even in Filler. I have an old blog post about this for Browser forms, but I know we've used a ...
-
It isn't in the query fields because it is a complex type, I believe. It is odd - if you select Created By or Modified By (which are also People), you can query. But if you create a connection to a task list (for example) and select Assigned To, you can't! I'd probably just add another column to the list for the account id (or email, ...
-
List forms are limited to the types available when you create a new column in a list. Regular forms have greater schema flexibility - however, there are still a few differences between browser & filler forms in what types of actions are available to you - I haven't checked control compatibility between browser & filler in a while, but ...
-
I'd be happy to take a look at your form, see if I can see something. If it were my form, I'd try to repro the issue in a test form - does it persist if the form doesn't have code (or qRules)?