Add Support for Pre/Post Data Deployment Scripts
Some of my more complex data objects require that I turn off Validation Rules during deployment, then back on again after deployment.
Options that would work:
BEST: List of Validation rules under each object and and option to temporarily disable on a one-by-one basis during the deployment. A "Disable All Validation Rules During Deployment" option would be helpful if this feature is implemented.
BETTER: Ability to specify metadata xml to apply to each sobject pre and post deployment.
GOOD: Ability to specify anonymous Apex to execute pre and post deployment. This would involve a callout to the Metadata API, which would be messy, but would still give me the tools to accomplish my goal.
Scott Mercer
shared this idea
-
Justin Lyon commented
I'm shamelessly going to link to another user voice request on scripting that I think should be at the top of the list for anything pre/post scripting related.
I can appreciate the value this request is looking for, but I think we'll see a lot more value if this second, lower voted request get's traction.
-
Matthew Pomar
commented
We need Pre/Post just like ANT gives us. Right now, if we use Gearset, we have to deploy multiple times. The issue is tests have to pass on first pass, then tests have to pass on subsequent passes as well, making this process very difficult at times.
-
Anonymous
commented
Yes, I agree custom triggers would also need to be in the scope to meet requiements
-
Aidan Harding commented
We're like the option to disable triggers for the data deployment, then restore them afterwards, too.
Obviously, we never write non-bulkified triggers, but sometimes inherit systems that do. And some trigger may have side-effect (email, callouts) that you don't want to happen when just migrating test data.
The selective approach would be best for this as some triggers may be necessary to keep data integrity, even when inserting test data.