What is data skew and how do you avoid it?

In Salesforce, building a future-looking data model is important. You generally want to anticipate issues before they occur.

One consideration that is overlooked is when a parent record has too many child records. Or when one user owns too many of the same records.… Read the rest

One-to-many relationships vs many-to-many relationships

Both Lookup fields and Master-Detail fields create a one-to-many relationship. This means the parent object can have multiple children. However a child cannot have multiple parents.

To allow the parent to have multiple children and the children to have multiple parents, a many-to-many relationship is needed.… Read the rest

Lookup fields vs Master-Details fields

When associating objects with each other, there are two main choices: Lookup fields vs Master-Details fields.

Here are some considerations for these two:

Master-Detail fields
These fields create a strong connection between two objects. The field is created on the “detail” object, and points to the “master” object.… Read the rest

Considerations when creating custom fields

One of the services I provide is technical debt assessment. I cannot tell you how many times I’ve been called in to help a client who is frustrated with their Salesforce implementation. I cannot tell you because the number is too damn high.… Read the rest

Autonumber naming convention

Let’s say you’ve decided to create a custom object and use an autonumber as the data type for the record name. The next decisions are, what should be the naming convention for the record name and display format.

Record Name
The most commonly used record names have either “Name” or “Number” (or “#”) in it.… Read the rest

Custom object record name

When creating a custom object, you have two choices for the Record Name: text and autonumber. What principles can you use to determine which one is best?

Consider the following:

1. Uniqueness
If you want the field to be unique, use an autonumber, since uniqueness cannot be enforced with text.… Read the rest

Data modelling – standard vs custom

When creating your data model, there are several principles that can be used. One of them is the KISS method: Keep it Super Simple (which is a better alternative than Keep it Simple, Stupid).

Here are some considerations when applying this principle:

Standard Objects
When the functionality you’re trying to build fits about 80% of the existing data model and built-in functionality.… Read the rest