CiviCRM Community Forums (archive)

Currently when I create a custom field, some of the questions relate to how its going to be stored in the database, while other questions relate to presentation.  In some cases this makes sense ( i.e. for date fields) but in many other cases it does not make sense. For example if I create a custom field called "Allergies" I want the options to be "peanuts, milk, wheat, bee stings"   Initially I choose multi-select. But I may want to change the presentation to "checkboxes" using the same options.  With Ajax libraries, I will have many other choices as to how to present this to the end-user. ( Both in the back-end and on the front-end via a profile.)

Also it would be nice to have a custom field that can be displayed as a "combo box"  where the end-user can choose from an option in the list OR type in something new.  Using the "Allergies" custom field, users could choose the predefined options "peanuts, milk, wheat, bee stings" and/or type in a new allergy such as strawberries.

It would also be nice to control the presentation of built-in CiviCRM fields. There are many cases where I may want to use radio buttons instead of a select list, or vice versa.

Thanks,
Sarah