Sometimes when we have a question on a form (specifically the Dropdown & Multiple Choice form fields), we want to store a different value for each. This would be used when the form questions and the stored value should be different.
For example. see these two Launch Form questions.
The options are Weekly, Semi-Monthly, or Monthly, but perhaps I want to store the responses as numbers (ie 52, 24, 12) to do some math/formulas.
I know I can use the use the Switch() formula, to transform these 3 options, but the formula is fragile & subject to breaking if I ever change the values. I would need to remember to update the Switch formula if I ever wanted to change "Semi-Monthly" to "Semi Monthly".
Here is another example:
The options are very descriptive (& long) to help the user select the correct option to drive conditionality, but we only need to store "Yes" or "No" in the metadata. I can use the Concat() formula, but store a different values for each would be a more elegant solution.
Last example, I feel like this feature would be perfect for solving @Cody_Greer's needs:
https://community.ironcladapp.com/t5/Ironclad-Users-Forum/Formula-Wizard-Needed/m-p/2396
We have conditions based on the entity selected (ex. Arby's Restaurant Group, Inc.) that inserts an alias "Arby's" into the document. Right now I have about a paragraph of conditions for our 7 brands in the document over 125 times, which makes the document unreadable. As an alternative, I was thinking of fields for each brand that contain a formula inserting the alias if that brand is detected, and then combining them all into one condition I can use in the document, the issue being that I'm struggling putting that into practice.
His question could be:
Selected Entity:
- Arby's Restaurant Group, Inc.
- Baskin-Robbin, Inc.
- Buffalo Wild Wings, LLP
but the stored value of each selection would be
- Arby's Restaurant Group, Inc. -> "Arbys"
- Baskin-Robbin, Inc. -> "Baskin-Robbin"
- Buffalo Wild Wings, LLP -> "Buffalo Wild Wings"
Lastly - I think formulas get us there, but it requires two fields - 1 field to store the value / selection from the question & 1 formula field to store the calculated / transformed value.
@Andrew_Smith - any use cases you can think of and want to share?
