SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I implemented cascading dropdown for City, State and Zip for a site collection. We are housing over 60 site collections and most of the now going through business process development. There is a huge demand for infopath forms with cascade drop down.

Does this mean all of those 60 site collections needs their own list for City, State and zip and maintain their own? This sound cumbersome to me.

Are there better solution as to maintain one set of lists (City, State and Zip) and consume it from one location?

share|improve this question
Which specific version of SharePoint? – Dave Wise Feb 24 '12 at 18:05
I am using SharePoint 2010. – Maria Burton Feb 24 '12 at 20:23
up vote 0 down vote accepted

I think one thing you could use here is the Content Deployment. It's a great way of sending content from one site collection to another.

I have no affiliation with this project, but it works great.
SharePoint Content Deployment Wizard

I think it will serve you great purpose for this :)

share|improve this answer
Good point but that wont help. Thanks – Maria Burton Feb 24 '12 at 21:28

The first place I'd look is at Managed Metadata to see if that would work for you. It allows you to manage that data in once place but have all sites use it

share|improve this answer
Good Point. I wonder if cascade dropdown will work with Managed Metadata as values are kept with it's index. – Maria Burton Feb 24 '12 at 21:28

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.