Duplicate field options

[Rocket Music]

I'm confused.

In my form, many field VALUES are the SAME within a field (e.g. dropdown might have 3 selections with value 0). So, when I view the submissions, it appears that nothing is shown for those fields - I think that is the case when a selection is made that has a duplicate value in that field, e.g. when there are 2 options with the same value.

I understand that in most cases, you would not want to duplicate values, but I don't think this is uncommon, is it? In my case, value is the added cost for an feature selection, so it's often the same number for several field selection options.

My, questions:
Do the Field Values in each Field Options Group defined in FT forms need to match the form field values declared in the form itself? Would changing those to different values fix my issue or mess up submissions?

Is there a way to view and send the entire form (field names, selection, etc.) like you see when you view then edit the submission? I don't understand why the view doesn't contain the selections, just the value of the selection. The selections are there when I view then edit - how do I get transfer all of that data?

Or am I missing something here?

thanks for any help !!

Dan

[Ben]

Hey Dan,

I understand that in most cases, you would not want to duplicate values, but I don't think this is uncommon, is it?

Actually, yes! Unfortunately, this won't really work for any script. Here's the problem. Imagine your dropdown has these values:

Code:

<select name="example">
  <option value="0">Zero option 1</option>
  <option value="0">Zero option 2</option>
  <option value="0">Zero option 3</option>
</select>

Passing the values is fine - Form Tools will happily store "0" for the field, but when it comes to re-populating the field within the UI, it won't know which one was originally selected since they all had the same values. Multi-option fields - dropdowns, checkboxes & radios - all must have unique values for each option in their group.

Do the Field Values in each Field Options Group defined in FT forms need to match the form field values declared in the form itself? Would changing those to different values fix my issue or mess up submissions?

They *can* be different, but it's generally simplest if you keep them the same. Sometimes I change the labels for the options, to make them more descriptive within the Form Tools UI, but generally I keep them the same. The important thing is that the values are the same. That's what's uniquely identifies each option. So if they're different, any values in the form that aren't in the field option group won't be displayed.

Is there a way to view and send the entire form (field names, selection, etc.) like you see when you view then edit the submission? I don't understand why the view doesn't contain the selections, just the value of the selection. The selections are there when I view then edit - how do I get transfer all of that data?

I actually don't quite follow you here... would you mind explaining this one again?

Thanks!

- Ben

[Rocket Music]

Ah. cool. I see.
I solved my problem by calculating option prices without reference to the element value. There's several ways to do this, but I used a function with an array (javascript) that referenced the same option number. There's better ways, but this works fine.

And I can keep all of my value labels as descriptions of the field option.

thanks !!!
Dan

[Ben]

Nice! And np.

- Ben