SOLVED

Relationships between two lookup type fields

Brass Contributor

I need create a content type with two Lookup type fields.

I dont mind if the first field is a Choice type or Lookup type. But the second one I believe must be a Lookup field).
Both fields must be related.
After select a value for the first one (for example a Continent), the second one must show only items filtered by the previous choice (for example, the countries for the continent selected). How can I do that?

I remember in a previous sharepoint version (2010 Foundation..., I'm not sure) I did it, but now I'm missing a field type in recent sharepoint versions. Thank you!

6 Replies
Cascade Lookups has not been there in any SharePoint version ^-^ You need to implement it by doing some code on the client side...is this SPO? If yes, then you have two scenarios here:
(1) For classic lists/document libraries you can have this functionality by means of JavaScript code injected in some way (JSLINK is one of the possibilities you have) in the client side of your list / document libraries forms
(2) For modern SPO lists / document libraries you have the SPFx Extensions that are currently in preview

Hi @Juan Carlos González Martín,

I forgot   to tag my question. I'm working with on-premise 2016...  I suposse that I'll have to write code because there is no an OOTB solution, won't I?

Thanks

Correct! And in this case, go for JSLINK!!
best response confirmed by María José Pedreira (Brass Contributor)
Solution

you may have been using the SPServices http://spservices.codeplex.com/ that were created by @Marc Anderson 

Hi @Dean Gross,

SpServices is great! Thank you for the idea. I followed this link (https://www.codeproject.com/Tips/758909/Two-Level-Cascading-Drop-Down-in-SharePoint-using) and for a list runs well.

 


Thank you!

1 best response

Accepted Solutions
best response confirmed by María José Pedreira (Brass Contributor)
Solution

you may have been using the SPServices http://spservices.codeplex.com/ that were created by @Marc Anderson 

View solution in original post