+2
In a Nintex form, I need the user to be able to enter items and then have those items be the choices in a choice field also on the form. That choice column will then be used within a repeating section. I thought this would be easiest to achieve using a multiline text box but I can't figure out a way to make this happen.
I basically want the items the user types in to 'clone' over to the choice field box, if that makes sense.
Any suggestions?
have you tried semicolon separated list of values?
see this https://community.nintex.com/thread/15319-checklist-based-on-value#comment-59806
+2
I figured it out!
Granted, the choice field on the form won’t be saving the option that the user chooses to a list column; but it can still be manipulated via form data if necessary.
+2
Got it, thanks!
, would you mind to share more details (screenshots)?
I somehow do not get what's the purpose of workflow...
it takes comma separated list of values from multiline text on input, does some magic that basically does not make any change with input and then writes the same comma separated list of values into same(?) multiline text filed.
as well, you fill in some field on form, then save and run a workflow. to execute workflow takes some time. so I would say you can not instantly see workflow output within the same form.
+2
Sure! Let me first explain why I needed this:
Our engineering division currently tracks all project design information in a very involved, multi-tab spreadsheet and they would love to convert the entire mess to SharePoint and use workflows to route everything. Each design section is currently a tab within the spreadsheet with six tabs in total, and each tab requires separate feedback and approvals. Also, not every tab is used on every project; that is determined by project cost and complexity.
For the design I am using 'tabs' and panels with rules applied in order to display one section at a time. In one of the sections, the project leader needs to enter possible design options, criteria and comments on how each interacts. The messy part is that there can be a random number of options AND a random number of criteria, so these need to be dynamic.
In order to 'clone' the options and criteria into the choice fields, I added a button tied to javascript that saves the data and refreshes the page; this button also kicks off the small workflow that 'clones' the data. It runs in the length of time it takes to refresh the page, which is nice.
The choice fields and comments (single line of text box) are all housed in a repeating section so that the project lead can add as many combinations as they need. That data I am leaving as form data and will then be able to display it in whatever format I need, thanks to Vadim Tabakman's post on parsing the XML to display it (Displaying Repeating Section Data in List Views, The Easy Way! ).
Here is the form set up for this particular section:
In the workflow:
And here is the set up on the Options Choice form field:
Hope this explains everything a bit better. 
ok, I see now.
thanks.
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
