-
yes to both. You establish the data connection using the designer. Then in script, you can set the parameters and call the Method function as necessary. The last page of the data connection wizard has a check box that you can clear in order to prevent the WS from being called onload.
-
I have not experienced this, and I always expected that the Outlook requirement as a client-side requirement, but I'm wondering if it is complaining about the server that SP is installed on--whether that server is expected to have Outlook installed and set as the default client... something to look into anyway.
-
If you are using a Web Service Data Connection, then you should not require full trust. If you are trying to write all the script needed to communicate directly with the Web sercice, then you might need full trust (not sure).
-
Thanks for jumping in and helping Matt!!
-
Which are you using right now? InfoPath 2003 or 2007?
If you are using 2007, are you using the IP03 OM or the IP07 OM? Because that makes a difference.
Getting the ''index value lies outside of the valid range'' error indicates that there is not a second form open (i.e. XDocuments(0) is always valid, but XDocuments(1) is invalid because there is ...
-
The schema you showed above looks like your main DOM schema... what does the schema returned from your Web service look like? The example I gave above was just to demonstrate that the Web service schema must have some kind of association between the vendor product and a particular vendor.
-
You will probably need to do this with code or rules... Set the query field before querying.
-
What is the data structure returned by the Web service? What it should be returning (at a minimum) is something like this (though the following is strictly an illustration and will not represent your actual structure returned):
<VendorProducts>
<VendorProduct vendor=''Vendor1'' product=''Product1''/>
<VendorProduct ...
-
In your code you have:
var objXDoc = Application.XDocuments(0);
var ddValue = objXDoc.DOM.selectSingleNode(''//my:bezeichnungderveranstaltung'').text;
XDocument.DOM.selectSingleNode(''//my:schulung'').text = ddValue;
Know that Application.XDocuments(0) is the same thing as XDocument. 0 is always the current form. If you want to get the other ...
-
You might be trying to map in FormA namespaces into FormB or the other way around. Make sure that when you set the selectionnamespaces, that you are setting the correct set of namespaces from the correct form.