Web Services

Re: SOAP/XML Error

Jimmy — Tue, 10 May 2011 13:37:58 GMT

The likely issue is that you are passing a blank value into a numeric or object parameter and this is causing the issue. The options you have are:

Pass the entire XML to the web service as a single parameter, and process it in the web service.
Change all your parameter types to string, and handle them individually in the web service.
Make sure that all of your fields have default values and validation to ensure they have the right type of data when they are submitted.

At Qdabra, we're keenly aware of InfoPath's gaps, and we designed DBXL specifically to take the headache out of this very scenario. You don't need to to write any code if you're using DBXL, and it will save you loads of time. I strongly encourage giving it a try.

Re: SOAP/XML Error

TobyHosterman — Mon, 09 May 2011 15:06:15 GMT

I've got a large infopath 2010 filler form (started with the generic blank form template) with about 250 fields, and I need to pull this data into a SQL Server table. There are too many fields to pull the data into "published fields" in a sharepoint list then pull into SQL via access. So, for my first time ever, I'm trying to submit the form to a web service, which then provides the fields as parameters to a stored procedure that does the table insert.

I tried using the SQL Database form template, but I've got some varchar(max) fields in my table, and that template won't allow for submissions to sql db when varchar(max) fields are involved.

With so many fields, they simply won't all be populated all the time, so null values are possible in the form data. I saw a post from 2005 (http://kjellsj.blogspot.com/2005/04/submitting-xsiniltrue-values-from.html) that indicated that with .NET 1.1 SOAP web services, you cannot have null values, and that post recommended writing custom code in the form, in the web service/stored procedure to put dummy data into any null-valued fields for the purpose of the web service submission then strip the dummy data out before it's written to the table. I'm hoping to avod all that somehow. I am unfamiliar with writing code to handle XML...

I saw references to Qdabra's products, but I'm hoping to avoid the cost and complexities of involving additional products in the solution.

If the null-value issue is really my problem, I'm surprised that there's not a simpler way of using web services to submit form data. Seems like a big flaw in the solution, like using InfoPath is amazingly simple as long as you don't try sumitting to a webservice, which requires expertise in writing code to directly handle XML.

Any help you can provide would be much appreciated.

Re: SOAP/XML Error

Jimmy — Sat, 07 May 2011 05:51:13 GMT

This error could happen for a number of reasons. What are the steps leading up to the error in your case?

Re: SOAP/XML Error

TobyHosterman — Fri, 06 May 2011 16:29:04 GMT

I'm seeing this same error. What did you do to resolve it for yourself?

Re: SOAP/XML Error

cef424 — Thu, 27 May 2010 17:33:45 GMT

Disregard... figured it out.

SOAP/XML Error

cef424 — Wed, 26 May 2010 13:40:26 GMT

Ok, several things...

Using InfoPath 2003 and while setting up my data connection for parameters on a repeating table it doesn't seem to keep them after I save?
Then while I am trying to test the form I am getting this error:

The SOAP response indicates that an error occurred: Server was unable to read request. ---> There is an error in XML document (1, 675). ---> Input string was not in a correct format.

Carrie.