This Post will discuss in detail about the options you have to set when using a Sharepoint Lookup Field. When you do a create Column in sharepoint you get it as
Lookup (information already on this site) on the Create column page.
To get a better understanding of the concept lets take up a scenario.
Scenario:
We have 2 lists
1) Company Information
2) Contacts
The relationship between then is established by using a Lookup column
“Company” in contacts
These 2 lists are placed on the Default.aspx (Home page) of the Site in the form of DataView web parts.
Refer the image as below:
What is the requirement?
Click on the “Company” Hyperlink It should take you to the DispForm.aspx of
the list item in "Company Information" List.
Click the “Close” Button of the DispForm.aspx it should bring you back to the Default.aspx (Home page) of the Site where we have the 2 DataView Lists.
Here “Company” column is a Lookup (information already on this site) Field.
To achieve the above requirement it’s very important to set its
Additional Column Settings -> In this column value to:
“Title (linked to item)” and not to “Title”. Why??? Refer the reason below.
Reason:
If you set the Additional Column Settings -> In this column value to : “Title”
In a Lookup Column, then the Hyperlink column created will show a &Root Folder=* at the end of the Hyperlink URL. This will make the navigation to go to AllItems.aspx of the “Company Information” List on clicking “Close” button on the DispForm.aspx
If you set the Additional Column Settings -> In this column value to:
“Title (linked to item)”In a Lookup Column, then the Hyperlink column created will not show any such Root Folder parameter. This will make the navigation to go to Default.aspx (Home page) of the Site
on clicking “Close” button on the DispForm.aspx
Refer the Images for a clear understanding.
.JPG)
11 comments:
Only one field has the 'linked to item' associated with it and it is not the column I want! Any way to get around that?
Thank-you so much for this post, I have been fighting this problem (exact same requirement) for weeks!!!! Easy fix worked exactly as you described.
Hi,
someone may help the approach to creating lookup fields in visual studio. here is tutorial with screenshots.
http://sharepoint-anthony.blogspot.com - Lookup field
Good trick..
I always used to wonder about the difference between Title and Title (Linked to Item)..
I have one specific requirement.. I want to make more than one column as 'Linked to Item'. Is this Possible??
for instance, List Company has 4 columns: Title, Owner, Production & ShareValue.
I want to make all of them as 'Linked to item'.
Let me know, if anyone can get around this.
Thanks
chinmay,
by default you can not have multiple link item in list view.
but i think you can add this by programmatically...not sure
we'll check and confirm.
Do you confirm we can only lookup fields/columns like Title, ID, Comment ... and not the columns created for that list?
Thierry,
you can also lookup column created by you. but limitation like you can not lookup a lookup column, multiline text and like that...
Exactly what field types can be used as lookups? And are there any restrictions - e.g. do they have to be unique?
Regards
John
there are some field like people picker, multiline textbox,cannot lookup a lookup column.... and some more of them
we don't have a link handy but there is a MSDN link which lists which type it doesn't support.
Is it possible to use the alternative columns associated with a lookup column as a document field? I.E. I have a Contacts list and I want to use more than just one column within a document as a field. For example, I want to have a comobo-box for the contact full name, and when selected it will change the fields associated with the other columns, such as the home phone and e-mail columns.
Anonymous,
you can do it but with a lot of custom coding
Post a Comment