-
If d:TimeSheetDetail is the repeating field/group, then I have a feeling you should use:
var iField = eventObj.Source.selectSingleNode("@In1");
and so on.
-
This appears to be the case with browser enabled forms. If your form is going to be browser enabled, you may need to come up with another way of adding rows to the repeating section. The method in this post is a bit trickier, but may work for your particular situation.
CurrentView.SelectNodes() is for changing the nodes that are ...
-
At the moment SharePoint is the only way to publish web-enabled forms (forms that run in a browser), if that's what you're asking.
If the people using your forms will be using them within InfoPath there are a few alternatives.
For simple solutions, you can just specify the address where you want the form to be accessed when you ...
-
Glad you worked it out. Just since you asked, this is the code to add a row in C#:
CurrentView.ExecuteAction(ActionType.XCollectionInsert, "group2_1");
-
Typically in XML, it is illegal for a field designated as a numerical value in the schema to not have a value. There is no such thing as a "blank" number. InfoPath manages to work around this by using a little trick in the schema:
<xsd:element name="field1" nillable="true" ...
-
If it's only to display the data (and not to modify it), you should be able to use filtering on the repeating sections (see the sections' properties dialog) to accomplish this. Is that a viable option?
-
My mistake, sorry. For a button it's eventObj.Source, not eventObj.Site, but looking at your code it looks like you have the wrong path anyway. The path should be relative to the repeating node, so:
printername = eventObj.Source.SelectSingleNode("my:Multiple_Printer_Name").text
not
printername = ...
-
Great to hear that. I wish you the best of luck with your form.
-
I'm guessing it would be:
For Each queryResultRow As XPathNavigator In queryDataFields.Select("*[my:Machine_Name = 'LRD1CTX16']")
Though you may need a different namespace prefix (if that doesn't work try replacing my: with dfs:
XML node selection uses a language called XPath, not SQL. I recommend reading up on ...
-
Ok, there are a few problems here.
The main problem is that in each interation of the loop, you need to store the relevant values in fields in the form to which the data connection is hooked up (in the data connection's settings). Right now, you're just temporarily storing the references to the nodes in variables that never get ...