The Short Story:
There is an undocumented (as of this writing) limitation to SharePoint 2010’s managed metadata columns: they only allow ~250 entries into one column, for one item. If you exceed this limit, you’ll most likely get this error:
<nativehr>0x81020030</nativehr><nativestack></nativestack>The URL 'SitePages/Test Page.aspx' is invalid. It may refer to a nonexistent file or folder, or refer to a valid file or folder that is not in the current Web.
We haven’t identified a workaround yet, but we opened a ticket with Microsoft to see what they might come up with.
The Long Story:
You may be asking why in the world a user would need to enter more than 250 values into a Managed Metadata column. If so, you’re apparently not alone since Microsoft seems to have thought the same thing.
Well, I’m currently consulting at a retailer where they have a system that publishes information to a portal that associates (employees) in the stores then read. In my experience, this is a common practice in the retail industry. Anyway, my client wants to publish information to specific stores. The solution that the team came up with was to populate the managed metadata term store with our store hierarchy (zones, regions, districts, stores). This gives our store operations group in corporate a great user interface in order to select any part of this hierarchy and target the content.
However, we noticed that when we started pasting in longer lists of stores (which is a common sense requirement by our end users), that SharePoint would give us this error when we clicked save on our item.
Recreating the error
To recreate the error, perform the following steps:
- Create a term store hierarchy with more than 250 choices – I created one with just numbers, using Excel to quickly generate a file that can be imported to the term store
- Create a managed metadata column in a list – it doesn’t matter what type of list it is
- Now, create an item and add more than 250 choices into the managed metadata column
- Save your changes --- BOOM – error!
Solutions / workarounds?
The team is currently looking into workarounds, and all of them require a good bit of coding. At this point, my advice will be to avoid the managed metadata based solution if you’re possibly going to be crossing the 250 values limit.