Leverage Salesforce bookmarklets to enhance the productivity

Well, it will still try to go on that path. So, if google.com is open it will try to open- https://google.com/lightning/setup/SetupOneHome/home and we will get a 404 error. We could add logic in our JS to check if we are in a salesforce org(like check if the URL has ‘force.com’ in it) but that logic may not always work perfectly(force.com may be there in some non-salesforce org URL) and we will get 404 error.

Similarly, let’s open ‘Object Manager’ and ‘app’.

For the Object manager,

Drag and drop this link-

javascript: window.open('https://' + window.location.hostname + '/lightning/setup/ObjectManager/home', '_blank')

– Object Manager on the bookmark bar to quickly install this bookmarklet.

For the App, we can use- (This will just redirect to the last open salesforce app in our org)

Drag and drop the following link-

javascript: window.open('https://' + window.location.hostname + '/one/one.app', '_blank')

– on bookmark bar to quickly install this bookmarklet.

Let’s try to open the ‘Developer Console’.

If you see the developer console its hostname in the URL is slightly different from the salesforce org URL. But with the full might of JS at our disposal, we march ahead. We only need to replace ‘lightning.force.com’ with the path of the developer console. Again, the path is the same across all orgs, so one bookmark to rule them all!

Drag and drop this link-

javascript: window.open('https://' + window.location.hostname.replace('lightning.force.com', 'my.salesforce.com/_ui/common/apex/debug/ApexCSIPage', '_blank'))

– on the bookmark bar to quickly install this bookmarklet.

Extending this Idea

While I created bookmarks for the pages I need, you may create for other paths you find yourself visiting frequently. Suppose you frequently open the custom settings page in setup, you may create a bookmark like this-

and navigate directly to it, instead of typing ‘custom setting’ every time in the search bar of setup.

You may insert prompt() statements in the URL at places where you need input from the user. For example- we often put ids in salesforce org URLs to navigate to the record page. So, we can create an URL like-

It will prompt the user for Input and then automatically redirect to the record page in the currently open salesforce org with the given record id. No more manual meddling with URLs.