Re: Problem with promoting fields to a form library

Patrick Halstead — Tue, 15 Nov 2011 03:12:07 GMT

Are the new fields in a different namespace? If so, that could be the issue.

In general, using property “demotion” is not a best practice because InfoPath uses XML data types and SharePoint uses SQL and for things like dates, it just won’t work to map back.

Hope this helps!

Problem with promoting fields to a form library

Chinosts — Mon, 14 Nov 2011 08:37:04 GMT

Hi guys.. I developed a rather large and complex InfoPath form (IPFS) a while ago that is used to track work in progress for a particular company. It was originally developed for MOSS 2007 form services but has since been migrated to a SP2010 Enterprise server and appears to be working nicely. I have, however, recently noticed a problem. When I promote a field from the form to the form library as a editible in Datasheet view field, the field has an error when I try and make a change in datasheet view. The follow is the error that appears -

The document is missing xml elements or attributes where the changes would be saved.

The wierd thing is that fields that were promoted a while back work ok and edit ok in Datasheet view and its only new fields that I promote produce this error when I try to change the value of the field in datasheet view. The field is of type Decimal Double (Ive also tried integers and text fields as a test)

Anyone have any ideas how I can fix this issue?

SharePoint Integration

Re: Problem with promoting fields to a form library

Problem with promoting fields to a form library