-
Where is the xsl:value-of in the code? Is it part of a repeating table? What type of node is it trying to pass in? You can also cast your parameters as you pass them in (if that helps)...
xdExtension:CalculateTotal(number(.))
But this is only useful if you are passing in a value.
Greg Collins [InfoPath MVP]
-
I just ran a quick test (I figured there were only a few possibilities).
I tried IXMLDOMDocument, IXMLDOMNode, and then finally IXMLDOMNodeList which worked.
So the answer to you question is that the data type you are passing in to your code is an IXMLDOMNodeList.
Greg Collins [InfoPath MVP]
-
Hmm. So this was a form that was upgraded from V1 to SP1, right? Well, once you have an SP1 form, no V1 InfoPath user can use it anymore... they need SP1.
''IF'' SP1 uses tns: as the namespace of choice when building from scratch, consider making a copy of your form, doing a global search and replace (at least for this one data connection in ...
-
Secondary data source connections to databases are readonly.
You should be able to write the code to directly communicate with the database, and then set up the Command property to do whatever functionality is required (provided you have adequate permissions on the database).
Greg Collins [InfoPath MVP]
-
Yes, this is a much complained about restriction between InfoPath and SQl/Access. To get around this you need to either use a Web service that will take your fields and place them in the appropriate database columns, or you will need to write code in your form to do so.
There are resources online that can be searched for that should give more ...
-
Yes, secondary data sources are second class citizens in this version of InfoPath.
I played around a little bit and found no way to turn off spell checking for a secondary data source field. Sorry.
Greg Collins [InfoPath MVP]
-
Great! Glad to hear you got it working!
Greg Collins [InfoPath MVP]
-
From what I understand about emailing forms... the location of the form template remains intact... in your case the form template was being looked for in:
C:\Documents and Settings\dwheeler\Local Settings\Application Data\Microsoft\InfoPath\Designer\''blahblahblah''\manifest.xsf
Just dropping the manifest in there doesn't do any good because the ...
-
I'm not sure I follow what you are trying to do. What I understood your original request to be was to find out how to access EmployeeID via selectSingleNode -- which it sounds like you are now able to do.
What I don't understand is why you are trying to convert it to an IXMLDOMDocument2.
Therefore... please rephrase what it is you are trying to ...
-
If I take your XML code from the previous post and use it to create ''test.xml'', then create a new blank form (JScript), and import that as a secondary data source, I am able to access the value of EmployeeID with no problem...
var domFoo = XDocument.GetDOM(''test'');
domFoo.setProperty(''SelectionNamespaces'', ...