InfoPath Dev

I have taken over the maintenance of an InfoPath 2007 (non-browser enabled) form which works with SharePoint 2007. When I examine the Form library on the UAT site collection, I find that some of the promoted fields are appearing more than once .

 What could have caused this? I will be re-building the site collection anyways with a fresh restore from production. But, I was just curious if anybody on this forum also might have faced such an issue.

thanks,

Saurabh

I've seen this when a form is published to more than one library - so if you have a template from production, it will have specific GUIDs in the manifest.xsf for the library columns. If it then gets published to another library, those GUIDs would change (unique to the library columns). Publishing once more to the original library would then cause duplicate columns.

If you save the form as source files and look at the manifest.xsf, you can find the promoted properties - xsf2:listPropertiesExtension has the SharePoint GUIDs and xsf:listProperties has the original fields with their GUIDs that are used in the listPropertiesExtension node.

Makes sense. Thank you Stoupa. That makes me wonder how I would accomplish this scenario using IP 2007 and SP 2007:

1)FormA_v0 has been running on production for a while. This has about 200 promoted properties.

 2)Some minor changes have now been made (no new properties) and tried out on an UAT site and acceptance obtained from the end users. Consider this new version as FormA_v1

To make a release, if I now publish FormA_v1 to PROD then , as you say, we will end up with duplicate columns. This is definitely a problem. So, what are my options?

Option 1) Should I download FormA_v0 from PROD and manually re-do all the changes and then re-publish to PROD?

OR

Option 2) Manually edit the manifest.xsf file of FormA_v1 in an editor and  copy the xsf2:listPropertiesExtension section from PROD's FormA_v0 and then re-publish?

Thanks again,

Saurabh

I would take option 2, myself. I'd probably verify my process in a test library or two first, so I was comfortable doing this with my production form / library.