J
Josiah Smith
When submitting a form to a SharePoint 2003 from a form designed and filled
out in InfoPath 2007, a filename containing a comma (either set with xpath
code, or typed into a text field) will be submitted to SharePoint 2003 with
an underscore replacing the comma. This will not happen when saving to a
local path, only when submitting.
Is this something that was designed in purposefully for some unknown reason,
or is this something that will be fixed?
We are in a doctor's office and have >3000 patient records saved with a
comma in the filename, and our current fix is to only have the secrataries
use InfoPath 2003 when submitting. Are there any other known work-arounds?
Would using the XDocument.SaveAs(argument) give us the same results?
out in InfoPath 2007, a filename containing a comma (either set with xpath
code, or typed into a text field) will be submitted to SharePoint 2003 with
an underscore replacing the comma. This will not happen when saving to a
local path, only when submitting.
Is this something that was designed in purposefully for some unknown reason,
or is this something that will be fixed?
We are in a doctor's office and have >3000 patient records saved with a
comma in the filename, and our current fix is to only have the secrataries
use InfoPath 2003 when submitting. Are there any other known work-arounds?
Would using the XDocument.SaveAs(argument) give us the same results?