{"id":4597,"date":"2015-06-27T01:25:54","date_gmt":"2015-06-27T01:25:54","guid":{"rendered":"http:\/\/www.jitendrazaa.com\/blog\/?p=4597"},"modified":"2015-06-27T01:58:58","modified_gmt":"2015-06-27T01:58:58","slug":"advance-apex-debugging-in-salesforce-and-best-practices-videos","status":"publish","type":"post","link":"https:\/\/www.jitendrazaa.com\/blog\/salesforce\/advance-apex-debugging-in-salesforce-and-best-practices-videos\/","title":{"rendered":"Advance Apex debugging in Salesforce and best practices – Videos"},"content":{"rendered":"

While developing applications on Force.com platform using Apex, I am sure you may have been in need of debugging your code. Salesforce being cloud platform, method to debug code is very different as compared to other programming languages. In this post we will discuss all about Apex code debugging, challenges, solutions and other best practices.<\/p>\n

\"Salesforce<\/a>
Salesforce Advance Apex debugging<\/figcaption><\/figure>\n

How many ways to debug Apex code<\/strong><\/p>\n

    \n
  1. Eclipse Force.com IDE<\/a><\/li>\n
  2. Debug log<\/a><\/li>\n
  3. Developer console<\/li>\n
  4. Fetch debug log using Tooling API<\/a><\/li>\n<\/ol>\n


    \nEclipse IDE vs developer console<\/strong><\/p>\n\n\n\n\n\t\n\n\t\n\t\n\t\n\t\n\t
    Eclipse<\/th>Developer Console<\/th>\n<\/tr>\n<\/thead>\n
    It can support Multiple Projects in Same workspace<\/td>We need to login to Salesforce first before navigating to Developer Console<\/td>\n<\/tr>\n
    Breakpoint supported in case of interactive debugging<\/td>Checkpoint is supported<\/td>\n<\/tr>\n
    Only Raw log is available with all detailed information<\/td>Raw log as well as other utilities like filtering are supported<\/td>\n<\/tr>\n
    It needs to be installed on desktop<\/td>Browser based<\/td>\n<\/tr>\n
    It does not has as many as features compared to Developer console<\/td>Developer console is future and with each release its growing. Currently performance analysis, Query execution plan , Save sequence and many more functionality supported<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n\n

    How to overcome with debug log size limit issue<\/strong><\/p>\n

    It is possible that you are trying to debug an application however you are hitting limit for debug log size. By default debug log size is 2MB, This 2MB would be last portion of file. Check if you have something like “Skipped xx bytes of detailed log<\/code>” in the very start of your log, If you find this statement that means debug log is truncated and it does not has all information.<\/p>\n

    It can be resolved by following below steps<\/p>\n

      \n
    1. Change debug log filters to only show intended Category. In my most of cases I choose only \u201cApex code\u201d with Level \u201cDebug\u201d and all other category \u201cNone\u201d.<\/li>\n
    2. If this still doesn\u2019t solves your problem and debug log is more than 2MB then as a best practice, instead of using System.debug(\u2018msg\u2019) , use System.debug(LogLevel.ERROR, \u2018msg\u2019) and set Level for \u201cApex Code\u201d as \u201cError\u201d.<\/li>\n
    3. Chances are very high that you are able to get your debug logs from Apex code. If you still have issue then set Log level for everything including Apex as \u201cNone\u201d and navigate to Apex class you want to debug and set log level explicitly for this class. Other way to set log level for individual class is by navigating to developer console, \u201cDebug | Change log level | Class and Trigger Trace Overrides | Add\u201d and select you Apex class or trigger (as shown in below image).<\/li>\n<\/ol>\n
      \"Salesforce<\/a>
      Salesforce – Setting log level for Apex class or trigger in Developer Console<\/figcaption><\/figure>\n

      Breakpoints (Interactive Apex Debugging)<\/strong><\/p>\n

      In case of breakpoint, execution of program stops at specified point and debugging can be resumed\u00a0line by line providing complete information on variables and other state of code at that time.<\/p>\n