You're reading from Mastering Apex Programming A Salesforce developer's guide to learn advanced techniques and programming best practices for building robust and scalable enterprise-grade applications

Product type Paperback

Published in Nov 2023

Publisher Packt

ISBN-13 9781837638352

Length 394 pages

Edition 2nd Edition

Languages

Apex

Tools

Salesforce

Concepts

CRM

Author (1):

Paul Battisson

View More author details

Table of Contents (28) Chapters

Preface

1. Section 1: Triggers, Testing, and Security

2. Chapter 1: Common Apex Mistakes FREE CHAPTER

3. Chapter 2: Debugging Apex

4. Chapter 3: Triggers and Managing Trigger Execution

5. Chapter 4: Exceptions and Exception Handling

6. Chapter 5: Testing Apex Code

7. Chapter 6: Secure Apex Programming

8. Section 2: Asynchronous Apex

9. Chapter 7: Utilizing Future Methods

10. Chapter 8: Working with Batch Apex

11. Chapter 9: Working with Queueable Apex

12. Chapter 10: Scheduling Apex Jobs

13. Section 3: Integrations

14. Chapter 11: Integrating with Salesforce

15. Chapter 12: Using Platform Events

16. Chapter 13: Apex and Flow

17. Chapter 14: Apex REST and Custom Web Services

18. Chapter 15: Outbound Integrations – REST

19. Chapter 16: Outbound Integrations – SOAP

20. Chapter 17: DataWeave in Apex

21. Section 4: Apex Performance

22. Chapter 18: Performance and the Salesforce Governor Limits

23. Chapter 19: Performance Profiling

24. Chapter 20: Improving Apex Performance

25. Chapter 21: Performance and Application Architectures

26. Index

Why subscribe?

27. Other Books You May Enjoy

Summary

In this chapter, we discussed how we can best work to debug our Apex code when we have a bug or issue. We started by noting some of the differences between debugging Apex compared to other languages and platforms due to its cloud-centric execution model.

We then discussed the standard debugging life cycle for most developers, which involves a lot of switching between windows to get static debug logs to inspect. We looked at how we can improve this debug cycle, by first reproducing the bug in a test to (a) reduce our replication time and (b) provide us with a concrete way of ensuring that the bug has been fixed.

Following this, we discussed how we can aid ourselves by improving the way in which we configure the debug log filters within Salesforce to get access to the most relevant information. We then discussed the use of the SFDX CLI to stream these logs to the terminal and then further filter them using the tools provided by the command line. This provided us with a...