When pushing Workflow rules and associated actions, gearset mistakenly says target objects do not exist
When pushing work flow rules and associated actions, if you do a compare with only workflow, then gearset prompts an error indicating that the target objects do not exist in the destination and that the rules should be removed from the package for the deployment to be successful. In this case, it told me Account, Event and Opportunity do not exist in the target. Including other metadata from the referenced fields resolves the issue.
Mike Watson
shared this idea
-
[Deleted User]
commented
GS should compare the WF between source and target: If the delta does not involve adding any new fields or sobjects from the source that are not present in the target, then the analyzer should not detect a need to deploy the underlying referenced objects.
There is only one edge case I can think of though wherein GS is doing the right thing: The source has changed the field type of a field referenced in the WF but the deloyment isn;t including that altered field. The deploy mighth go through successfully but the WF might not execute as expected.
This same User Voice applies to Process Builder flows as well - especially if the only change is description or activation