Salesforce advanced Code searcher
By using the advanced quick find you can get your code few clicks shorter. Also, you can search any string your code
We are now on Lightning!!!!
Using this extension you can search your code components your salesforce instance:
1) apex Classes
2) Apex Triggers
3) visualforce Pages
4) Visualforce Components
5) Lighting Component
In addition to the above you can use this extension to jump to classes / pages / triggers from the advanced quick find section on the left hand side.
How to make it work in Lightning:
1) We embed the extension in the setup page. Please navigate to the setup home page where you can find the extension injected in the right.
2) You need to authorize (this is a one time activity) for the application to make the API calls.
3) On clicking the button, you will be navigated to the Salesforce to authorize. Once you have successfully completed the authorization, you will be redirected back to the home page.
4) Once this is done, all the functionalities will be enabled.
How to use it (Classic):
Both the below section get added in the set-up pages, so this is only useful for developers and Admins, this tool will not make any sense for salesforce users.
1) Advanced Quick Find section:This part gets added in side navigation bar on all set-up pages. Select the code component that you want to go to, then start typing the name of the code,an autocomplete suggestion pops up, select the one that you want to go to.
2) Developer Utilities:
2.1) This component get added in force.com home page only. Let's say you want to know where you have hard-coded a profile name in your code, like if(profile.name =='sys Admin'){//you're doing something}. Right now to find this out you have to either go thru all the code individually or create a force.com project in eclipse and then search there. There's no way we can do this directly in salesforce. This string search will help you do that. You have to check the code components in which you want to search the code, enter a string in the input text field and hit enter. You will be presented with a list of code components where the string is used.
2.2 ) Code Coverage Extract: You can View and download the code coverage in your org.
2.3 ) This extension now allows you to lint the lightning code via the Lightning Linter tab.
2.4 ) You can now run PMD against your code
2.5 ) Added a new tab which will allow the users to view the record and its child information .
update 1.26
GraphQL Explorer is now available
update 1.22
Improved the static code analysis functionality
update 1.20
Moved away from heroku to firebase functions.
update 1.17
LWC editor now has linting capabilities.
update 1.15
Added the LWC Editor with Autocompleting for html & xml files.
update 1.10
Added the ability to get the record Information by just giving the record Id.
update 1.8, 1.9
Added support for the application to work on lightning
update 1.4.2
Added support for Custom label
Addes support for Apex PMD
Update 1.1.1
Expanded the quick search scope to Email Templates, Validation Rule, Workflow Rule, Custom Object
Added edition checks.
Update 1.2
Update the UI to be more in sync with Lightning
Update 1.3
Added Code coverage Extract section allowing user to view and download the code coverage.
Update 1.3.3:
UPdated the cookie issue.
NOTE:
1) Salesforce's REST API is used to accomplish the above functionalities
Update 1.3.5
1) Added support to delete all the Debug logs
2) Added a button on traceflag to renew the startDate / expiration date.
update 1.4:
1) Added functionality to support linting of lightning components
Latest reviews
All of the sudden disappeared, had that reinstalled numerous times, however no luck :( want this back :(
Not working
Got it working in Windows after Summer '25 release per other reviewers suggestions; however, on Mac, it doesn't load in Lightning. I hope this gets fixed so I can change my review.
Joe Smith I only found 1 line, any other tricks?
I found a fix for the URI Mismatch error. When you run into the page with the following error: Error: error=redirect_uri_mismatch&error_description=redirect_uri%20must%20match%20configuration 1. Press F12 2. Go to Console 3. Look for the following two lines 1st: chrome-extension://token1/callback.html 2nd: chrome-extension://token2/callback.html 4. copy the token2 string between "chrome-extension://" and "/callback.html" in the second line 5. replace the two instances of token1 in your url bar with token2 and press Enter
Broken since Winter 25'. Please fix. everyone email [email protected] to get it fixed.
I made changes as per Alan comments but getting error while authorising the developer org by selecting Developer in Org Type. Error: error=redirect_uri_mismatch&error_description=redirect_uri%20must%20match%20configuration
HUGE shoutout to Alan Garcia (alnandr) for the temp fix - THAAANNNKKKK YOOOOUUUU - we are back in business
I've never written a review but didn't realize how much I needed this extension until it wasn't working. Shoutout to Alan Garcia (alnandr) for posting the fix, I can confirm it works.
This extension is still fully functional, the issue is that Salesforce changed the name of the setup header element in the Spring '25 release that caused the injection to break. To anyone reading this who wants to get the advanced code searcher to work again in the meantime until the developer pushes an update, follow these steps: 1. Uninstall the extension from Chrome either from the nav bar or from chrome://extensions 2. Use a "CRX Extractor/Downloader" tool extension to download this Chrome extension as a ZIP file. 3. Extract the ZIP file contents to a folder somewhere you'll keep it long-term (i.e., Documents folder). 4. Open the contentScript_l.js file in the root directory using a text editor or IDE like VS Code. 5. On lines 16 and 29, replace ".onesetupHelpBanner" with ".onesetupSetupHeader" and save the file. 6. Navigate to chrome://extensions in your browser and enable developer mode. 7. Select "Load unpacked" and choose the extracted root directory from step 2. 8. Load Salesforce Setup in Lightning again and voila, the extension works again! Hope this helps everyone :)
After the new release the extension's UI disappeared. Please fix it urgently.
I gave it a 5 because I love this extension. It doesn't work for me any longer. Maybe Winter 2025 release caused the issue. Please fix.
Not working anymore
Was working very well. Not working now. Kindly check and fix
Was working very well. Not working now. Last saw it working on Feb 2025
Was working very well. Not working now. Last saw it working on Feb 28th
No longer works as of March 2, 2025
Whenever I try to authorize, I get this error: This page has been blocked by Chrome ERR_BLOCKED_BY_CLIENT Version - 1.30 Was a great extension to use. Chrome has ruined everything.
Was working so well but not it doesn't work :(
Extension is not working in my system.
This is a great tool. It doesn't work in our lower environments as the setup url has been updated to my.salesforce-setup.com. Could you please support these as well? Is there a similar tool that I could use?
Hi, This is a great tool. It doesn't work in our lower environments as the setup url has been updated to my.salesforce-setup.com. Could you please support these as well? Is there a similar tool that I could use? Thanks Anuj
ver good
This extension is not working for me after salesforce org URL is updated to : salesforce-setup.com If there is any solution, please suggest.
With some Salesforce orgs moving to a "salesforce-setup.com" url for Setup pages in Lightning, the extension's allowed sites needs to be updated to continue working. how to make that update working?
This extension has been a huge help! With some Salesforce orgs moving to a "salesforce-setup.com" url for Setup pages in Lightning, the extension's allowed sites needs to be updated to continue working.
Unable to login through "Use org domain for login"
Great tool! Having the LWC Editor in-browser is awesome! The code search is super handy and the GraphQL is a bonus. Thank you very much!
Hi, This tool is really great, but from today I am receiving weird error when I try search piece of code in Apex Classes (Tab - Search Code). Some error occured while query for data TypeError: Cannot read properties of undefined (reading 'records') Are you able to check what is wrong?
Hi, This tool is really great, but from today I am receiving weird error when I try search piece of code in Apex Classes (Tab - Search Code). Some error occured while query for data TypeError: Cannot read properties of undefined (reading 'records') Are you able to check what is wrong?
But how can I save my changes made with the LWC editor?
But how can I save my changes made with the LWC editor?
LWC editor is an outstanding feature Salesforce should have had. Thank you a lot!!
LWC editor is an outstanding feature Salesforce should have had. Thank you a lot!!
Great work. It works perfect to develop LWC! Please add bracket opening closing indications and also Provide insight if file is saved or not otherwise everything is perfect
Great work. It works perfect to develop LWC! Please add bracket opening closing indications and also Provide insight if file is saved or not otherwise everything is perfect
Great tool for SF Developers
Great tool for SF Developers
we were able to find some code verbose quickly with this
we were able to find some code verbose quickly with this
Does everything it says really well, loved the work
Does everything it says really well, loved the work
Great Tool ... I love this
Great Tool ... I love this
Great Tool! I used it all the time but it stopped working. I hope it gets fixed!
Great Tool! I used it all the time but it stopped working. I hope it gets fixed!
Very useful and handy tool to edit LWC components in a go
Very useful and handy tool to edit LWC components in a go
It is more useful tool to search Apexclass, Page, Trigger,workflows, Email templates,Validation Rules,Static Resource..Well Done Sameer...Again More improvement here...
It is more useful tool to search Apexclass, Page, Trigger,workflows, Email templates,Validation Rules,Static Resource..Well Done Sameer...Again More improvement here...
