-
Nothing to do with the view, but everything to do with the XPath. I'm using an absolute reference to the node bound to the radio button instead of a relative reference and that seemed to do the trick.
-
My sample had a super simple schema. Check the default on field68 in the attached file. Be sure to check the edit XPath box in the formula editor, you'll be able to see what I did from there.
-
Use multiple rules and a helper field in a secondary data source XML file. Put this field on the form instead.Submit with your qRules commandCheck the value of the success nodeIf success = true, set helper field message to "Submit succeeded"If success = false, set helper field message to "Submit failed" and include the ...
-
No - views and data are separate. You can use controls bound to the same field in multiple views or in multiple places in the same view. Did you check "Edit XPath" in the formula editor so you could see the entire XPath? If you need a hand attach your form under the options tab - I should have a few minutes to help you out later ...
-
Your problem is here:
xdXDocument:get-DOM()/my:myFields/my:Time/my:Employee
That will always return the first Employee.
Since this rule is on Employee, you should be able to use current() in place of that.
xdXDocument:GetDOM("Employee Records")/dfs:myFields/dfs:dataFields/d:SharePointListItem_RW/d:EmployeeID[../d:Title = ...
-
I'm not sure I understand the question. I see you have some other qRules commands in the form - those will set success to true when they succeed. You shouldn't have to clear the success node to submit.
-
Okay - if things are getting set to the value of the first row, something is off with your filter. Can you paste in the full XPath of the expression you are using?
-
When you say "set incorrectly" could you please tell me what "incorrectly" means here? Is the value being set to anything? To the wrong value? The first value? Some random value? :)
-
If you look at your working form, you'll see in the QdabraRules data source, on the finishedLoading node, a rule that sets the useWebServices attribute to true. Add that rule to your form that is not working. That will force the form to use web services for the submit (like it does in preview) instead of using the SharePoint Object ...
-
Hi - when you say don't set the values correctly, what do you mean? Are the values not getting set at all? Are they getting set to something unexpected?