-
I should add that unless you have the fields in your schema, you are not going to be able to add them at runtime. The only way to do this is to have the fields in your schema, but not the nodes in your XML... and then add the nodes to your XML at runtime. You need them in your schema or you cannot build them into your form template at design time ...
-
Then what you are needing to do is to make sure that your form schema is set up to have those fields... and then you will need to write code behind your button to add in the XML DOM nodes for those fields.
-
Good luck. If that doesn't fix it, respond back. Maybe someone else here can help out.
-
Not sure how you got into that state... but the XPath is invalid, which is why you are getting the error.
..[1]/my:GroupAction[1]/@my:Progress
You can't have the filter "[1]" on "..". These kind of filters only work on valid node names.
".." only goes up the tree [1] anyway... so a valid XPath, from what ...
-
You would use a rule on the drop-down list that sets the AdminName. It gets the name from the secondary DOM that pulls its data from your SP list. To get the right name, you need to filter the list based on ManagerID = the selected value in the manager field.
You can use the InfoPath UI to do all of this, but pseudo-code-wise it would look ...
-
Why not just submit it to the document library that your form template is tied to? The other applications can access the forms from there.
-
The failure is happening in the ParseQName() method. QName stands for Qualified Name. Are you doing anything in code, like adding new nodes into your DOM? If so, then check to make sure that they are naming the nodes valid names.
-
Does it matter which column you remove? Will removing any do (first, middle, last)?
I've not done much work with Access in InfoPath, but I would not imagine such a limit existing.
-
You will need to place your text boxes in a section. The section has conditional formatting to hide if some field value is not set to true, for example. The button, when clicked, has a rule that sets that field value to true, causing the section to be displayed.
-
You probably don't want "objError.Node.xml"... you are probably looking for "objError.Node.nodeName" or "objError.Node.baseName".