In step 4, we searched for the JavaScript we would like to debug. If you are looking for your custom script manually, they usually sit under a folder with your organization URL followed by a subfolder with a number between curly brackets, as shown in the following screenshot:
In step 5, we set the breakpoint at the line where we would like the debugger to break.
In step 7, we inspected the values of an expression. We can also add it to the Watch list by clicking on the Add watch link under the value. Any changes to that expression will then be highlighted in the watch list.
In scenarios where your script is executed during the OnLoad event, consider using Telerik's Fiddler to intercept calls from Dynamics 365 to replace the JavaScript with an updated version until you are satisfied with the outcome, before going back to the usual channels.
Finally, in step 8 and step 9, we used the keyboard shortcuts to step over the breakpoint line or continued running the script. We can also use F11 to step into a function and Shift + F11 to step out of a function.