-
The controls in the view reflect the current state of the data, and allow the user to interact with it. So if two of the radio buttons have the same value then they will both show as selected when the field takes that value. I'm fairly sure there's no way to prevent that behavior and in some ways it wouldn't make sense (for example, ...
-
That looks correct.
One alternative solution to this problem that I have used sometimes is to create a new calculated value box, copy/paste the expression into it, and then delete the old one. That tends to work as well.
-
You should be able to do this by checking for the existence of a following sibling. last() would be unreliable here. Please try this:Condition: following-sibling::my:ProductItem
Formatting: Hide button
-
For the second one, you need to open up the Formula Editor and enter it there, not in the Value: box. Is that where you're entering it?
Note that you can also troubleshoot by dragging the qRules Error field into your form and seeing what it says after you execute a command.
-
Ah, sorry, you need to remove the / after preceding-sibling:: (I imagine InfoPath displayed some sort of error about that?). Fixed it now.
-
You just need to delete the slashes before the predicates (the parts in [square brackets]):Delete /xpath=/dfs:myFields/dfs:dataFields/d:ExpensesMain/d:ExpenseItems[@ReceiptNumber = 0] (no concat() needed here)
concat("Delete /xpath=/dfs:myFields/dfs:dataFields/d:ExpensesMain/d:ExpenseItems[", ...
-
You can manually enter a formula by selecting "The expression" from the left dropdown in the condition builder, but if you're going to be applying these complex formatting rules to lots and lots of controls, that's all the more reason not to be copying a manually-constructed expression from place to place.
I can understand ...
-
It is possible to define more complex expressions by entering your own manually, but I like to avoid that when possible because you lose the built-in checking that comes with the InfoPath designer. It is possible to define your condition in terms of disabling the button, using the following rules:
Rule 1: Disable if Status = ...
-
This is fairly easy to accomplish with a custom validation rule. You can simply add one with the following condition:Employee is existing employee (however you define this in your form) AND
AssetID is blankWhen you do this, you should remove the "Field is required" property in the field's settings
-
InfoPath doesn't provide any built-in way to calculate date differences in a straightforward manner. There is a somewhat convoluted way to do it codelessly:
http://alecpojidaev.wordpress.com/2008/12/30/infopath-codeless-programming-walkthrough-2/
The other option is a code-based approach. qRules provides a way to make use of code-only ...