Skip to main content

Developing a SP2013 list solution and using Nintex 2013 Form
Needed to create a Cascading Drop-down and built using 2 additional SP Lists for Choice 1 and 2.

  1. In my entry form, I created the 2 selection/input fields using the List Lookup control, following instructions as outlined numerous times in Nintex blogs.
  2. The 2 fields are bound to the SP list fields using the "Text Connected To" option
  3. All is working as designed, but I've run into 2 not-insignificant problems:
  4. Problem #1 
    •  The 2 List Lookup fields where the data is selected and then bound to the SP list, is used (enabled and visible) for initial data entry and intended for the New Mode function only
    • Those same fields are intended to also be "visible" for Edit and Display modes, but not editable. (so that the initial data entry is protected from future edits.
    • When I set the Appearance control Enabled to No or use an Expression such as "Is New Mode", and then open the form in Edit Mode the previously entered (and bound) values are no longer visible. When I Save the item while in the Edit Mode, the data is then unbound or deleted from the List.
    • The same action occurs if I use the Form Rules for Disabled and use an expression such as "not(Is New Mode)"
  5. Problem #2
    • When the 2 List Lookup fields are Enabled in the Appearance control option (so that I can at least view the intended cascading drop-down results), when they are viewed in the Display Mode, the values are shown as hyperlinks to their respective SPS lists that were built to contain the field 1 and 2 choices.
  6. Since this appears to be the most efficient means to create a Cascading Drop-down which is essential for this solution, this is obviously creating a big problem and I am on a tight deadline. (of course wink.png)

Thank you in advance to anyone who has a solution

Mark

The 2 fields are bound to the SP list fields using the "Text Connected To" option

lookup value (text) is not sufficient to identify an item in source list. source item is always identified by its ID.

easier for you will be to drag&drop list field on design canvas from left-hand 'List columns' pane. it will setup binding to list field automatically.

if you  want to do it manually on your own, you have to bind 'ID connect to' to respective lookup list field. (btw. after that 'Text connected to' should disappear)

When I set the Appearance control Enabled to No or use an Expression such as "Is New Mode", and then open the form in Edit Mode the previously entered (and bound) values are no longer visible. When I Save the item while in the Edit Mode, the data is then unbound or deleted from the List.

if you configure lookup control as mentioned above, I believe it will work correctly.

When the 2 List Lookup fields are Enabled in the Appearance control option (so that I can at least view the intended cascading drop-down results), when they are viewed in the Display Mode, the values are shown as hyperlinks to their respective SPS lists that were built to contain the field 1 and 2 choices.

this is by design, what's the problem with that?

Marian

Thank you for your prompt feedback - I wondered whether I needed to use the ID Connect feature.  I'll be working your solution today.  I'll revisit this blog to report results.

On the last point, I expected to simply display the values (editable or not), but when clicking on the value now, the user is redirected to the actual subsidiary SP lists, which takes them completely out of the master list.  Viewing the values as choices is necessary of course, as in the initial selection, but this is an actual hyperlink, where you're not presented the choices but takes you to the other lists.

Thank you again

Mark

Marian

Again, thank you for your feedback.  Made the changes as suggested, binding the ID# as well.

The Disabling feature that I needed had to be accomplished using the Form Rule formula for Disable in order to work correctly.  Using the Disable feature in Appearance, either using NO or Expression (is New Mode) still caused the unbinding of the Text Connected. (But strangely, the ID binding remained intact). That also solved for preventing the values having hyperlinks in the View Mode.  All appears to be working as I would expect.

that should not happen.

but at least you found a workaround happy.png

Reply


View our Community Site Map

Nintex Community Sitemap
Terms & ConditionsCookie settings