-
Where have you placed the rules you are talking about for field4? They should probably be placed on the MonthNumber field.
-
XPathNavigator.Clone() doesn't work like you think it does. You need to use AppendChild() first, re-select the newly added node, and then modify it.
-
Can you verify that the form is actually successfully querying the data source where that data is supposed to come from? You can verify this by dragging some of the fields from that data source into your form.
-
You can use this formula to get the location of the XSN that's currently open:
substring-before(substring-after(/processing-instruction()[local-name() = "mso-infoPathSolution"], 'href="'), '"')
would that be enough to help you extract out the information you need?
-
What was the trouble you encountered with Matt's code? Perhaps we can help you sort that out.
-
Unfortunately, InfoPath's built-in support for multi-select list boxes is pretty limited. Doing what you describe will either require code or qRules. I'm attaching an example form that uses qRules to accomplish this behavior. The full version of qRules comes with one hour of free support, which you can use to have us set ...
-
That is strange. I've observed the same behavior just now and it seems like it might be a bug in InfoPath. Luckily, there's hope.
Firstly, I don't think a hyperlink control is the right tool for the job here. Hyperlink controls allow form users to edit the link, but it doesn't sound like you want that. An ...
-
Could you attach an XSN where you've deleted all of the content except for a few of these problem controls?
-
Is the problem occurring on all of the text boxes, or just that one? There's a good chance you can fix the problem by just deleting the text box and recreating it (drag the field from the data source taskpane into the form). Have you given that a try?
-
Most likely, the node has an xsi:nil attribute that needs to be removed before you can set a value to it. Search this forum for xsi:nil, and you should find plenty of help.