This extension can be used to find the references of a particular search text on the SFDC metadata and generate a readable excel report.
Features
Commands:
SFMScanner: Scan Metadata
Helps to retrieve all the references of the search strings that user inputs from the selected metadata folder which contains all the Salesforce metadata files.
SFMScanner: Scan Picklists
Helps to retrieve all the picklist fields and their values, along with Global value set and standard value sets from the selected metadata folder.
Steps:
Launch the extension by (Windows) Ctrl+Shift+P and typing any of the above commands
SFMScanner: Scan Metadata
Select the Metadata folder (Github Repository or SFDX Project with retrived metadata), suggested to select the src folder if it is repository or directly the main/default folder if it is a SFDX project.
Select the folder to store the Output file/report.
Input the SearchString/s
For example: If you want to search for a field reference enter field API name --> FieldAPIName__c
To make logic search for multiple texts or fields concat the values with || --> FieldAPIName1__c||FieldAPIName2__c||Status||Health Care
Hardcode Value Check > User gets a pop up asking - "Do you want to check for hardcoded value? *Works well with field reference search." Yes / No
Selecting Yes will trigger a logic to check if the identified reference has a hardcoded value, this option works well with Field API searches
For Example - If you are searching for FieldAPIName__c, the same field is referenced on a Flow decision element equated with a Hardcoded value, then in the output report user will see a column "Contains Hardcoded Value" with value set to True.
User gets a pop up asking - "Do you want to include file type filter?" Files / Folders / No
a. Selecting Files user can specify the file types that the user wants to restrict logic to search.
For Example - The Metadata folder can have multiple file/metadata types like Fields, Layout, Flow, Apex, trigger, approvalprocess etc. If user wants to perform the search only on Flow and Apex metadata, then user can input something like
.flowxml,*.cls
b. Selecting Folders user will be provided with an Input box defaulted with all the folders from the selected root folder in step 1 as a comma separated value. User can specify what folders should be considered for the reference search.
Once all the above steps are completed, Logic start searching for the Searching Text/s provided.
SFMScanner: Scan Picklists
Select the Metadata folder (Github Repository or SFDX Project with retrieved metadata)
Select the folder to store the Output file/report.
Requirements
NA
Extension Settings
NA
Known Issues
The Hardcode check works well only with Field API references
Release Notes
1.0.0
Working with Markdown
You can author your README using Visual Studio Code. Here are some useful editor keyboard shortcuts:
Split the editor (Cmd+\ on macOS or Ctrl+\ on Windows and Linux)
Toggle preview (Shift+Cmd+V on macOS or Shift+Ctrl+V on Windows and Linux)
Press Ctrl+Space (Windows, Linux, macOS) to see a list of Markdown snippets
