-
Temo que yo no entienda el problema muy bien, pero no debe hacer el filtro como "LookUp = Valor elegido en DropDown 1," como en este formulario?
-
InfoPath will not allow the dropdown box to be populated with aggregate values. They will need to be present in a field somewhere. Where is the secondary data source coming from? Is there any way it could be modified to have a "dummy" field where the combined value could be evaluated and stored?
-
What is the data type of the fields that are doing this? If they are numerical, there might be some condition under which this would happen. Are you using any special technique to add rows to the table, or just the built-in functionality?
-
It sounds like some rule somewhere is changing the list of available values when you click the office name, or perhaps a rule is being triggered and setting your Office Name field to "false." You can use the Rule Inspector to help you track down the problem, or if you don't mind sharing it, you can attach the form to this ...
-
This is entirely possible in InfoPath. In the ComboBox's properties, you can specify which field is the Display field, and which is the Value field. This means that when an item is selected, the bound field will take on the corresponding "Value" value. Once you have that, you can use some rules and filtered XPath to ...
-
Unless you are using the 2003 OM, the usual MessageBox should do the trick, and should not require full trust.
-
To avoid a full trust form, you should use InfoPath's APIs to use the form's data connections to access webservices, make queries, etc. If you try to call webservices or make SQL queries directly from code, you can run into a full trust situation.
-
Please give this form a try.
-
Sorry, that should have been
xdXDocument:GetDOM("test")/phrases/phrase[@value = current()/dfs:dataFields/d:RATABLE8D/@REASONCODE]
-
Are you saying that you selected "contains" in the middle dropdown box? If so, you should be selecting "is greater than" and then just entering 255 in the third box.