Hi there, folks!
You may recall this blog post from a while back by Sean Fiene -- it's a great write-up on how to approach cascading look-ups in Nintex Forms using lookup columns in SharePoint. A summary is: for each set of data you want to create - you need to make a new SharePoint list. It makes sense!
But, I, personally, don't like having so many lists. I'd rather just have one place for myself and my clients to update. I wanted to find a new way - and, I have. I'd like to share that with you today so you can poke holes in it, or try it for yourselves.
Let's look at a 1-list set-up for 4 different cascaded sets of metadata.
|Tier 1||Unique 1||Tier 2||Unique 2||Tier 3||Unique 3||Tier 4|
Let me explain:
An issue we have right now is that if we simply use a List Lookup and pull back Tier 1, we will get hella duplication of Animal and Vegetable. Perhaps some day we will have a "remove duplicates" functionality, but right now - we don't.
This is where views save the day.
For me, this works really well. How about you? What are your thoughts?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.