The entity: {object} does not have history tracking enabled

The entity: {object} does not have history tracking enabled

Luke Drury on

Share with

LinkedIn
Twitter

History tracking for Salesforce metadata can be hugely useful in seeing how your fields have changed. But, it’s also a common cause of deployment failure that blocks teams from releasing changes to their standard or custom objects. In this post, we’ll walk through why history tracking can cause deployment failure and show how Gearset allows you to deploy tricky metadata with confidence.

Tracking changes to CustomObjects

In Salesforce it’s possible to enable history tracking on custom and standard objects. Once you’ve done this, you can then turn on history tracking on a per field basis, and so track changes to fields you’re interested in.

Gearset DevOps Summit: Developing a long-term Salesforce DevOps mindset

Find out more

Why deployments can fail due to changes in history tracking

NOTE: Gearset’s comparisons have had an upgrade! We’re in the process of updating all our blog posts with the new UI images, but in the meantime you can find out more here.

In Gearset we break objects down into sub-components during the comparison, giving you control over which changes to an object you want to deploy. An example of this is standard objects and their fields. For example, you can deploy a new picklist value on a field without also deploying changes to the parent object to which it belongs, or changes to other fields in that object.

However, Salesforce enforces relationships between certain configuration options within these objects. The history tracking option is one example. If you tried to deploy a change to a field, such as adding a picklist value, and this change also turned on history tracking for that field, then your deployment would fail if the parent object in your target org didn’t have history tracking enabled.

Selecting a field to deploy that contains a history tracking change

How Gearset solves the problem for you

We’ve added in a new feature to the underlying dependency analysis engine in Gearset so that we can detect when you’re trying to make this type of change.

When this happens, Gearset will warn you and give you a chance to ignore the history tracking change on the field, but continue your deployment with all other changes to that field.

Excluding history tracking changes in your deployment

Do you want to achieve a 98% deployment success rate?

Gearset users have an average deployment success rate of 98% — the highest in the industry! If you want to join the thousands of Salesforce teams leading deployment accuracy, why not try Gearset for yourself with a 30-day free trial today.

Try all of Gearset for free