Great session, since the User is not obstructed with an ERROR but the Exception are logged, what is the proper method to inform the User of the failure?
Thanks to Apex Hours and Meera for this wonderful session. The video is very informative and full of demos related to real word scenarios. Is there any way we can get the ppt? That will be very helpful. Thanks again.
I think that there is a correction. We can throw standard built in exceptions. Please correct me if my understanding is wrong //Sample code CalloutException e = new CalloutException(); e.setMessage('This is a constructed exception!'); throw e;
@samir khan yes we can throw standard exception, but point is to log the exception in a custom object, so that we can view the database entry later. So we create a separate object. Major issue comes when the it is a dml exception, your business logic (like other insert update) are usually allOrNone so when that fail, your exception logs dml also fails.
@@70samirkhan yes,you are correct. We can trow standard exceptions. I created a generic custom Exception for throwing all kind of exception with a custom message which can be even accessed from flows.
Check this post for code www.apexhours.com/exception-handling-using-platform-events/
Thanks for sharing knowledge. Very informative session.
Glad it was helpful! Keep watching
awesome thanks for your efforts
Our pleasure! Keep watching. Please share recording with your friends
Can we perfom similar logic for Logging the other levels of type Info, Warning etc ?
Awesome session Meera 😊
Thank you 🙂
Great session, since the User is not obstructed with an ERROR but the Exception are logged, what is the proper method to inform the User of the failure?
You can get a feeling of what quality an architect is when they say something like "second parameter, or variable in the list"
Thanks to Apex Hours and Meera for this wonderful session. The video is very informative and full of demos related to real word scenarios. Is there any way we can get the ppt? That will be very helpful. Thanks again.
check apexhours.com site
Can we log using platform events of type INFO, Warning etc?
Yes
Can we not achieve partial transaction using database.insert? @apexhours
Ok i get it now, its the 2nd scenario where platform events are really helpful to come around savepoint business logic
Let us know if you still more details
I think that there is a correction. We can throw standard built in exceptions. Please correct me if my understanding is wrong
//Sample code
CalloutException e = new CalloutException(); e.setMessage('This is a constructed exception!');
throw e;
@samir khan yes we can throw standard exception, but point is to log the exception in a custom object, so that we can view the database entry later.
So we create a separate object.
Major issue comes when the it is a dml exception, your business logic (like other insert update) are usually allOrNone so when that fail, your exception logs dml also fails.
@@70samirkhan yes,you are correct. We can trow standard exceptions. I created a generic custom Exception for throwing all kind of exception with a custom message which can be even accessed from flows.
Hello Can any one help providing guide for rollback in salesforce
We will post soon
Hi
Could you please tell best source for Salesforce vlocity
Only Vlocity University. Its a closed program no public content is available
@@apexhours thanks
Keep watching and share with your friends