InfoPath Property Promotion to SharePoint Form Libraries

[Chris]

Hello,
I'm using InfoPath and SharePoint 2007 RTM and may have found a limitation
on the number of Property Promotions allowed for a certian number of form
libraries.
I was not successful in finding this limitation documented anywhere or a
patch or update of Office that addressed this InfoPath issue.

The following lists the number of Property Promotions that I found allowable
(does not fail to update the Content Type when publishing in InfoPath) to be
specified on an InfoPath form template when publishing it as a Content Type
to a Site Collection. The forms libraries described below are those that
specify the InfoPath Content Type as their default:

• 17 Property Promotions publish up to 3 form libraries
• 13 Property Promotions publish up to 4 forms libraries
• 10 Property Promotions publish up to 5 forms libraries
• 9 Property Promotions publish up to 6 forms libraries
• 7 Property Promotions publish up to 7 forms libraries
• 5 Property Promotions publish up to 8 forms libraries
• 4 Property Promotions publish up to 11 forms libraries
• 3 Property Promotions publish up to 13 forms libraries
• 2 Property Promotions publish up to 16 forms libraries
• 1 Property Promotions publish up to at least 20 forms libraries

From my testing, this limitation did not seem to be due to the size of the
form (it’s only about 32KB) or the number of data connections or unused data
sources.
I currently have 17 Property Promotions required and 18 Fom Libraries that
use this as their default content type. To work around, I’m going to make 8
Content Types that are exactly the same (for usage in different libraries).

My questions: has anyone else experienced this issue? Is this a known
limitation?

TIA

 

[Chris]

Update to this post....
The issue was due to the manner in which the Virtual Machine that the
SharePoint environment was running on was built. It was created with a
non-supported (by Microsoft) configuration when attempting to reproduce the
environment for X number of development environments. In this unsupported
configuration, SharePoint appears to function as expected for most
functionality, but manifests strange errors like the one originally posted
here.
After building a new environment from scratch, this issue did not appear
again. I've confirmed by reproducing the issue on other VM's built the same
way as mine was before I rebuilt it.

Hope this helps someone.

 

[S.Y.M. Wong-A-Ton]

Great info! Thanks, Chris, for reporting back to us. Are you also able to be
more specific about what this 'non-supported configuration' is/was? That
might be useful too to know. Thanks!