Tip #570: Remote debugging in CRM with vorlon.js

Our resident visual effects tipster asked me the other day if I had any experience with using vorlon.js in CRM. I didn’t as I never heard of it. But since someone somewhere some time ago pointed out that these days <random noun>.js is probably a valid javascript library, I decided to take a look.

As it turns out, vorlon.js is a very cool

An open source, extensible, platform-agnostic tool for remotely debugging and testing your JavaScript. Powered by node.js and socket.io

Steps to enable vorlon for your CRM:

  1. Install node and npm. Easiest way to do it is to use PowerShell
    install-package -name nodejs
    install-package -name npm
  2. CRM won’t allow loading anything over http and we’ll need a certificate that we can generate ourselves using openssl.
    install-package -name "openssl.light"
    openssl genrsa -des3 -out server.key 1024
    openssl req -new -key server.key -out server.crt
    copy server.* c:\temp
  3. To make browsers to trust our dodgy certificate, import server.crt into Trusted Root Certification Authorities store (e.g. using mmc certificate snapin)
  4. Install vorlon
    npm i -g vorlon
  5. Modify server/config.json to enable ssl
        "useSSL": true,
        "SSLkey": "c:/temp/server.key",
        "SSLcert": "c:/temp/server.crt",
  6. And run it
  7. Open browser and point to https://localhost:1337. We have a lift off but now what?
  8. Create an html web resource and insert it into any CRM form
        <p>Vorlon lives here</p>
  9. Load that form
    Vorlon host on CRM Form
  10. And here you have it!
  11. Object explorer in Vorlon

  12. You can now use console, for example, peek at the data
    Look at the data with Vorlon

Big deal, you say, because you can use magic F12 and achieve the same result? Well, yes, except all of the above works remotely, e.g. you can debug stuff on the user’s machine over the network.

Early days, of course, few additional notes to get you going:

  • DOM explorer is not very useful as its root is at the resource level. Injecting vorlon into CRM window is probably an option to consider
  • Create delayed load to debug only when needed. (See vorlon.js documentation for more details and options)
    <!-- load without autostart -->
    <script src=
    <!-- bind this to a button on command bar -->
  • Last but not least: use at your own risk, contains small parts, choking hazard, swim between the flags. Not tested on animals, children or CRM 2011.

Leave a Reply

Your email address will not be published. Required fields are marked *