Timeline for How to bypass Validation logic in a Trigger
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 17, 2012 at 20:12 | comment | added | AMM | Good point, but still doesn't resolve MY need, unfortunately. The trigger will fire randomly (so to speak), so it has to allow bypass when it runs. YOUR solution is certainly good for FIRST INSERT of new leads, definitely. ;) Thanks. | |
| Oct 17, 2012 at 14:42 | comment | added | techtrekker | I've added the ISNEW() check, which means the validation rule will be skipped only when the Lead is inserted and had a Lead Source of 'Web to Lead' | |
| Oct 17, 2012 at 14:34 | comment | added | AMM | Even using Lead Source, though, it would be a permanent ban on the rule, yes? I mean, unless you have a way to do it selectively, Lead Source X would always avoid the rule, whereas the idea was to be able to avoid the rule "when needed". Am I missing something? I don't want to bypass a possible alternative. ;-) Thanks. | |
| Oct 17, 2012 at 8:24 | history | edited | techtrekker | CC BY-SA 3.0 |
added 19 characters in body
|
| Oct 16, 2012 at 19:27 | comment | added | Mohith Shrivastava | Custom validation rule will execute after the before triggers.Standard UI validations execute before triggers .Thanks | |
| Oct 16, 2012 at 19:24 | comment | added | techtrekker | The only thing is that if you use the Lead Source, and it is set to Web to Lead, you save yourself a new field. | |
| Oct 16, 2012 at 19:23 | history | edited | techtrekker | CC BY-SA 3.0 |
deleted 17 characters in body
|
| Oct 16, 2012 at 19:23 | comment | added | AMM | Good idea, though I'm going with a boolean check that will get Unchecked in the workflow after the fact (seen in Mohith's suggestion). Thanks! | |
| Oct 16, 2012 at 19:18 | history | answered | techtrekker | CC BY-SA 3.0 |