Timeline for How to implement my de-dupe code into batch apex?
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 14, 2017 at 19:15 | vote | accept | Peter Noges | ||
| Feb 14, 2017 at 19:15 | |||||
| Feb 14, 2017 at 19:09 | comment | added | Peter Noges | @sfdcfox and Adrian - next time you two are in Palo Alto, happy hour is on me! Both of your answers are incredibly helpful. Thank you sfdcfox for the education here, i did not know those things. Adrian that's exactly what I need, but I asked the wrong question and sfdcfox helped illustrate that. Choosing his answer so that it rises to the top to help others who face similar confusion. | |
| Feb 14, 2017 at 18:45 | comment | added | Adrian Larson♦ | Right, that's what I'm saying, they'd have to go through the whole development/deployment cycle, so involving a proper class which implements any of those interfaces may be more effort than it's worth in the short term | |
| Feb 14, 2017 at 18:44 | comment | added | sfdcfox♦ | @AdrianLarson Yeah, the database and system interfaces you'd use to script queueable, schedulable, or batchable can't be implemented without actually having a compiled class saved in the database. You'll just either get compilation errors, or if you really force the issue, an Internal Server Error. | |
| Feb 14, 2017 at 18:39 | comment | added | Adrian Larson♦ | Sounds like a one-off job here where the priority is to get it done as quickly as possible. Nice efficiency tips though. And an interesting note about Queueable vs. Batchable. | |
| Feb 14, 2017 at 18:39 | history | answered | sfdcfox♦ | CC BY-SA 3.0 |