-
Attached is a sample XML file that can be used to preview the form. Delete the "Primary Repeater Section 2" group and see that the "Repeater Aggregate Stage 3" field does not update.
-
Here is an example template that demonstrates the problem. Enter values into the fields highlighted green, adding as many fields, field groups or primary groups as you like. You'll note that all field values are aggregated into large double eval expressions.
The problem is that the high level double evals do not update when an entire ...
-
Put the hidden field on the form to see the math in action.
Each rule on the FinalStatus field will need the box ticked to not run past the rule if correct. They are 3 separate rules, not 3 conditions attached to one rule.
-
Thank you for these posts, they have been very helpful to address a need for my client. I have this working perfectly in the Preview mode on my desktop, however, when published, the browser form does not update the SP list & provides no errors. Any ideas on why? Thank you in advance.
-
Hilary
THANK YOU!
I tried your suggestion and got the same thing. Acting on a hunch, I added [last()] to both path indicators as follows --> CurrentStateGroup[last()]/CurrentStateText[last()]. In raw XPath it looks like this: ../my:CurrentStateGroup[last()]/my:CurrentStateText[last()]
And - it worked. Such a simple solution to such a vexing ...
-
Attaching a sample with a validation rule that should do this.
-
I'd use user roles, since this sounds like it is not a browser form. More info here: http://office.microsoft.com/en-us/infopath-help/introduction-to-user-roles-HP010165118.aspx
-
I've used this double eval technique but don't see a difference with just merging the account-ids together when promoting the account-id field.
In the sharepoint formlibrary this column is of type text and not of person/group. Is er a possiblity to change that?
-
no one?
Please. Is there any way to resolve my problem?
-