Skip to main content

Just tried out the Cascading drop Down feature in O365, and I wanted to share the experience

 

First thing first, why will you need “Cascading Dropdown”? | Because it’s “User Friendly”

 

Example: create a form where user can choose a value in a
“Country” field then the next field “City” will filter and display the cities
for the chosen country.

 

Requirements:

 

Nintex Form for O365

 

One SharePoint Main List

 

Two support SharePoint List

 

First create a support list named Country:
84150_pastedImage_0.png
 

Then create a second support list named City | in the City
List create a lookup column “Country” with lookup to the “Country List”

84151_pastedImage_1.png

My main list is named “CascadingDropDown” | it has three
columns | Title | Country (lookup to country list) | City (lookup to city list)

84245_pastedImage_2.png

In the ”CascadingDropDown” list in the ribbon choose to
customize with Nintex Forms

84246_pastedImage_3.png

This will send you to the Nintex Form Designer view | we
won’t make any big changes to the form just the “City” field control

84247_pastedImage_4.png

Double click on the City
field control to bring up the control settings | we will filter the selection
based on the “Country” field control

84248_pastedImage_5.png

Save and Publish your form | when adding a new item you can
now choose “Country” and “City” will filter the selections available

84249_pastedImage_6.png
84250_pastedImage_7.png

84251_pastedImage_8.png
Great Works on bringing this cool feature to O365, thank you!

 

ENJOY!!

Michael,

I,too, have found the cascading lookups in Nintex forms to be a little unfriendly, and more complicated than they need to be. Nintex forms are harnessing Indexed columns only here (generally Title columns) to do the lookup. Here is an example from a current form I am working on:

These are the settings from the 2nd lookup.

1 - ID connected to => this is pointing a lookup column in the current list. The source for this lookup is the Title column of a Cost Unit list. The Cost Unit list also contains a lookup column displaying the Departments the Cost Units belong to. In effect we have 2x indexed title columns here - which is what Nintex forms are using to do the filtering, I believe.

2. Filtered By Control => the first lookup is pointing to a list of Departments (the Title column, again), which was also used as a lookup in the Cost Unit list's Dept column.

The Cost Unit list is our 'master lookup' table where changing Dept selection (control 1) filters the Cost Units (control 2)

cascading lookup settings.PNG

I hope this helps.

Reply


View our Community Site Map

Nintex Community Sitemap
Terms & ConditionsCookie settings