Select the fields to deploy during a data deployment
Hi we use the data deployment feature is it possible to only select some fields to deploy data from one org to another and not always all the fields on an object.
You can now select fields to exclude during a data deployment
Bijay Saha commented
This is very important, as there is a chance of overriding the unwanted field data
Samuel Murphy commented
Agreed--this is critically important. Really need the option to explicitly include or exclude fields. I've been able to do some stuff around masking--but there's not even an option to "mask" with a null value!
This is a very important feature in any ETL tool. Exclusion of certain fields is a must feature for data migration for various use cases.
Also I totally agree with David Spell's comments for that feature to be "Deploy everything except these fields" as that will save number of clicks for users. Exclusion of fields are less and by default all fields should be selected on the UI presented to exclude certain fields.
David Spell commented
To answer Tom's question from September 4, 2020, I would find it most helpful to have an option to select which fields to NOT deploy - "Deploy everything except these fields"
JF Thibault commented
This would make data deployment simpler. We have the same issue as Chris mentioned where for some records have inactive values that make the deployment partially fail.
What scenarios are most interesting to people here?
Is it important to be able to say "only deploy these fields"?
Is it important to be able to say "deploy everything except these fields"?
What other scenarios do you run into where you need to be able to set a specific set of fields, such as the picklist example below?
Chris Deutschmann commented
I add my vote to this. We have a number of fields, specifically picklist where records might have inactive values set in them so when doing data deployment these records fail. however the fields might not be critical to the data deployment, so being able to exclude them will allow the data deployment to complete without skipping records that we otherwise need, but not necessarily all the data in the record.