Advertisement

  • SharePoint Filtered Lookup Field

    Whilst working with SharePoint lists/libraries, have you ever wanted to include a lookup field that retrieves data from a column residing in another list/library that's found found in a different site within the same site collection?

    The standard SharePoint lookup field allows you to do all that except the "...different site in the same site collection" bit; all lookups must be within the same site. I've recently published the Filtered Lookup field, a custom SharePoint field that allows you to achieve the "missing" bit.

    I must state, at this point, that there are quite a few good projects and/or free codes out there that provide the cross-site functionality to lookup fields as well, and, just like the Filtered Lookup, some indeed allow you to filter the retrieved data based on defined list views located at the source list/library. However, the Filtered Lookup field also allows you to filter the retrieved data based on dynamic/ad-hoc CAML queries; this implies that you don't need to create a new list view each time you need to retrieve filtered data from source list/library.

    The Filtered Lookup field and its source codes are published for free on codeplex.

    Feedback and comments are, of course, most welcomed.

3 comments:

  1. Anonymous says:

    I tried the control, it is not working with the sharepoint content deployment job. Is there anything that I'm missing?

  1. what this means is that you don't need to make a new record perspective every time you need to recover strained information from resource list.

  1. what this implies is that you don't need to create a new history viewpoint whenever you need to restore damaged details from source record.