How prevent deletion in Event delete trigger and update a field instead
up vote
1
down vote
favorite
Our Salesforce users are deleting Events from Salesforce due to our integration with Outlook. When a Meeting from Outlook is deleted, we want the corresponding Event record in Salesforce to be not deleted but change the status field (a custom field on Activity) to be marked as "Cancelled" instead.
Is it possible to not delete the Event from delete trigger?
trigger delete
add a comment |
up vote
1
down vote
favorite
Our Salesforce users are deleting Events from Salesforce due to our integration with Outlook. When a Meeting from Outlook is deleted, we want the corresponding Event record in Salesforce to be not deleted but change the status field (a custom field on Activity) to be marked as "Cancelled" instead.
Is it possible to not delete the Event from delete trigger?
trigger delete
2
What have you done so far?
– Carlos Naranjo
Nov 27 at 20:32
@CarlosNaranjo I didnt know where to start. Only thing I knew was, I can't stop a DML to happen which initiated the trigger. Hence, the question.
– Json Bourne Shell
Nov 28 at 2:16
add a comment |
up vote
1
down vote
favorite
up vote
1
down vote
favorite
Our Salesforce users are deleting Events from Salesforce due to our integration with Outlook. When a Meeting from Outlook is deleted, we want the corresponding Event record in Salesforce to be not deleted but change the status field (a custom field on Activity) to be marked as "Cancelled" instead.
Is it possible to not delete the Event from delete trigger?
trigger delete
Our Salesforce users are deleting Events from Salesforce due to our integration with Outlook. When a Meeting from Outlook is deleted, we want the corresponding Event record in Salesforce to be not deleted but change the status field (a custom field on Activity) to be marked as "Cancelled" instead.
Is it possible to not delete the Event from delete trigger?
trigger delete
trigger delete
asked Nov 27 at 20:29
Json Bourne Shell
10911
10911
2
What have you done so far?
– Carlos Naranjo
Nov 27 at 20:32
@CarlosNaranjo I didnt know where to start. Only thing I knew was, I can't stop a DML to happen which initiated the trigger. Hence, the question.
– Json Bourne Shell
Nov 28 at 2:16
add a comment |
2
What have you done so far?
– Carlos Naranjo
Nov 27 at 20:32
@CarlosNaranjo I didnt know where to start. Only thing I knew was, I can't stop a DML to happen which initiated the trigger. Hence, the question.
– Json Bourne Shell
Nov 28 at 2:16
2
2
What have you done so far?
– Carlos Naranjo
Nov 27 at 20:32
What have you done so far?
– Carlos Naranjo
Nov 27 at 20:32
@CarlosNaranjo I didnt know where to start. Only thing I knew was, I can't stop a DML to happen which initiated the trigger. Hence, the question.
– Json Bourne Shell
Nov 28 at 2:16
@CarlosNaranjo I didnt know where to start. Only thing I knew was, I can't stop a DML to happen which initiated the trigger. Hence, the question.
– Json Bourne Shell
Nov 28 at 2:16
add a comment |
2 Answers
2
active
oldest
votes
up vote
3
down vote
accepted
Yes you can do it using future / queuable APEX.
In the before delete trigger call the Future method which will undelete your event.
trigger EventTrigger on Event (before delete) {
MyEventUndeleterFutureClass.undeletEvent(JSON.serialize(Trigger.old));
}
Then future class
public class MyEventUnDeleterFutureClass {
@Future
public static void undeletEvent(String eventJson){
List<Event> EventList =(List<Event> ) JSON.deserialize(eventJson, List<Event> .class);
System.debug(EventList);
undelete EventList;
for(Event even : EventList ){
even.subject = even.subject+'Cancelled';
}
Update EventList;
}
}
thank you for the response. I will update here in case of issues.
– Json Bourne Shell
Nov 28 at 2:14
add a comment |
up vote
5
down vote
You cannot convert the delete
event into an update
. Once the DML operation has been started, you can block it (and potentially roll back the transaction) by adding an error on the record. That's unlikely to be what you want to do here.
Instead, I'd suggest you build your delete
trigger to create a new Event (or Task), copying fields from the deleted recording and applying the transformation you mention to mark the event as cancelled. You can insert new Event records from the delete trigger.
Why not let the event delete and then undelete it in future method?
– Pranay Jaiswal
Nov 27 at 21:03
@PranayJaiswal (1) I didn't think of it (clever idea!); (2) do you need to worry about bulk data processes that would blow out the Recycle Bin storage?
– David Reed
Nov 27 at 21:04
2
If deleting from outlook its still one delete at a time, even its bulk, the trigger handles it. The only blocker is, if its cascade delete , then delete triggers are not fired.
– Pranay Jaiswal
Nov 27 at 21:06
@DavidReed Thank you for the response.
– Json Bourne Shell
Nov 28 at 2:14
add a comment |
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
3
down vote
accepted
Yes you can do it using future / queuable APEX.
In the before delete trigger call the Future method which will undelete your event.
trigger EventTrigger on Event (before delete) {
MyEventUndeleterFutureClass.undeletEvent(JSON.serialize(Trigger.old));
}
Then future class
public class MyEventUnDeleterFutureClass {
@Future
public static void undeletEvent(String eventJson){
List<Event> EventList =(List<Event> ) JSON.deserialize(eventJson, List<Event> .class);
System.debug(EventList);
undelete EventList;
for(Event even : EventList ){
even.subject = even.subject+'Cancelled';
}
Update EventList;
}
}
thank you for the response. I will update here in case of issues.
– Json Bourne Shell
Nov 28 at 2:14
add a comment |
up vote
3
down vote
accepted
Yes you can do it using future / queuable APEX.
In the before delete trigger call the Future method which will undelete your event.
trigger EventTrigger on Event (before delete) {
MyEventUndeleterFutureClass.undeletEvent(JSON.serialize(Trigger.old));
}
Then future class
public class MyEventUnDeleterFutureClass {
@Future
public static void undeletEvent(String eventJson){
List<Event> EventList =(List<Event> ) JSON.deserialize(eventJson, List<Event> .class);
System.debug(EventList);
undelete EventList;
for(Event even : EventList ){
even.subject = even.subject+'Cancelled';
}
Update EventList;
}
}
thank you for the response. I will update here in case of issues.
– Json Bourne Shell
Nov 28 at 2:14
add a comment |
up vote
3
down vote
accepted
up vote
3
down vote
accepted
Yes you can do it using future / queuable APEX.
In the before delete trigger call the Future method which will undelete your event.
trigger EventTrigger on Event (before delete) {
MyEventUndeleterFutureClass.undeletEvent(JSON.serialize(Trigger.old));
}
Then future class
public class MyEventUnDeleterFutureClass {
@Future
public static void undeletEvent(String eventJson){
List<Event> EventList =(List<Event> ) JSON.deserialize(eventJson, List<Event> .class);
System.debug(EventList);
undelete EventList;
for(Event even : EventList ){
even.subject = even.subject+'Cancelled';
}
Update EventList;
}
}
Yes you can do it using future / queuable APEX.
In the before delete trigger call the Future method which will undelete your event.
trigger EventTrigger on Event (before delete) {
MyEventUndeleterFutureClass.undeletEvent(JSON.serialize(Trigger.old));
}
Then future class
public class MyEventUnDeleterFutureClass {
@Future
public static void undeletEvent(String eventJson){
List<Event> EventList =(List<Event> ) JSON.deserialize(eventJson, List<Event> .class);
System.debug(EventList);
undelete EventList;
for(Event even : EventList ){
even.subject = even.subject+'Cancelled';
}
Update EventList;
}
}
answered Nov 27 at 21:02
Pranay Jaiswal
12.3k32251
12.3k32251
thank you for the response. I will update here in case of issues.
– Json Bourne Shell
Nov 28 at 2:14
add a comment |
thank you for the response. I will update here in case of issues.
– Json Bourne Shell
Nov 28 at 2:14
thank you for the response. I will update here in case of issues.
– Json Bourne Shell
Nov 28 at 2:14
thank you for the response. I will update here in case of issues.
– Json Bourne Shell
Nov 28 at 2:14
add a comment |
up vote
5
down vote
You cannot convert the delete
event into an update
. Once the DML operation has been started, you can block it (and potentially roll back the transaction) by adding an error on the record. That's unlikely to be what you want to do here.
Instead, I'd suggest you build your delete
trigger to create a new Event (or Task), copying fields from the deleted recording and applying the transformation you mention to mark the event as cancelled. You can insert new Event records from the delete trigger.
Why not let the event delete and then undelete it in future method?
– Pranay Jaiswal
Nov 27 at 21:03
@PranayJaiswal (1) I didn't think of it (clever idea!); (2) do you need to worry about bulk data processes that would blow out the Recycle Bin storage?
– David Reed
Nov 27 at 21:04
2
If deleting from outlook its still one delete at a time, even its bulk, the trigger handles it. The only blocker is, if its cascade delete , then delete triggers are not fired.
– Pranay Jaiswal
Nov 27 at 21:06
@DavidReed Thank you for the response.
– Json Bourne Shell
Nov 28 at 2:14
add a comment |
up vote
5
down vote
You cannot convert the delete
event into an update
. Once the DML operation has been started, you can block it (and potentially roll back the transaction) by adding an error on the record. That's unlikely to be what you want to do here.
Instead, I'd suggest you build your delete
trigger to create a new Event (or Task), copying fields from the deleted recording and applying the transformation you mention to mark the event as cancelled. You can insert new Event records from the delete trigger.
Why not let the event delete and then undelete it in future method?
– Pranay Jaiswal
Nov 27 at 21:03
@PranayJaiswal (1) I didn't think of it (clever idea!); (2) do you need to worry about bulk data processes that would blow out the Recycle Bin storage?
– David Reed
Nov 27 at 21:04
2
If deleting from outlook its still one delete at a time, even its bulk, the trigger handles it. The only blocker is, if its cascade delete , then delete triggers are not fired.
– Pranay Jaiswal
Nov 27 at 21:06
@DavidReed Thank you for the response.
– Json Bourne Shell
Nov 28 at 2:14
add a comment |
up vote
5
down vote
up vote
5
down vote
You cannot convert the delete
event into an update
. Once the DML operation has been started, you can block it (and potentially roll back the transaction) by adding an error on the record. That's unlikely to be what you want to do here.
Instead, I'd suggest you build your delete
trigger to create a new Event (or Task), copying fields from the deleted recording and applying the transformation you mention to mark the event as cancelled. You can insert new Event records from the delete trigger.
You cannot convert the delete
event into an update
. Once the DML operation has been started, you can block it (and potentially roll back the transaction) by adding an error on the record. That's unlikely to be what you want to do here.
Instead, I'd suggest you build your delete
trigger to create a new Event (or Task), copying fields from the deleted recording and applying the transformation you mention to mark the event as cancelled. You can insert new Event records from the delete trigger.
answered Nov 27 at 20:38
David Reed
27.6k61746
27.6k61746
Why not let the event delete and then undelete it in future method?
– Pranay Jaiswal
Nov 27 at 21:03
@PranayJaiswal (1) I didn't think of it (clever idea!); (2) do you need to worry about bulk data processes that would blow out the Recycle Bin storage?
– David Reed
Nov 27 at 21:04
2
If deleting from outlook its still one delete at a time, even its bulk, the trigger handles it. The only blocker is, if its cascade delete , then delete triggers are not fired.
– Pranay Jaiswal
Nov 27 at 21:06
@DavidReed Thank you for the response.
– Json Bourne Shell
Nov 28 at 2:14
add a comment |
Why not let the event delete and then undelete it in future method?
– Pranay Jaiswal
Nov 27 at 21:03
@PranayJaiswal (1) I didn't think of it (clever idea!); (2) do you need to worry about bulk data processes that would blow out the Recycle Bin storage?
– David Reed
Nov 27 at 21:04
2
If deleting from outlook its still one delete at a time, even its bulk, the trigger handles it. The only blocker is, if its cascade delete , then delete triggers are not fired.
– Pranay Jaiswal
Nov 27 at 21:06
@DavidReed Thank you for the response.
– Json Bourne Shell
Nov 28 at 2:14
Why not let the event delete and then undelete it in future method?
– Pranay Jaiswal
Nov 27 at 21:03
Why not let the event delete and then undelete it in future method?
– Pranay Jaiswal
Nov 27 at 21:03
@PranayJaiswal (1) I didn't think of it (clever idea!); (2) do you need to worry about bulk data processes that would blow out the Recycle Bin storage?
– David Reed
Nov 27 at 21:04
@PranayJaiswal (1) I didn't think of it (clever idea!); (2) do you need to worry about bulk data processes that would blow out the Recycle Bin storage?
– David Reed
Nov 27 at 21:04
2
2
If deleting from outlook its still one delete at a time, even its bulk, the trigger handles it. The only blocker is, if its cascade delete , then delete triggers are not fired.
– Pranay Jaiswal
Nov 27 at 21:06
If deleting from outlook its still one delete at a time, even its bulk, the trigger handles it. The only blocker is, if its cascade delete , then delete triggers are not fired.
– Pranay Jaiswal
Nov 27 at 21:06
@DavidReed Thank you for the response.
– Json Bourne Shell
Nov 28 at 2:14
@DavidReed Thank you for the response.
– Json Bourne Shell
Nov 28 at 2:14
add a comment |
Thanks for contributing an answer to Salesforce Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsalesforce.stackexchange.com%2fquestions%2f240708%2fhow-prevent-deletion-in-event-delete-trigger-and-update-a-field-instead%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
2
What have you done so far?
– Carlos Naranjo
Nov 27 at 20:32
@CarlosNaranjo I didnt know where to start. Only thing I knew was, I can't stop a DML to happen which initiated the trigger. Hence, the question.
– Json Bourne Shell
Nov 28 at 2:16