InfoPath Dev

 Hi,

Does any one has worked with Sharepoint in built Web services and Infopath. I was trying to get some MOSS list data directly to my Infopath form (without code behind), I came across 2-3 web services which can be used to achieve this.

http://<MOSS Server Name>/_vti_bin/DspSts.asmx?WSDL

 http://<MOSS Server Name>/_vti_bin/Lists.asmx?WSDL

When i create a Secondary data source to connect to Sharepoint list using these Web services I got some options to fill in values. Did any one has worked with this before

Hi Sourav,

Yes, we need to fill the values while connecting to shrepoint list. For example, if we take a data connection using http://<MOSS Server Name>/sitename/_vti_bin/Lists.asmx?WSDL for GETLSTS method, we have to give the library name. Depending on the method we have to give the input values.

Hi, 

To get the data from SharePoint list you have two options.

1. Take a secondary data connection to SharePoint list. But here the limitation is all the data in the list will come into the form. You cannot query specific data. You can filter the results after wards.

2. Use GetListItems web method in 'http://<MOSS Server Name>/_vti_bin/Lists.asmx?WSDL' web service. By using this method you can query specific data from list. But it requires some code. To know how to connect to GetListItems web method, go through this blog

http://www.infopathdev.com/blogs/agni/archive/2006/05/15/Query-for-Items-in-SharePoint-Form-Library-Using-GetListItems-Web-Method.aspx

 Hi Swathip,

Thanks for the reply. I have already tried the stuff you are talking about. Have you ever tried this without writing code. I mean using the data connection wizard, when we specify any builtin Moss Web service it asks for some parameters. Even I specify those values it gives me some XML root error.

Do you some examples or links where I can get to know how to use these webservices in WEB Enabled forms without code.

It is not possible to use the Lists.asmx directly in InfoPath via a web service data adapter because the schema is too complex for InfoPath to handle. There is a SharePoint adapter type, but it has its own problems that prevent it from being particularly useful.

The two choices are to write code in the form or to use a proxy web service that runs on the server, calls Lists.asmx on the caller's behalf, and prepares a cleaner xml result that InfoPath could consume.

Qdabra be adding such a proxy in the next version of DBXL.