Skip to main content

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...

Labels:

Comments

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.
July 15, 2011 at 12:05 AM
Post a Comment

Popular posts from this blog

Zambia's first Helpdesk System on SharePoint

For my 25th birthday today 3rd March, 2009, allow me to present to you another first of its kind in Zambia. Yes we have done it again, having been Project manager, I present to you Zambia's first Helpdesk System which Masialeti and I have developed on Microsoft Office SharePoint Server 2007. The system also implements SharePoint designer workflows, Infopath forms, SharePoint document library and sends email notifications to the relevant personnel. When a user logs in a call, the user automatically receives a mail from the system, telling them that their call has been received and is being attended to, IT section will also receive a notification and the helpdesk manager will assign the call to the right IT guy who will also automatically receive a mail notification from the system. When the call is resolved, the user again automatically gets notified by the system with a mail giving them description of the problem they logged and also how it has been resolved. The user also has an ...
7 comments
Read more

Zambia's first K2 BlackPoint roll-out

Reporting to you live from Code|Influence... My colleague and I have been managing our organization's SharePoint infrastructure for some time now and we have just rolled out the first K2 BlackPoint in the country, intended mostly for SharePoint workflow developments.
8 comments
Read more

How to implement a SharePoint "Change Management Process"

Not so much from the technical point of view, SharePoint Change Management is the process of monitoring and controlling changes within a SharePoint project. By managing the implementation of change, you can: • Reduce the impact of changes to the SharePoint project • Identify new issues and risks as a result of changes raised • Ensure that changes do not affect the SharePoint project's ability to achieve its desired objectives • Control the cost of change within the SharePoint project Change Management is comprised of the following processes: Step 1: Identify Change: The first step in the change process is to identify the need for change. Any team member can suggest a change to the SharePoint project, if he or she believes it is needed to keep the SharePoint project producing deliverables to the customer's specified requirements. After identifying a need for change, the team member records relevant information on a Change Request Form (commonly called a CRF), describing the chan...
2 comments
Read more