I've proven my cascading dropdown works when it's item lists being used, but i would like to have cascading dropdowns in a task list and it does not seem to work. I'm thinking it has something to do with the content type but don't know what about it is getting in the way. i have a setup just like the one exampled here: Three-Tier Cascading Drop Downs: Do Go Chasing Waterfalls! except that the master list is a task list instead. still with lookups.
I'm currently just focused on getting one cascade to work so the third tier has no bearing now.
i've tried making all the lists used task lists thinking it was a content type miscompare type issue. no progress.
i've tried making a content type that had both item and task columns. no progress.
Please forgive me if this is a silly fix, i'm still pretty green working in sharepoint and nintex in general.
Solved! Go to Solution.
Hi Cassy, of course, though there's no workflow. Hope this is clear, let me know if i make things easier to see or whatever, i've never posted something like this in a forum. Thanks for any thoughts/help you can provide!
Thank You very much for your help!
in step 9, where field should be name of the list field to filter by. not its reference.
field reference (item property) is evaluated to current item field's value, so your filter likely tries to filter by non existing list field.
Thank you and good catch on that, but that's not it. i tried both "Detector" and the "main model version lookup" while toying with things and happen to leave it on the wrong one. but to make sure i understand, you mean to set up the control setting for the Model/Version control like this:
if that's so, the result is still
I've tried this same setup using item lists. it worked. then i changed each item list to contain and default to the task list content type (CT), made sure to add the columns to the task content type. then it stopped working. i switch things back to item CT's for all lists and move columns back to that CT, but then it still doesn't work; as if changing them to "task" CT ruins the whole cascading system somehow.
Any next thoughts? i appreciate your efforts! thanks again.
no, I meant field name typed in as simple string like: "main model version lookup" (without quotes).
but filter definition requires you identify list fields by their internal names.
since you have spaces in field name, sharepoint converts each space into "_x0020_" string in internal names, and if resulting string is longer then defined limit, it as well shorten it.
so, your field's internal name might look like "main_x0020_model_x0020_version" and you have to use it this way.
check in the field settings what' the exact internal name.
alright. i got the internal name (Model%5Fx002f%5FVersion%5Fx0020%5FList) from the column URL and used that, no change. i did the same for the detector (as noted above, it should be detector in the Where field*) and still no change. i should maybe note that the red text in those screenshots are from the "insert reference" button to the right of the field. they worked fine when the setup used item lists instead of task lists. so it still seems to me to be a content type matter somehow.
thanks again. any additional thoughts/suggestions appreciated ")
1. replace %5F with underscore => Model_x002f_Version_x0020_List
2. 0x2F is slash character, do you really have it used in field name? I wouldn't recommend it, it could only cause problems
i should maybe note that the red text in those screenshots are from the "insert reference" button to the right of the field
yes, I noticed that.
they worked fine when the setup used item lists instead of task lists
I can't believe that, you would compare apples and oranges
so as you pointed out before, the Where field should be detector.
it's internal name is Detector, no spaces or anything else. i tried Model_x002f_Version_x0020_List as well and nothing changed.
i would compare apples and oranges if the nature of that contrast would give me insight to why they would behave differently for the same setup. if that makes sense.
the slash character was used in the name of the column. tried everything with that taken out to no avail either.
have you (or anyone checking in on this thread) had a OOTB cascading dropdown in a task list by chance? i didn't see any examples in my searches, they were all item list based.
Thanks again, i'll keep plugging away. thoughts welcomed and appreciated.