-
InfoPath will not allow you to change the contents of the data source in a Changing event. Please try adding that code to AcademicPerformance's Changed event.
-
If you have a good command of C# or VB coding, you can create and use any kind of dialog boxes that you like, but InfoPath does not provide anything like what you're describing without custom code.
-
Precisely what settings are you using for the Data Validation? Please try setting it to something like [dropdownField equals 'yes'] AND [compulsoryField is blank]
-
Please inspect the attached XSN, which should be a simple mock-up of what you described, though all in one view. The logic in this form is contained in:The rule on the CurrentFYSpend fieldThe default values on YearlyCost, RunningTotal, and Remaining (Note that the "Recalculate this value" box is unchecked for YearlyCost)
-
I have seen this error before and to the best of my experience it indicates exactly what it says: that you are not connected to the domain that your active directory LDAP string indicates. Are you in fact connected to a domain with active directory, and if so, could you verify the LDAP string in your web.config file?
-
The formula is: count(full path to listbox1's field[. = full path to listbox 2's field])so if my first listbox is bound to field2 and my second listbox is field4, the formula would be: count(/my:myFields/my:group1/my:field2[. = /my:myFields/my:group1/my:field4])I'll let you experiment around with any rules/default values for ...
-
If it's simply for display purposes (i.e. you're not storing the intersected list somewhere in the data source), then this is possible without code.
Make a repeating table/section bound to the same field as listbox 1 and set the conditional formatting:Expression: not(path to field for listbox 2[. = current()])
Behavior: hide ...
-
If you're able to open DAT, that's a good sign. I'm not quite sure what document types you're expecting to see. Have you created any yet?
-
I just tried this for myself, and found it's a little tricky because of the way multi-select list boxes add and remove nodes on the fly. The solution I found requires a combination of a rule and a default value.
First, change the expression in your rule to: count(../my:Type_of_Policy_Referred)(I'm assuming my: is the ...
-
Neat. You might also try doing that from a rule on the list box's field, so that users don't have to press a button to update the number.