Improve detection of custom fields on Managed Package objects coming from Git
If I have a managed package object in Git, Gearset does not recognize it as managed package code in its comparison to a Salesforce org. This is a problem since it may not recognize a change if a custom field has been added to the managed package object.
Bob Hatcher
shared this idea
-
MT Harvey commented
i can see them in changesets but not in the primary tool to manage my deployment pipeline? strange no?
-
Aidan Harding commented
We frequently have to add fields to managed objects. Not being able to deploy those fields via CI is a great pain and another hole in the idea that git is the source of truth.
-
Randy Lutcavich
commented
This is also affecting me. Makes our CI/CD pipeline unusable at this point and I have to manually deploy.
-
Anonymous
commented
We have similar issue. We have a bigger team and many developers are keep on changing the managed package custom objects. CI jobs is excluding these changes in every deployment which makes us to deploy manually. Manual deployment adds work effort and time consuming. If there s way that Gearset automatically skips the suggestions " exclude managed package changes" and keep the changes that would be greatful.
-
Samuel Lee
commented
had same issue. this would be a great new feature!