-
My biggest recommendation when debugging xpaths that are supposed to work but return null is to put a breakpoint in the debugger and try to run your xpath incrementally, removing pieces from the right until it starts to return something. Then examine the resulting navigator/node/what-have-you in the watch window and try to figure out what is ...
-
The short answer is "no" - the expression box text is not stored in the data and you can only manipulate the data in the forms code.
The long answer is "well, it depends". There are two possible things you can put into an expression box:
- an xpath xpression (as complex as you want)
- plain text
In the first case, you ...
-
You cannot. The display value is a pure view notion and view cannot be accessed by neither rules not scripting.
Your workaround is to define an aux data source based off an XML file where you will type the values for the dropdown. For example, it may look like this:
<data>
<option ...
-
Hey saudak,
to make a textbox read-only, double-click on it, select Display then Conditional Formatting.
Add your condition, then check the read-only box.
Your condition may depend on another field. Now you can set this field either via rules, calculation or code, it's up to you!
This is the only way of dynamically changing the read-only ...
-
Hello saudak,
You cannot manipulate the form controls in the code - the only thing you can access is the XML data. As such , selectSingleNode returns you an XML node, you can only change its value and you can never communicate directly with the control that displays that value. Because of this, there is simply no Enabled property available on the ...
-
InfoPath is pretty picky about web services and only supports Document/Literal style. More on this (including workarounds) here:
http://msdn2.microsoft.com/en-us/library/aa202750(office.11).aspx
-
Hey, you're welcome! I think the reason why these contorsions are needed is because there is some obscure bug with reading the XML directly.
-
This happens because there is no QueryAdapters property...
To access the main query adapter's command, use this:
XDocument.QueryAdapter.Command
To access a secondary adapter's command, use this:
XDocument.DataObjects["Detail"].QueryAdapter.Command
Hope this helps. Also using F1 while editing the code is very helpful, just ...
-
I am not sure why it does not work - have not used the FSO in a while. But maybe you could just use ReadAll() instead of ReadLine() and not worry about while loops...
-
Qu'est-ce que ton bouton fait? Utilises-tu les Règles?