Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Remove email, sex, birth_date base fields from Individual
Original summary
Problem/Motivation
After we add new fields(email, sex, birth_date) to individual entity, make those fields configurable.
Proposed resolution
- Create custom settings form where you have a custom settings UI and then set the settings there based on that configuration.
- Update the contact view already here to show the email and also have a a filter for it.
Comment | File | Size | Author |
---|---|---|---|
#12 | crm_core-2721775-10-12-interdiff.txt | 1.4 KB | RoSk0 |
#12 | crm_core-2721775-12.patch | 10.46 KB | RoSk0 |
Comments
Comment #2
CTaPByK CreditAttribution: CTaPByK at MD Systems GmbH commentedComment #3
miro_dietikerNot sure about this direction. I fear we will end up with a crazy amount of configurable items...
For instance, just because things are configurable won't help us adapt default views and other configurable items. Not sure what the real value is for these fields, it we would offer a known well prefixed field name that can be easily used / reused.
Comment #4
mikran CreditAttribution: mikran at Mediamaisteri Oy commentedI was a bit surprised to find out that these are base fields and not normal fields. If these were just normal fields, one could delete the field or hide it when it's not wanted. And yes, views would need to be updated after too but that's why these are just default fields / views and ones that site owner can update, right?
Comment #5
RoSk0The only field which make sense for me as a base field is a name for Individual. Rest is redundant and shouldn't be bundled as part of core. There is many use cases when sex, date of birth or email doesn't play key roles in CRM system.
I'm going to wait some time for feedback from community and then I will remove sex, birth_date and email base fields.
Also created a task to remove email with type field from CRM Core, it doesn't belong to this project.
Comment #6
mikran CreditAttribution: mikran at Mediamaisteri Oy commentedI agree. Name is problematic base field too as name field does all of the configuration on storage level and not on field instance level which would be best for CRM.
Comment #7
PanchoAgree with both of you, @RoSk0 and @mikran: all of these should be normal rather than base fields. While sex, birth date and email should be optional, the name field at least needs to be fully configurable.
Comment #8
RoSk0Patch to remove sex, birth_date and email base fields.
Comment #10
RoSk0Fixed failing test and coding standards.
Comment #12
RoSk0Removed email test leftovers.
Comment #14
RoSk0Committed.