HAving trouble with a lap top, it will not let me connect to the internet tryed with a router from
at@t and also connected the dsl cable to to laptop and still not working.
View Complete Post
I have an InfoPath form with two Submit Connections. One of them is a regular submit connection to a SharePoint Document Library. The other is a submit connection to the UpdateListItems web Service.
I have one button using rules that submits the forms fields to the Document Library. Some of those fields have data validation rules like entry must be four digits, and field cannot be blank.
The other submit button uses rules to submit an XML template to the UpdateListItems Template. My problem is that even though this second button does not have the first submit connection as an action, the form will still check all of the forms fields to see
if they violate the validation rules before it will submit to the Web Service.
How do I tell InfoPath to ignore the validation rules when I only want to submit to the Web Service? I want the user to be able to enter data into the XML template fields and submit to the Web Service, even if some of the rest of the fields are blank. Right
now if any of the other fields fail validation it prevents submittal to the web service even if the fields that failed validation are not being submitted to the web service.
Thanks for any advice that can be offered,
HI, does anyone have any ideas...
I have created a BDC application in VS 2010, and installed it on the sharepoint 2010 server and I am at a loss to explain the behaviour.
I create an external list using my application as the data source. When I open the sharepoint site and access the list from a browser on the sharepoint server itself, everything works fine.
However, when I access the sharepoint site from a different machine, my BDC application reports a failure to open the SQL Server connection (Error 40 - could not open connection to SQL Server).
However, if I access the list from the server (which works), and then access the list from another machine, the remote machine now works, and will work for a short while before reverting to error 40. I am assuming that this is because the connection has
been opened when I accessed the list on the server, and then the remote session is picking up the open connection in the pool, because if I then wait a couple of minutes for the connection to time out and try accessing the list again from a remote machine
the connection then fails again.
It does not matter who I am logged in as (I have tried being a normal user on the server and an administrator on the remote machine, and visa versa), but the behaviour is consistent. Also, my connection string in my BDC application contains a