My example here is the Case object, which is used for integrating an external tool used for case management, into Gainsight.
While it is great that it comes with some OOB fields, some of those cause problems. Namely, the already created dropdown fields. Consider the following:
- Once a picklist field is created, the dropdown list ‘category’ cannot be changed or removed.
- When the dropdown for Cases is created, a field and corresponding dropdown category is created and assigned to that field.
- Part of that dropdown category includes values that cannot be deactivated, or modified, in any way.
Why does this matter? Because if you have no business use for those values, you cannot repurpose them. You cannot even deactivate them. You essentially need to create a new field, and a whole new category. Because some of these OOB fields are *required*, that means you have to dummy map to them anyways, then use the fields you actually want. This is enforced platform bloat and it is incomprehensible why it exists.
Maybe you can submit a case for them to be removed, maybe it will happen, and maybe they’ll do it in 2-3 months. But is not something an admin shouldn’t be able to manage on their own.
Very much related to this request as well:
