Following the logic behind
CRM-3631, what we also did for this client was to denormalize organizations to use simply one custom field for "Organization Name" instead of using the full-blown Organization contact type. While adding the possibility for data inconsistencies between contacts, this approach does make for a much simpler interface.
Usability is often often more desirable than flexibility to groups with not enough staff to manage all the intricacies that having multiple contact types brings.
I see this integrating with the settings for
CRM-3631. You could have an option for organizations:
- Use the "Organization" contact type
- Use a field for "Organization Name"
- Do not use Organizations.
Naturally there would need to be strong warnings when changing from one option to another if there is data in CiviCRM that would be lost.
When switching from one option to another CiviCRM should also pre-fill data (ex. if the admin switches from the contact type to the field, Individuals should have the field populated with data from previously related Organization objects and vice versa).