This problem analyzer helps you deploy missing dependencies from your deployment package.

What triggers this problem analyzer?

If you try to deploy an item without a component that it depends on, Gearset's analyzers will first try to find that missing component so that it can suggest you include it in the deployment.

If the analyzer is unable to find the missing component, this means that the component has not been detected by Gearset in both the source or target environment of your comparison for the current deployment. This will cause this analyzer to fire and identify the unresolved missing dependency problem. 

For the example below, Gearset has identified a dependency on a custom field that cannot be found.

What problem is it solving?

When deploying items without the components they depend on, your deployments will most likely fail.

How does it work?

While the nature of the problem the analyzer is identifying is very similar to the missing dependency problem, you can distinguish the difference by the message presented into Gearset's UI being slightly different.

Rather than being able to provide a list of components to add to the deployment, as they can't be detected, Gearset will suggest to include the dependency's component type in the comparison filter. By including the missing type in the filter, hopefully the components can be seen in the new comparison results and included in your revised deployment package.

Did this answer your question?