SHould I use a lookup for my column or choice?


I'm going to create a column to be used in a new project workspace template for issues (and one for risks too). I want to have a column to select the business unit and I think it would work to have a sharepoint list of the business units, which could include a description field and be used for other stuff too.

My questions:

Should I do this and use it as a lookup column? It seems like the benefit would be that I could allow admins to modify the table and if the business structure changes, all they would have to do is change the lookup table.

Can it be used on subsites, or it is constrained to the site where it is created? (Don't really see this as being a problem, but just asking).

Are there any downsides to doing this? It seems pretty intuitive.

If there is a URL of someone out there with an answer to this or a comparison I will accept that as a solution (as long as it fully answers the question and clearly).

Thanks in advance!!!


Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

A site column is restricted to the site only, not the site collection.  The two best ways to do this are

1) Create a list and make the column do a lookup.  This is best especially if you will have frequent changes to the list. The only major downside is that there is now one more list on your site.

2) create a multiple choice column and populated it with the correct options.  This is better for a list that will not be changed often, as it is self-contained, and doesn't require another list "cluttering up" the site.  I believe there is also a minor performance gain, as the column definition contains the possible values and an additional query to another list is not required.  I don't think that would normally be noticeable, however, unless you had a lot of choices in the list.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
mobrien118Author Commented:
Thanks for the input. Good answer.
There is more to this than the two best ways to create the site column.  Potential gotchas are:  a lookup cannot be used as a formula in a calculated field.  A lookup cannot be accessed in "edit in datasheet" mode.  I'm sure there are more; this thread would be a great place to keep track of them as community members find them.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SharePoint

From novice to tech pro — start learning today.