Need to be able to change the custom field option values without changing the option name
K
Kate Cooper
We want to be able to use a custom field as the opportunity value. The custom field will be selected from a dropdown by the client on a survey so needs to show as (for example) "£97/month".
The option value that we would then pull in to the opportunity value needs to just be the number "97". However, when creating the custom field it is impossible to update the option value without updating the option name.
Log In
P
Pascal Dörflinger
Weird this hasn't been fixed, still.
M
Mark Penney
Lots of little weird, easy to fix quirks like this. It's great they move fast and add new features. But things left half done can become more and more frustrating no matter what new features are added.
Need to be able to have different values that are not just numeric. For example a drop down to select Tax types for Xero, you want the human friendly name and then the API required value.
Otherwise have to create new fields and automation just to track and update that.
K
Kevin Slaton
Agreed 100% Why have a field that has an "Option Name" and an "Option value" if they have the exact same data/value. This makes NO sense at all. I almost fell like the original intent of this field was to provide the functionality we are seeking and was not implemented correctly.
R
Ryan Buono
I need this. Anyone with any sort of data background understands why this is important. It's like they know it should be working the way it would appear to work, otherwise, why would there be both a name and value field?
G
Gracen Duffield
I figured out how to put an option value in for calculation, but I can't access the calculation value.
G
Gracen Duffield
This is possible to do.
Create the dropdown list custom field.
Put the dropdown list on a form.
In the form, select options for the dropdown list.
There is an option to add a calculation value.
G
Gracen Duffield
Agree. Currently, when I use a dropdown, I also have to write If-then-else code for all of the dropdowns. If we could code the option value to be different from the option name, it would save significant overhead for processing forms.
for example, I am coding a form that has 10 questions. each question has a dropdown with six selections, which are:
Disagree strongly
Disagree moderately
Disagree a little
Neutral
Agree a little
Agree moderately
Agree strongly
When I compute the score, I have to do an if-then for each of the questions:
Question 1:
If Disagree strongly, then score = 0
If Disagree moderately, then score = 1
...
If Agree strongly, then score = 6
This means there are 6 branches for each question, which adds up to 60 branches total.
If there could be an option-value that is different from the option-name, then when the form is filled out, the option-value could be automated.
The way i have seen this done in the past is with a two-pronged data structure. there is a field.name and field.value on the backend. The front-end presents just the field.name for selection, but for calculation, you can use field.value.
J
Jon Bowerman
This is a must have