-
In that case, using ../../Review[1]/Reviewer should probably do the trick, but you may be missing a prefix on Review or Reviewer, or both (like z:Review, or dfs:Review, etc).
-
Could you attach a screenshot of your data source and explain a little more clearly what you want to do?
Do you want the Reviewer field to always default to the value of the Reviewer field in the first row, or the value in the previous row?
-
To answer your questions:
1. You can use qRules' Insert command to insert rows into a repeating section using rules. Then you can turn off the "Allow users to insert/delete rows" option in the repeating section.
2. Unbound controls are essentially useless. If you don't want the comment input field ...
-
Ok, thanks. So I'm guessing that Code (Are the letter code and the code description both in this field?) is in an expression box.
Please try placing the following conditional formatting on that expression box:(Conditional formatting expression) @Code = preceding-sibling::d:v_AllEmpsBlueBook/@Code
(Action) Hide this ...
-
Could you show us a screenshot of your data source as a point of reference? There should be a way to do this with conditional formatting.
-
thisXDocument is a feature of the 2003 InfoPath object model and does not exist in the realm of the 2007 object model. You're free to use the 2003 object model within InfoPath 2007, but you have to choose one or the other.
The 2007 object model is much friendlier to standard CLR features, and you're free to create your own ...
-
I would expect that you should be able to have unique values in the dropdown boxes without making GrpService recursive. Could you try and see what happens if you delete the "child" GrpService group, leaving only the top-level GrpService, and preview the form? I don't have access to your web services, so I can't ...
-
Thank you. What you have in your form is a recursive group (a group that contains references to itself, potentially infinitely), and it seems that for some reason InfoPath will not allow rules to be added to fields in recursive groups. I don't know of a simple way around this, but from looking at your form, I can't see ...
-
InfoPath's save function only saves data in the main data source. For anything else, you will either need to set up the form to re-query the data when it is opened and get it to the state it had before, or copy the data into your main data source, where it can be saved.
If you want to try copying data from a secondary data source ...
-
I don't think that simply making fields reference fields is enough to cause this problem. If possible, could you describe an exact sequence of steps that can reproduce this problem? Alternatively, could you attach a copy of an XSN file where this problem is occurring? That would make it easiest to troubleshoot.