InfoPath Dev

 I've set up a test sub site in SharePoint 2010 to get familiar with the Rest web data service. I'm having problems right out of the box when trying to create a secondary data connection to a list. I select the Rest webservice option, enter the following url:

http://servername/site/subsite/subsite2/_vti_bin/ListData.svc/Test II?$select=Email

 The endgame here is for me to add a drop down control to the primary data source that gives me all the rows of data from the email column in the secondary data source. The two error messages are as follows:

1.  Could not open http://servername/site/subsite/subsite2/_vti_bin/ListData.svc/Test II?$select=Email
2. infopath cannot open the xml document: http://servername/site/subsite/subsite2/_vti_bin/ListData.svc/Test II?$select=Email. Not enough storage is available to process this command

I'm using IFS if that makes a difference. This is a web enabled form. Thanks in advance!

Does your URL work in the browser? Is it http or https? What version of IE do you have installed? I ask because if I recall correctly there was an issue w/ https and a particular version of IE that returned this error in IP when creating the connection.

 Hi Hilary,

I'm getting this error when trying to create the data connection in design mode in the template.xsn. I'm using the "Customize Form" link in the SharePoint UI. I'm using IE9. Not sure what you mean by "Does your url work in the browser?"

 If you open your web browser and paste the URL:

http://servername/site/subsite/subsite2/_vti_bin/ListData.svc/Test II?$select=Email

Into the address bar and tab out or enter, what happens?

I get the message: Webpage cannot be found.

If I strip off everything from_vti_bin on, it brings me back to the site default page. Looks valid to me   :(

Try just accessing the ListData.svc: http://servername/site/subsite/subsite2/_vti_bin/ListData.svc

ADO.NET data services need to be installed: http://scottcurrier.wordpress.com/2009/12/16/rest-and-sharepoint-2010-quick-start-guide/

 Thank you Hilary, I'll look into this.

Update:

I got a successful REST connection!! The web service needs the internal field name when selecting, filtering etc. Thanks again for pointing me in the right direction. this problem has been plaguing us for a bit.