Timeline for Programmatically Turn off Triggers/Validations/Workflow
Current License: CC BY-SA 3.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 3, 2017 at 21:04 | history | edited | Daniel Ballinger | CC BY-SA 3.0 |
Fixed typo in Title
|
| Apr 30, 2017 at 23:03 | answer | added | Daniel Ballinger | timeline score: 3 | |
| Sep 27, 2016 at 6:05 | comment | added | Girbot | That is an option but I was trying to find a way without having to edit existing code - being a bit idealistic :) | |
| Sep 26, 2016 at 21:06 | history | tweeted | twitter.com/StackSalesforce/status/780513987377164288 | ||
| Sep 26, 2016 at 20:51 | answer | added | o-lexi | timeline score: -1 | |
| Sep 26, 2016 at 20:50 | comment | added | Daniel Ballinger | What if you had a Custom Setting that you could flag to disable all the triggers, validation rules, workflows, etc... ? Just set it as the first part of the sandboxpostcopy class. They would still be active, but wouldn't actually do anything. | |
| Sep 26, 2016 at 19:50 | comment | added | Girbot | ah. nuts. Time to have a "play" I guess! | |
| Sep 26, 2016 at 19:48 | comment | added | Adrian Larson♦ |
I mean I don't think the SandboxPostCopy context supports callouts.
|
|
| Sep 26, 2016 at 19:47 | comment | added | Girbot | I am sure I have read on here there is a way of doing, maybe using github.com/afawcett/apex-toolingapi ? | |
| Sep 26, 2016 at 19:44 | comment | added | Adrian Larson♦ | Tooling API maybe? I don't think callouts are supported though. | |
| Sep 26, 2016 at 19:39 | history | asked | Girbot | CC BY-SA 3.0 |