What and why​

SF Explorer 6.0.0 is out with new features:

• a refresh on the navigation with a description and an icon for each entry point
• boards that allows you to create interactive charts
• data cloud and marketing cloud support

What and why​

SF Explorer 5.0.0 is out with new features:

• Schema Builder on Steroids
• Open API Generator
• Rule engine tester
• Web app deployment

What and why​

SF Explorer 4.0.0 is out with a focus on:

• Improved performance
• Improved UX and a new SOQL Query Editor (based on VSCode)
• A new feature: Data Dictionary Generation (from the object manager)

What and why​

SF Explorer 3.0.0 is out with a focus on:

• A brand new approach to be able to define best practices on your metadata
• New capabilities to edit your data/metadata directly from SF Explorer

Demo​

SF Explorer 2.0.0 is out with a full rewrite targeting an improved user experience:

• Right click in your page to open explorer or use the extension icon
• non-intrusive: do not inject code unless you require it to do specific operations (like show LWC info): no more walking man in your page!
• taking advantage of the great chrome new side panel
• Show LWC info in your page
• Export to excel
• And more...

SF Explorer 0.3.0 is back to school with a full internal rewrite now using jsforce and a couple of interesting new features:

Security

Explore your org security model with an interactive UI to make the bridge between theory and practice

GraphQL

Browse your org using GraphQL and generate LWC starters accordingly

Usage

Explore chosen records child relation at once

But wait - what is Salesforce Explorer ?​

Salesforce Explorer is a productivity tool provided as a chrome extension intended for Salesforce administrators and developers. It contains features I needed on some of my previous assignments that I decided to package.

What is included ?​

Here is the list of the most important features provided:

Multi org

Connect to multiple orgs to browse and compare records across them.

Object Manager

Retrieve key information on the objects you use the most.

Explore Data

Chain requests and Query data across multiple orgs with ease

Explore Code

Extract JSDoc information from your LWCs and your Apex to generate a status report

Explore Omnistudio

Get an overview of your omniscripts, DataRaptors and your flexcards

Explore Products

Explore Insurance Products with their coverage, attributes, rules and dependencies

Interact with ChatGPT

Get Contextualized help with ChatGPT to facilitate your work.

Compare records

Compare any other record in your orgs such as Flexipages, accounts or Flows.

But why?​

Most of the time I started working on something because I needed it on my project and I could not find the capability in salesforce or I was not comfortable with the user experience.

How is it built?​

It is built with React, Typescript and React SLDS to provide a salesforce like UX experience.

Why not an Appexchange?​

Web extension architecture offers the following advantages

• First and foremost: No need to be admin of your org to install/use it!
• A single installation is enough for all your orgs
• React, Typescript, webpack and friends offer a better developer experience than lwc
• Interestingly you can access the tooling API from a web extension and in LWC to do the same you need to a configuration with a connected app which is more complex in my opinion

Is it open source?​

Not yet, but the plan is to make it open source - code needs to be cleaned and documented first.

Can you use it on your project?​

Yes please try it out and let me know what you think. You can provide feedback here

Is it secure?​

Yes, like for the appexchange, chrome makes a security review for chrome extension and it has been approved