Hi Laura, Here, If field "Delete_Case__c == true" then delete a case.So your trigger will fire on After Insert or After Update.Try below code:
trigger CaseTrigger on Case (after insert , after update){
if(Trigger.isAfter){
if(Trigger.isInsert || Trigger.isUpdate){
Set<Id> setIds = new Set<Id>();
for(Case c :trigger.new){
if(c.Delete_Case__c == true){
setIds.add(c.id);
}
}
if(setIds.size()>0){
List<Case> listCaseToDelete = [Select Id from case where id in:setIds];
delete listCaseToDelete;
}
}
}
}
Please mark my answer as a solution, if it is really helpful.
trigger CaseDelete on Case (after insert , after update ) { List<Id> deleteList = new List<Id>(); for(Case c :trigger.new){ if(c.Delete_Case__c ==true){ deleteList.add(c.id); } } if(deleteList.size()>0){ delete [Select Id from case where id in:deleteList] ; }
trigger CaseTrigger on Case (after insert , after update )
{
Set<Id> setId = new Set<Id>();
for(Case c :trigger.new)
{
if(c.Delete_Case__c == true )
{
setId.add(c.id);
}
}
if(setId.size()>0)
{
List<Case> listCaseToDelete = [Select Id from case where id in:setId] ;
delete listCaseToDelete;
}
}
Trigger Best Practices | Sample Trigger Example | Implementing Trigger Framework
1) One Trigger Per Object A single Apex Trigger is all you need for one particular object. If you develop multiple Triggers for a single object, you have no way of controlling the order of execution if those Triggers can run in the same contexts
2) Logic-less Triggers If you write methods in your Triggers, those can’t be exposed for test purposes. You also can’t expose logic to be re-used anywhere else in your org.
4) Bulkify your Code Bulkifying Apex code refers to the concept of making sure the code properly handles more than one record at a time.
5) Avoid SOQL Queries or DML statements inside FOR Loops An individual Apex request gets a maximum of 100 SOQL queries before exceeding that governor limit. So if this trigger is invoked by a batch of more than 100 Account records, the governor limit will throw a runtime exception
6) Using Collections, Streamlining Queries, and Efficient For Loops It is important to use Apex Collections to efficiently query data and store the data in memory. A combination of using collections and streamlining SOQL queries can substantially help writing efficient Apex code and avoid governor limits
7) Querying Large Data Sets The total number of records that can be returned by SOQL queries in a request is 50,000. If returning a large set of queries causes you to exceed your heap limit, then a SOQL query for loop must be used instead. It can process multiple batches of records through the use of internal calls to query and queryMore
8) Use @future Appropriately It is critical to write your Apex code to efficiently handle bulk or many records at a time. This is also true for asynchronous Apex methods (those annotated with the @future keyword). The differences between synchronous and asynchronous Apex can be found
9) Avoid Hardcoding IDs When deploying Apex code between sandbox and production environments, or installing Force.com AppExchange packages, it is essential to avoid hardcoding IDs in the Apex code. By doing so, if the record IDs change between environments, the logic can dynamically identify the proper data to operate against and not fail
trigger DeleteCases on Case (after insert , after update ) { Set<Id> Case_ID = new Set<Id>(); for(Case case_obj :trigger.new) { if(case_obj.Delete_Case__c == true ) { Case_ID.add(case_obj.id); } } if(Case_ID.size()>0) { List<Case> lst_case_del = [Select Id from case where id in:Case_ID] ; delete lst_case_del; } }
Hi Laura, Here, If field "Delete_Case__c == true" then delete a case.So your trigger will fire on After Insert or After Update.Try below code:
trigger CaseTrigger on Case (after insert , after update){
if(Trigger.isAfter){
if(Trigger.isInsert || Trigger.isUpdate){
Set<Id> setIds = new Set<Id>();
for(Case c :trigger.new){
if(c.Delete_Case__c == true){
setIds.add(c.id);
}
}
if(setIds.size()>0){
List<Case> listCaseToDelete = [Select Id from case where id in:setIds];
delete listCaseToDelete;
}
}
}
}
Please mark my answer as a solution, if it is really helpful.
Hello all, I'm using this trigger, but am not able to deploy it as I need to have a test class/code coverage. I've been googling for a sample I can work from, but have not been successful. Please help.
Here, If field "Delete_Case__c == true" then delete a case.So your trigger will fire on After Insert or After Update.Try below code: Please mark my answer as a solution, if it is really helpful.
Regards,
Akshay
All Answers
Please use this code .
trigger CaseDelete on Case (after insert , after update ) {
List<Id> deleteList = new List<Id>();
for(Case c :trigger.new){
if(c.Delete_Case__c ==true){
deleteList.add(c.id);
}
}
if(deleteList.size()>0){
delete [Select Id from case where id in:deleteList] ;
}
}
I will recommend to learn Trigger with below trailhead module
1) https://trailhead.salesforce.com/modules/apex_triggers
Please try below code Please check below post for trigger Best Pratice
1) http://amitsalesforce.blogspot.com/2015/06/trigger-best-practices-sample-trigger.html
2) https://developer.salesforce.com/page/Trigger_Frameworks_and_Apex_Trigger_Best_Practices
Trigger Best Practices | Sample Trigger Example | Implementing Trigger Framework
1) One Trigger Per Object
A single Apex Trigger is all you need for one particular object. If you develop multiple Triggers for a single object, you have no way of controlling the order of execution if those Triggers can run in the same contexts
2) Logic-less Triggers
If you write methods in your Triggers, those can’t be exposed for test purposes. You also can’t expose logic to be re-used anywhere else in your org.
3) Context-Specific Handler Methods
Create context-specific handler methods in Trigger handlers
4) Bulkify your Code
Bulkifying Apex code refers to the concept of making sure the code properly handles more than one record at a time.
5) Avoid SOQL Queries or DML statements inside FOR Loops
An individual Apex request gets a maximum of 100 SOQL queries before exceeding that governor limit. So if this trigger is invoked by a batch of more than 100 Account records, the governor limit will throw a runtime exception
6) Using Collections, Streamlining Queries, and Efficient For Loops
It is important to use Apex Collections to efficiently query data and store the data in memory. A combination of using collections and streamlining SOQL queries can substantially help writing efficient Apex code and avoid governor limits
7) Querying Large Data Sets
The total number of records that can be returned by SOQL queries in a request is 50,000. If returning a large set of queries causes you to exceed your heap limit, then a SOQL query for loop must be used instead. It can process multiple batches of records through the use of internal calls to query and queryMore
8) Use @future Appropriately
It is critical to write your Apex code to efficiently handle bulk or many records at a time. This is also true for asynchronous Apex methods (those annotated with the @future keyword). The differences between synchronous and asynchronous Apex can be found
9) Avoid Hardcoding IDs
When deploying Apex code between sandbox and production environments, or installing Force.com AppExchange packages, it is essential to avoid hardcoding IDs in the Apex code. By doing so, if the record IDs change between environments, the logic can dynamically identify the proper data to operate against and not fail
Let us know if this will help you
trigger DeleteCases on Case (after insert , after update )
{
Set<Id> Case_ID = new Set<Id>();
for(Case case_obj :trigger.new)
{
if(case_obj.Delete_Case__c == true )
{
Case_ID.add(case_obj.id);
}
}
if(Case_ID.size()>0)
{
List<Case> lst_case_del = [Select Id from case where id in:Case_ID] ;
delete lst_case_del;
}
}
Hope it will help you:)
Choose as best answer
Thanks
Here, If field "Delete_Case__c == true" then delete a case.So your trigger will fire on After Insert or After Update.Try below code: Please mark my answer as a solution, if it is really helpful.
Regards,
Akshay
Thanks for selecting my answer as a best answer. It's my pleasure to help you!
Regards,
Akshay
I'm using this trigger, but am not able to deploy it as I need to have a test class/code coverage. I've been googling for a sample I can work from, but have not been successful. Please help.
Thanks!
Natalie