-
Does field X have to be Yes | No? Can it be true | false?
Here's a sample that uses a default value for this - just checks field1 through field3 and makes sure they are all the value of the option button labeled Yes.
-
I'd think that this might work:
count(preceding-sibling::my:gpRepeating) > 2
As a condition for your formatting - I'd add an expression box inside the gpRepeating section and use the formula editor to get the syntax right for this: count(preceding-sibling::my:gpRepeating)
Then for your condition, change the first box to ...
-
So, when the person opens the list item to edit it - they don't get the same form?
-
Sorry about that - we need a (much) better error message here and I've opened a case on that. I actually think when the installer fails it is what leaves a hung IP process about - I'm hoping we can check to see if IP is running and warn the user to quit instead. :)
-
Close all instances of InfoPath. Open Task Manager and under processes, see if INFOPATH.EXE is running for any user - if it is, end the process (alternately, restart the machine). Then try again.
-
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/
-
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 think you instead need to look at the data connection and change the URL there: http://msdn.microsoft.com/EN-US/library/microsoft.office.infopath.webserviceconnection.aspx might help.
-
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.
-
I'm really not sure what could be causing the issue - it isn't one I've run into before. If it were me, I'd try narrowing the issue down:Narrow the issue down to user vs. machine - have users that are having failures try on a machine where other users have succeed - if the user succeeds on a different machine, it seems likely the ...