Nintex Form Rules to set the value of controls
I'd like to be able to use Nintex Form Rules to set the value of a control or list item without needing Javascript. For instance, if my user selects a particular checkbox or selects a specific choice from one list, I'd like to set the value of other checkboxes (choice or yes/no fields), radio buttons (choice or yes/no fields), or enter a particular string into a single or multiple line text box.
I'd like it to function much like an IF statement in Microsoft Excel, where if a particular control equals a certain value, the value of other controls and their connected sharepoint list items can be set.
Jamal Brown
shared this idea
I am pleased to announce that with the September release of Nintex Forms for SharePoint 2013 and 2016, Set Field Value is now a new rule type in the responsive designer. This will allow you to set the value of the Single line of text control.
If you would like to see the rule set other fields, please submit a new idea.
-
Adeel Ahmed
commented
I am using Nintex form 2019 and unable to see set field value action in the rule. can you please guide me on how can I achieve this in 2019?
-
Joanne
commented
Please add this functionality to classic 365 forms.
-
Anonymous
commented
How can I locate this rule feature so that I can try it out?
Euan Gamble (Admin, Nintex)commented · February 01, 2018 19:05 · Flag as inappropriate
This allows you to set the value of the Single Line of Text in the Responsive Forms designer. We are currently looking into how we could bring more advanced functionality to more fields in the future.
-
Brett
commented
I cannot see this in the Classic form, a lot of features are currently missing in responsive designer including the Nintex live feature, so if it can be added to classic form it will help us immensely...
-
Anonymous
commented
Ok, I'm currently missing something. Has the action rule been added as a function for the single line of text control? Cause when I attempt to create a rule for this type of control, I do not see "action" as a type, only formatting and validation. I've recently updated my forms to the newest version so that was why I'm confused here.
-
Anonymous
commented
Yes, i've updated my Nintex forms to the newest version and I do not see this built into the forms. Do I need to do something different?
-
Susan Sch.
commented
Are there any plans to make this also available for date, people picker, choice or yes/no controls?
-
Jason
commented
Any update on the timeframe for this feature in O365?
-
Anonymous
commented
Only for text fields... hmm
-
Kassie Stippel commented
Fantastic News. Thanks for the update Euan!
-
Anonymous
commented
Great news. I'm hoping this will be for 365 as well. Is there an ETA?
-
Susan Sch.
commented
Eagerly awaited feature - hopefully made available on prem?
-
shaunlub
commented
Fantastic. Can't wait.
-
Anonymous
commented
I was looking for something like this the other day. Sad to see it's not readily available. Anxiously awaiting ...
-
Jon F
commented
Isn't this the Default value=expression feature?
-
Carmien Owen
commented
This is a required feature. I'm looking at every angle: Rules, Form Variables. I'm being forced to do this because a filtered list lookup isn't working on a particular form (bug?) and need to grab a selected value on a direct list lookup.
I noticed Nintex Prod Mgmt indicated this is under review May 4, 2016. It's got 429 votes by Feb 10, 2017 and still no update.
The use case is clear. I don't know how these forms are coded, so my solution suggestion is moot. But why can't we find an elegant way to simply use rules to store the value into a workflow variable at runtime? I'm sure there are other solutions from a coding point of view. But this approach strikes me a possibility - build a runtime function that allows the storage of a value into a workflow variable.
-
Bruce Smith
commented
Agreed that I used this type of rule a lot in InfoPath, so helpful to administer forms
-
Jeff Frantz
commented
Ugh! I am literally creating my second Nintex form ever, and ran into a critical need for this functionality. I am in disbelief that it doesn't exist.
-
Anonymous
commented
If only we could have this without having to resort to Java script code - I would have so many less grey hairs. I cant even understand why its not there already. InfoPath did this 10 years ago.
-
Jade
commented
I have been looking for this everywhere on the Nintex forum. Glad I no longer have to keep looking as it is not available, but very sad this functionality doesn't exist. I thought for sure there would be a way.