Allow individual lines to be selected for inclusion or exclusion of a deployment
Allow individual lines to be selected for inclusion or exclusion of a deployment
![](https://secure.gravatar.com/avatar/9ce75bea581dcb38bdba5c4e28a2ca6f?size=40&default=https%3A%2F%2Fassets.uvcdn.com%2Fpkg%2Fadmin%2Ficons%2Fuser_70-6bcf9e08938533adb9bac95c3e487cb2a6d4a32f890ca6fdc82e3072e0ea0368.png)
EDIT:
Gearset now lets you select specific fields in layouts for a deployment.
Here's a quick article on getting started with precision deployments for layouts:
https://docs.gearset.com/en/articles/6407322-getting-started-with-precision-layout-deployments
We are working on adding support for more metadata types such as record types, value sets, Lightning pages and other XML types.
-
Ryan commented
We've seen some competitors that have this feature. Especially for things like flow, where I want to only grab my edits, but allow others to also work on this at the same time if needed.
-
Carl Stobie commented
Very wanted feature please.
-
Yan N. commented
This feature is a MUST when trying to deploy a change in a single picklist field that is part of a record type, while excluding changes to other fields that are part of the same record types.
-
Tuhin Mazumder commented
This is required please
-
Shashi Shroff commented
This would make deployments much easier where there are multiple developers.
-
[Deleted User] commented
especially useful for "container" type metadata like Layout; we would use an exclude lines feature here
-
Patrick commented
This would make deploying multiple work streams much easier.
-
Stuart G commented
This is an absolute must-have for use cases past one developer building one change and deploying it at a time.
We have a use case where a record type has multiple changes reflecting new fields, but only one field is ready to be deployed - this blocks us being able to deploy the record type. -
Anonymous commented
This would be really handy!