Choosing between standard objects and custom ones
Summary
Choosing between Salesforce standard and custom objects is crucial when designing new features. If standard objects meet at least 80% of your data needs, they should be preferred to minimize technical debt. Overusing custom objects can complicate data models and operations, as shown by a client case involving a custom Transaction object overloaded beyond typical use. Carefully analyze your requirements to decide whether to extend existing standard objects or invest in rebuilding with standard functionality for long-term simplicity and maintainability.
Takeaways
- Use standard objects if they cover 80% or more of your data model needs.
- Avoid overloading custom objects with multiple unrelated functions.
- Weigh quick fixes against long-term technical debt and maintenance costs.
- Carefully analyze existing data models before deciding on custom development.
- Rebuilding on standard functionality simplifies operations despite higher initial costs.
When designing a new feature for a client, one of the first questions you need to ask yourself is: should I use standard objects or create custom ones? Best practices dictate that if you can use 80% or more of the standard data model, then that’s your choice. If it’s less, then consider custom objects. Case in point: I’m working with a new client who has had several consultants help them over the years. As I analyze their data model, I noticed they have the following custom objects: Transaction (which looks a lot like Opportunity or Order) Item (which is like Opportunity Product or Order Product) {ClientName} Product (which is like Product) Tree (which is like Asset) Transaction is usually created from an ecommerce store. It contains both purchases and donations. They could have used it as staging object and then created records in standard objects (like Order and Order Product). Instead they’ve overloaded it, and even use it to fulfill the order.