Its very hectic to debug when we have too many script statements. Most of the time when we apply System.debug in our code with many script statement we get :

*********** MAXIMUM DEBUG LOG SIZE REACHED ***********

I get frustrated with this and started rolling over the pdf which says there is a solution for this. Now if I want to see a specific line debug which is coming almost in the end of our code so I will simply write this where I want to get the debug in my code :

System.debug(Logginglevel.ERROR , ‘ ::::::: My Debug :::::::::::::’) ;  
And after this some steps to be done
  1. Create Debug logs from “Monitoring”
  2. Create Filters :
    • Database : NONE
    • Workflow : NONE
    • Validation : NONE
    • Callouts : NONE
    • Apex Code : ERROR
    • Apex Profiling : NONE
    • Visualforce : NONE
So when I execute my code only debug with Logginglevel.ERROR will be displayed.

(353)

Written by 

I am Sakthivel Madesh, a certified Salesforce Developer & Administrator working on Salesforce Technology since 2011. I am currently working in IBM Austraila as Sr. Salesforce Developer. I have worked on multiple technologies Like PHP, Java, Salesforce, I am very passionate about Salesforce and to earn 10 Salesforce Certification. I love Trailhead for learning Salesforce Skill and Become a Trailhead Ranger too. I Love to Learn & Share my Salesforce knowledge to Salesforce Learners/Beginner using My Blog and Salesforce Community.

Leave a Reply