-
The most sensible approach here would be to use a repeating structure instead of individual fields. Please give the attached form a whirl.
-
Are you using it in a rule, or in a default value formula?
-
Hello Jason,
Where are you using that formula? If you already have a PreliminaryLineAndGradeTotalHours field, perhaps it would make more sense to just sum that. Is there a reason you're not doing that?
-
Where are you using that formula. Is it in a rule on the dropdown, or is it the formula in a calculated value box?
If it's the former, try this:
xdXDocument:GetDOM("ExpenseClaimsCostCentre")/dfs:myFields/dfs:dataFields/dfs:ExpenseClaimsCostCentre/@AccountName[../@ID = current()]
If it's the latter, try ...
-
It requires some manual changes to the form's source, but it can be done:
http://www.infopathdev.com/blogs/greg/archive/2005/06/08/Create-a-Picture-Button.aspx
-
I don't generally advocate using code when you don't understand how it works, but this thread has a completely codeless square root implementation. Once it finishes, you can copy the Result value to Field1, and Result * 3 to Field2.
http://www.infopathdev.com/forums/p/21041/72904.aspx#72904
-
So to be clear, do you want to validate the table Q rows against the table P rows based on position (i.e. match row 1 against row 1, etc.), or based on some other common value? Will tables O, P, and Q always have the same number of rows?
-
If you're not experienced with code (and even if you are), it's best to steer clear of using custom code in InfoPath forms, lest you wind up with a maintenance nightmare.
qRules was created precisely for situations like these, and its SortTable command can have you sorting your table within minutes.
-
What does the condition you're using look like? I think the one you should use would look like this:value1 is not equal to datasourcevalue1
AND
value1 is not equal to datasourcevalue2
AND
value1 is not equal to datasourcevalue3
-
Ok, so what is the full condition under which you would like the control to be unhidden?