When default changed for an alphanumeric multi-select custom field defaulting breaks for that field on backend forms.
Editing the default value of a alphanumeric multi-select custom field results in that field having no default on backend forms (note I was able to recreate this on the "New Individual" form and "New Contribution" form).
- create a new contribution custom field (alphanumeric, drop-down select, with multi-select checked) and add a few options from the initial screen, making one default
- Go to create a new contribution from a backend form (ex: CiviCRM Admin Menu -> Contributions -> New Contribution) , watch that the default works correctly.
- Go back to the custom field, edit another option to make it the default
- Go to create a new contribution from a backend form (ex: CiviCRM Admin Menu -> Contributions -> New Contribution)
I was able to recreate this on dmaster (CiviCRM 5.32.alpha1)
I believe the issue is that when the default is changed it is not saved to the database the same way. It also does not show in the API the same way. See screenshots below of the differences.
|where||new field||edited field|
|API||'default_value' is an array||'default_value' is not in an array|
|DB||'default_value' is inside blocks||'default_value' is just a number|
|backend option value table (I think this is related)||no default check||default checked|