InfoPath Dev

I'm having an issue where my submit routine, using c#, to a SharePoint web service does not work as expected. The item in a Document Library is created but none of the columns are populated.

All the mappings are correct as far as the fields/columns/batch go;
[Client]] -> [Server]
InfoPath Form [Template.xml 'OptionA' = InfoPath Field 'OptionA'] ->
Lists.asmx [Document Library column 'OptionA' = Template.xml 'OptionA']

I am using managed code, is the problem that my form is not Fully Trusted and that I need to create a certificate?

I notice InfoPath uses WebDAV, not sure if it also uses SSL. Is that the problem? How do I use WebDAV in InfoPath?

There must be some simple explaination for why my Document Library items are created without being populated with the form data!

Is there a reason why you do not use the built in submit to SP via a data connection in InfoPath? You can call the submit function with C# code.  Often people over complicate it when the functionality is already built in.

You should check and make sure that the fields you want as columns are promoted in form properties.  Fields are not by default and you would need to specify these. That is what Sharepoint looks for when creating columns when the form is published.

Due to the need of a specific feature. When these types of documents are submitted, there will be fourt types. Each denoted by a specific unique identifier (within the DocType column), then each of the type has it's own unique ID (within the DocID column); a progressive series of values. What the form has to do is as the form is submitted capture the previous ID of the last entered document of that type, and increment it and append it to the submitting document as its DocID. That has to be done during the submit routine.

If I were to capture that ID and increment it when the form loads, then someone else who also opens the document to submit a new copy will end up duplicating the ID, 'poisoning' the DocID's. I need to capture and increment the value the moment the form is submitted just incase two of the same DocType's are being created at the same time.

Yes, this is a common issue with SharePoint, which I always have used submit to SQL to overcome, since a unique and sequential ID is created with each record insert. 

I have seen many attempts at using Sharepoint by itself but I am not sure how many have been successful or whether having an occaisional duplicate is that big a deal.

Good Luck.