This analyzer helps solve problems with deleting items from an org when they are still referenced by other items.

What triggers this problem analyzer?

If we try and delete a component that is referenced by other components, the analyzer will suggest that you also delete components that reference that original component that you were trying to delete. 

For example, consider we have a custom field, DiscountPercentage, on the Account object that references another custom field,  DiscountRate, shown below.

If we were to try and delete this custom field DiscountRate , the problem analyzer will identify this deleted dependency and suggest that you also delete the DiscountPercentage  custom field.

What problem is it solving?

If you don't include these deleted dependencies, your deployment will most likely fail.

How does it work?

Gearset will automatically add the deletions to the deployment package to be also be removed from the target environment.

Did this answer your question?