General

Re: InfoPath 2010 Form Submit to SharePoint 2010 library error "The filename, directory name, or volume label syntax is incorrect."

jvazquez — Mon, 09 Dec 2019 16:16:33 GMT

thanks so much for posting your workaround. I ran into this issue today and was able to save myself alot of work using your method.

Re: InfoPath 2010 Form Submit to SharePoint 2010 library error "The filename, directory name, or volume label syntax is incorrect."

ln1000000 — Fri, 25 Apr 2014 19:43:54 GMT

Figured it out. Opened the library in explorer, cut the original file, pasted it locally, then cut pasted back to library explorer. Each file is now labelled as new and can be edited and posted back.

Only idea my boss and I had was that the xml schema didn’t update when I published the new template, seems to be accurate when comparing the new file with the old file. Hope this helps others!

InfoPath 2010 Form Submit to SharePoint 2010 library error "The filename, directory name, or volume label syntax is incorrect."

ln1000000 — Fri, 25 Apr 2014 19:24:39 GMT

Hello,

I've looked everywhere for a solution, including this site, to my error with no success so I figured I'd make a new one in order to bump this issue.

I'm getting an error when editing existing InfoPath 2010 forms from my sharepoint library. New forms are not affected, and I can edit said new form without this error. What's even more confusing is most older forms work fine, it's only the 2013 forms that prevent editing.

I'm using a custom submit button which has nothing special, it just submits using my defined sharepoint data connection in a rule set. The rule is literally Submit using data connection, no prompt.
Allow overwrite is checked on the data connection options.

Details: Some rules were not applied

InfoPath cannot submit the form.
An error occurred while the form was being submitted.
The form cannot be submitted to the following location: <removed>
The filename, directory name, or volume label syntax is incorrect.

Nothing has changed in my form template except I populate hidden fields with parsed data from another visible field when the button is clicked in a separate rule.

Thanks,

Brian H.