👋 Use this site to provide feedback and ideas for all Nintex Products. See our post on Nintex Community "Welcome to Nintex Ideas" for more details on Nintex Ideas, how an idea is handled by our product teams and more!
If you are looking for the Nintex roadmap, you can find that on Nintex Community
If you have questions about Nintex Ideas, please contact email@example.com
If you require support, please visit Nintex Customer Central
If you have a sales inquiry, please contact firstname.lastname@example.org
Thank you very much for posting your feedback for our review. Due to very low votes, we will not be adding this request to the near-term backlog. We are also focused on other highly requested features such as Form Participant permissions, Repeating sections re-usability, etc. Please keep the feedback coming as it is critical for our longer-term planning.
No this is not the same thing. My idea is driven off the feature we already have in Nintex Forms for Office 365, that allows us to select "distinct" checkbox in configuration on a drop-down control that only returns unique values even if duplicates exist. You can only do cascading by using distinct checkbox. Usually, you'd add a second drop down to the form that is filtered based on what you picked in the initial drop down. It's referred to as "cascading" drop downs that are all conditional based on previous selection in other drop downs.
The idea you provided is regarding rules being allowed on the data lookups. Good idea as well, would be nice when we need to force info for some situations that may require this.
A rule is created that allows developer to auto populate value in drop down control.
Is your idea the same as this idea? https://ideas.nintex.com/ideas/IDEA-I-2939