SharePoint 2007, 2010, 2013 – Filtered Lookup Field

You may also like...

15 Responses

  1. THANK YOU! This worked for me!!!

  2. damii says:

    http://www.azu.mn/?p=239
    The SharePoint Lookup Plus Field type is a “super” lookup field type that brings added capabilities that implementers found lacking in out of the box SharePoint 2013 Lookup fields:

    Cascading fields (“master-details”)
    Cross-site lookups
    Filtered lookups (filter lookup by views & CAML)

    check it

  3. Jason Cooper says:

    Sounds great – filtering on the Lookup Source!
    Do you know of a way to filter from the Destination?

    Example:
    List A – is "Apple", "Banana", "Cherry"
    List B has a lookup reference to A
    I can ensure List B enforces unique values (so no two items in B will be "Cherry")
    However, if A is over 30 pieces of fruit, it may be confusing – because they'll have to scroll quite a bit.
    Thus: how would I filter the lookup values so that, when adding a new item to B, I only see unused items?
    Everything I've read says it can't be done without code or a third-party solution.
    If you have any ideas, please let me know!

  4. Fanaticit says:

    Thank-you so much. This works so well.

  5. Paul Beck says:

    Nice post! This saves me having to customise, I reference your post on my blog. http://blog.sharepointsite.co.uk/2014/07/sharepoint-2013-ootb-lookup-list.html

    thanks paul

  6. damii says:

    This comment has been removed by a blog administrator.

  7. April Dunnam says:

    Thanks for the reference Paul! Glad this worked for you 🙂

  8. Rita says:

    Hi,

    I'm using the following formula:
    =IF([Estado do Planeamento]="Em Elaboração", [Nome],"")

    and the following error is ocurring:
    The formula contains a syntax error or is not supported.

    I think the formula it's ok, and i don't know what's happening 🙁

    Thanks,

    Rita

  9. Nabeel Salie says:

    Hi Rita.

    Try and replace the "," (comma) with ";" (semi-colon)

    I've read that site regional settings can affect the syntax used in SP

  10. Rod Dreyer says:

    Very nice and thanks for the great tip April 🙂

  11. Keith Hudson says:

    NOTE this will not work if the child list (the list you're looking up on) has more items than the list view threshold.

  12. Anonymous says:

    A beautifully simple solution. Thank you.

  13. Hello. this works fine, "more less", the problem is that when you change the Task to "Not active" then in the list you have been using the calculated column the value disappear so you lost this information,

  14. Hello, may you solve this issue?

  15. Jason, I am looking for the same thing. Did you ever find a solution? I don't see a response here and calculated IF statements won't filter out multi choice options…

Leave a Reply

Your email address will not be published.