Accepted Solutions
They all have the same name value. The name value is what is stored in your data. The system then looks up the label that corresponds with that name to display the label to the user. So it looks up the name of 'M1-1 (1 or 2)' and grabs the first associated label.
You need to set up unique names for each of your unique labels. If it's important to have M1-1 (1 or 2) populate in a field whenever a user picks one of those four options, then you set up an additional field to store that value and use pulldata to populate it. In that situation your external choice list will look something like this:
Use existing data in your survey - the pulldata( ) function
They all have the same name value. The name value is what is stored in your data. The system then looks up the label that corresponds with that name to display the label to the user. So it looks up the name of 'M1-1 (1 or 2)' and grabs the first associated label.
You need to set up unique names for each of your unique labels. If it's important to have M1-1 (1 or 2) populate in a field whenever a user picks one of those four options, then you set up an additional field to store that value and use pulldata to populate it. In that situation your external choice list will look something like this:
Use existing data in your survey - the pulldata( ) function
That worked like a charm, Thank You! The only thing I added to your workflow was that I needed a choice filter because my choice list was based on a previous select one value.
