Salesforce introduced the fastest way to write SOQL statements, the SOQL Query Builder. SOQL Query Builder is the Visual Studio Code Extension that enables you to write, execute SOQL statements write inside your project workspace. Not only that, this tool will allow you to download the query result in either CSV or JSON format.How to install SOQL Query BuilderOnce you open the Visual Studio Code, search for SOQL in Marketplace. From there install the SOQL extension from Salesforce. After installation, it is always recommended to restart VS Code. Below is the screenshot How to use SOQL Query BuilderAfter installation, all your soql files will be stored under the folder scripts -> soql. You can save your own soql commands, just make sure the extension of the file is .soql.Below is the example where I have opened account.soql file and executed the statement. As you can see, with this new tool, we have the opportunity to do everything we are doing today with workbench w.r.t. executing soql statements. Also, you can download the query result in either CSV or JSON format.Youtube VideoVideo Link: https://www.youtube.com/watch?v=LG13jPWYqVwReference...Read More
Category: VS Code
Writing test classes to cover both positive, negative, and bulkified scenarios are always the best practices that each developer should follow. While writing test classes, our approach should be to cover as much as code and all the scenarios. There is a restriction from Salesforce that if there is not enough coverage (75%) for the code, then Salesforce will not allow you to deploy your code to production.So identifying the code coverage is very important. Now there are multiple ways we can get to know the code coverage like – Setup menu, Developer Console, SOQL Query, Salesforce CLI, or Salesforce extension in Visual Studio Code. With so many options there comes the difficulties. Each option presents the code coverage in a different way and more importantly, each option calculates code coverage in a different way. This always creates confusion. For example, when a developer writes the test class and executes that from CLI, it provides the code coverage, let’s say 90%, which should be good enough to deploy the code into Production. But while deployment, the code coverage came down to 50%, and thus deployment stops. The reason for this drop in code coverage is that while deploying code coverage is calculated at the org level i.e. percentage of coverage for that class across the org.To solve this problem, Salesforce comes up with the Enhanced Code Coverage option. With...Read More
- Salesforce API – New and Changed Objects
- New Video – Mastering Google Cloud Storage Part 3 – Diving Deep into Retention Policies!
- Salesforce Winter 24 Release | Sharing Related Enhancements
- How To Perform Enhanced List Sorting with Comparator Interface
- Unleashing The Power of AI: Salesforce and Tableau GPT