Sorry but no the display and value are the same, there is no aliasing of the items, so you would either have to use abbreviations or full state names.

Best,

Joe

I'll ponder it but I'm inclined against it because it would require making it possible and required to enter both a display and value setting from the UI (and it would require storing both in the database) and that would complicate things more than I would like. I really think the UI needs to be as simple as possible, and the answer choices are supposed to be the answer choices, what you see is what you get. I think it is perfectly reasonable to display the abbreviation and use it as the value as well or display the full name and use it as the value as well.

Best,

Joe

You could do some post processing on the form data after exporting it to handle that kind of thing or even implement a custom form submission handler to automate it.

I realize that I'm not going to make everyone happy but for now my answer is no on this and I think saying no is the right thing to do in this case for similar reasons that Steve Jobs mentions about saying no. 

Best,

Joe

the form submission handler would not be for adding items to the dropdown list it would be for translating the displayed values into the non displayed values once the form is submitted and either pushing the data somewhere or sending a custom email with the values translated ie from the street address to the store number in your example.

To me if its a "larger" project then certainly it seems reasonable to do custom post processing of the data to meet the project goals.

Hi Jamie,

Actually IndigoTea emailed me with some more points in favor of it and I've decided to implement it. I think what I will do is have a setting to enable showing the extra inputs so that by default we can keep it as simple as possible, but more advanced users who need it can enable it.

Best,

Joe