Scribd Logo
Upload

Welcome to Scribd!

  • 108 views

    Using The Developer Console To Execute Apex Code

    Uploaded by

    ksr131
    The document discusses using the Developer Console to execute Apex code and view the results in the Log Inspector. It provides steps to open an anonymous window, enter a debug statement to print "Hello World", and execute the code. The Log Inspector is then used to view events from executing the code, including the USER_DEBUG indication for the debug statement. Additional tips are provided on filtering the log to only show debug events. The document aims to demonstrate successfully executing code and viewing results in the Developer Console and Log Inspector.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd

    Using The Developer Console To Execute Apex Code

    Uploaded by

    ksr131
    108 views5 pages
    The document discusses using the Developer Console to execute Apex code and view the results in the Log Inspector. It provides steps to open an anonymous window, enter a debug statement to print "Hello World", and execute the code. The Log Inspector is then used to view events from executing the code, including the USER_DEBUG indication for the debug statement. Additional tips are provided on filtering the log to only show debug events. The document aims to demonstrate successfully executing code and viewing results in the Developer Console and Log Inspector.

    Original Description:

    Developer Console

    Original Title

    Using the Developer Console to Execute Apex Code

    Copyright

    © © All Rights Reserved

    Available Formats

    DOCX, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    The document discusses using the Developer Console to execute Apex code and view the results in the Log Inspector. It provides steps to open an anonymous window, enter a debug statement to print "Hello World", and execute the code. The Log Inspector is then used to view events from executing the code, including the USER_DEBUG indication for the debug statement. Additional tips are provided on filtering the log to only show debug events. The document aims to demonstrate successfully executing code and viewing results in the Developer Console and Log Inspector.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Download as docx, pdf, or txt
    108 views5 pages

    Using The Developer Console To Execute Apex Code

    Uploaded by

    ksr131
    The document discusses using the Developer Console to execute Apex code and view the results in the Log Inspector. It provides steps to open an anonymous window, enter a debug statement to print "Hello World", and execute the code. The Log Inspector is then used to view events from executing the code, including the USER_DEBUG indication for the debug statement. Additional tips are provided on filtering the log to only show debug events. The document aims to demonstrate successfully executing code and viewing results in the Developer Console and Log Inspector.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Download as docx, pdf, or txt
    of 5

    Using the Developer Console to

    Execute Apex Code


    The Developer Console can look overwhelming, but its just a collection of tools
    that help you work with code. In this lesson, youll execute Apex code and view
    the results in the Log Inspector. The Log Inspector is a useful tool youll use
    often.
    1.

    Click Debug | Open Execute Anonymous Window or CTRL+E.

    2.

    In the Enter Apex Code window, enter the following


    text: System.debug( 'Hello World' );

    System.debug() is like using System.out.println() in Java (or printf() if youve been

    around a while ;-). But, when youre coding in the cloud, where does the
    output go? Read on!
    3.

    Deselect Open Log and then click Execute.

    Every time you execute code, a log is created and listed in the Logs panel.

    Double-click a log to open it in the Log Inspector. You can open multiple logs at a
    time to compare results.
    Log Inspector is a context-sensitive execution viewer that shows the source of
    an operation, what triggered the operation, and what occurred afterward. Use
    this tool to inspect debug logs that include database events, Apex processing,
    workflow, and validation logic.
    The Log Inspector includes predefined perspectives for specific uses.
    Click Debug | Switch Perspective to select a different view, or click CTRL+P to
    select individual panels. Youll probably use the Execution Log panel the most. It
    displays the stream of events that occur when code executes. Even a single
    statement generates a lot of events. The Log Inspector captures many event
    types: method entry and exit, database and web service interactions, and
    resource limits. The event type USER_DEBUG indicates the execution of
    a System.debug() statement.

    1.

    Click Debug | Open Execute Anonymous Window or CTRL+E and


    enter the following code:
    1
    2
    3

    System.debug( 'Hello World' );


    System.debug( System.now() );
    System.debug( System.now() + 10 );

    3.

    Select Open Log and click Execute.

    4.

    In the Execution Log panel, select Executable. This limits the display to
    only those items that represent executed statements. For example, it filters
    out the cumulative limits.

    5.

    To filter the list to show only USER_DEBUG events, select Debug Only or
    enter USER in the Filterfield.

    The filter text is case sensitive.

    Congratulationsyou have successfully executed code on


    the Force.com platform and viewed the results!

    Tell Me More...
    Help in the Developer Console
    To learn more about the Developer Console, click Help | Help Docs in
    the Developer Console.
    Anonymous Blocks
    The Developer Console allows you to execute code statements on the fly.
    You can quickly evaluate the results in the Logs panel. The code that you
    execute in the Developer Console is referred to as an anonymous block.
    Anonymous blocks run as the current user and can fail to compile if the
    code violates the users object- and field-level permissions. Note that this
    isnt the case for Apex classes and triggers.

    https://developer.salesforce.com/docs/atlas.enus.apex_workbook.meta/apex_workbook/apex1_2.htm

    You might also like