I have an InfoPath 2010 form that I publish through the Administrator Approval path to the Sharepoint 2007 site. There are approximately 15 fields that are promoted to be usable by Sharepoint. However, there are six fields that don't work.
The strange thing is that the XPath in Sharepoint is /my:CoASubmission/my:Main_Form/..... whereas the XPath in my InfoPath form (main data source) is /my:main/my:SAGE....
Now here is the situation...
12 fields with the SP XPath of /my:CoASubmission/my:Main_Form work fine with newly created documents, even though the .xml doesn't have that path.
3 fields with the SP XPath of /my:CoASubmission/my:Main_Form don't work, even though they are in the same group in the IP2010 form as the 12 that do work.
3 new fields have the /my:main/my:SAGE/.... xpath specified in Sharepoint 2007 as identified by Sharepoint Manager, but they do not work.
Manually updating the XPath in Sharepoint 2007 does not help any of the six broken fields.
Working means that I can edit the value in the InfoPath form (web browser form), and the value updates in Sharepoint when I save and close the form.
Not Working means that the value displayed in Sharepoint is blank, and nothing I do can make it a different value.
I am able to have InfoPath create a new field in Sharepoint on the property promotion tab, and it will work properly, but I am unable to fix the six non-working fields.
Here is my process for updating my form
- Publish the form in InfoPath to the server using the Adminstrator Approval button (bottom one)
- Upload the Form
- Wait for it to finish upgrading
- Deactivate the form from the site collection
- Activate the form from the site collection
- Test
Does anyone have any ideas, or are we going to need to pull out the axe and wipe out the whole content type and rebuild it from scratch? I am unable to remove the six non-working fields from Sharepoint because they are linked to the Content Type.