search

forcedotcom / devops-center-feedback

61 stars 2 forks source link

Including a custom object adds unwanted items #218

Open LoganGanieanyReddit opened 2 years ago

LoganGanieanyReddit commented 2 years ago

I updated the label of a custom object and added that object to a work item. In the pull request, I noticed the object also included 3 custom fields that were changed/added in my dev box. However, I don't want to deploy one of the fields.

Upon deployment i received an error since the field it's trying to deploy is a lookup to an object that does not exist in any other environments yet. This is by design as I am not ready to deploy that field or object yet.

I have a few questions:

  1. Why are additional fields that I did not select being included when adding the object to the work item?
  2. How would you recommend just deploying an object label change?
  3. What are the implications of deleting the file (for the unwanted field) from the pull request?
kfidelak94 commented 2 years ago

See question/response here: https://trailhead.salesforce.com/trailblazer-community/feed/0D54S00000JdnSUSAZ