what if the label on the radio button was the wording, but the radio button to be selected would have the numerical value? Otherwise a script trigger on the field modified could in turn change a Boolean value in another field.
Transforming the litteral text to boolean is very simple using an evaluation formula in the field's options (Manage Database > Fields > Options for Field > Auto-Enter > Calculated Value).
The formula must be something like this: Case ( MyField = "Confirmed"; 1; 0 ). Do not forget to uncheck the "Do not replace existing value of field".
The problem you will run into, though, is that the radio button will not show which value is selected (as the checked value depends on the value list you used to populate the values for the radio button).
If you still want tu use the radio buttons and show which one is selected, you will need to use 2 fields (one for selection and the other to store the boolean value).
On the Data Formatting part of the inspector
Select Boolean as the type
Then enter a value for the zero and non zero which is what will show in the radio button, but it will be the 1 or zero you wish underneath
That text box DOES have limits to the number of characters that you can use though.
Using 2 fields per each boolean field seems wasteful and probably not the way to go.
My conclusion here is that in FileMaker the "correct" pattern is to use the radio button labels as the value for fields... is this correct?
I agree with you, Juan. I don't think it is the way to go.
Radio buttons is a way to select in a value list. So, yes, they are meant to behave like that.
You will have to explore a more suitable input method for your needs. Buttons maybe?