-
Perhaps what is best for you to do is to use a repeating table with a single column, inwhich you place a section and/or layout table to organize your columns. Then you can have additional rows which you hide until needed which show the subtotals.
-
Souns like you might need to delete the control from the view and then add it back in. Something got messed up somewhere.
-
xsl:sort is not natively supported in InfoPath. When you ''roundtrip'' your form (i.e. bring it into the designer, make a change, and save it again) the xsl:sort tag is either modified or stripped out, making it useless.
The only way around this is to use a Preserve Code Block -- which means that InfoPath will pretty much leave your XSL code ...
-
current() for an expression box will typically be different than current() for a text box (or other control). This is because the context of the expression box is the container (table, section, etc) whereas the context of the text box is itself.
-
I haven't done any specific testing around this, but my initial guess is that you can only send the current view via email. *IF* that is the case, you will need to switch to the correct view, then perform your send.
-
ExecuteAction is somewhat flaky. There's lots of places where it doesn't work. The best way to do this is to manually insert the XML you need into your DOM. You can usually grab the XML from the template.xml file or the sampledata.xml file.
-
Thanks for sharing this with us!
-
You might need to be checking eventObj.Site instead of .Source.
When you get the #text, you can do a selectSingleNode(''..'') to get to the actual node.
-
It is the default behavior for InfoPath to print an underline for drop-down list boxes.
One solution is to create a separate print view which changes any drop-down list box to a text box or to an expression box.
-
Yes. This is really the best approach. Then you can use code to calculate whatever you need to correctly populate your secondary data source field. The expression box just binds to the 2DS field instead.