Convert Radio select property value to number property
SOLVE
One of our clients has a form with numerous radio select fields that asks the user to choose a 1-10 answer. Even though the value of these properties happen to be numeric, Hubspot only allows radio selects to be copied to single-line/multi-line properties in a workflow. I need to be able to do calculations with the values of these radio questions but only number properties can be used in a calculated property.
Looking for some ideas on how I could convert the radio select values to number properties.
The easy solution is to create number properties for each of the radio selects and use those in the form. However, I don't think the client to going to like the idea of users having to manually key in their 1-10 answer for each question.
In this scenario I would have number based properties that correlate with the radio select question and then use a workflow to set the value on each end. You don't necessarily need to copy the value if it is consistent. For example:
If Radio Button Property is "Great" then set number property to 9
If Radio Button Property is "Good" then set number property to 6
A bit up front work with workflows, but it would give you the ability to use calculated properties without a bunch of manual effort in the future.
Convert Radio select property value to number property
SOLVE
@WVanBalen in your Deal pipeline set-up, you can set those probabilities to whatever you need. And if you limit permissions, you can protect them so no one changes them. Or you set a policy in place to ensure no single user is changing the global Deal probability setting. Would that solve it so no one changes it?
I don't know that I understand how a radio select would change the experience. Can you provide more details of your use case and reasons if that solution doesn't solve it for your needs? Thanks!
Did my answer help? Please "mark as a solution" to help others find answers. Plus I really appreciate it!
In this scenario I would have number based properties that correlate with the radio select question and then use a workflow to set the value on each end. You don't necessarily need to copy the value if it is consistent. For example:
If Radio Button Property is "Great" then set number property to 9
If Radio Button Property is "Good" then set number property to 6
A bit up front work with workflows, but it would give you the ability to use calculated properties without a bunch of manual effort in the future.