Friday, July 1, 2011

SharePoint Lookup Fields: Did you know that....

This one time I was trying to figure out why every time I created a SharePoint lookup field, be it programmatically or via the UI in SharePoint 2010 and 2007, which looks up to another SharePoint list field, it would always have a value "none" in it when in use. So now I really wanted to eliminate that value...


After much thought and research, it came to make sense that the reason was because the lookup field was not a required field, and if set to be a required field, the "none" value would disappear, and there I had it. Basically if I really wanted my users to choose only from the options being looked-up, then I might as well set it as a required field.



I hope this saves some time for 'you' who wanted to use some javascripts to hide it :)

ciao...

1 comment:

Nick Kharchenko said...

Hello, I'm Nick from MAPILab - the vendor of software solutions for Microsoft SharePoint.

We are looking for SharePoint evangelists who are also involved in blogging or who are authors at SharePoint-related sites.

We released recently new workflow solution: HarePoint Workflow Extensions for SharePoint 2010: http://www.harepoint.com/Products/HarePointWorkflowExtensions/Default.aspx

Our purpose is generating reviews for this new solution and their professional point of view. Please, note that we don't look for any king of advertising or 'paid' review - but we are very interested to offer you the evaluation of the software as a subject for your post/article. And certainly, we will be glad to place links to the best reviews in the product homepage.

You are welcome to contact me back with any additional questions.


Nick Kharchenko
MAPILab Ltd.