Mastering Salesforce: Step by Step

 Object -Level & Field-Level Security (CRUD/FLS) 💬 In plain words:  Two locks on data: object-level (can you touch Accounts at all — Create/Read/Update/Delete) and field-level (okay, but can you see the Salary field?). Sharing decides WHICH records; CRUD/FLS decides WHAT you can do with the object and its fields. 📌 Example:  Asha can see the Candidate object (object-level ✓) but the Salary field is hidden from her profile (field-level ✗). She opens the record fine — the Salary column is simply not there, even in reports and the API. Concept CRUD (object permissions) and FLS (field permissions) are granted via profiles/permission sets and are enforced automatically in the standard UI, standard controllers, and Lightning Data Service — but NOT automatically in Apex, which runs in system mode by default on API v66 and earlier (from v67, user mode is the default — see 3.7). In older code Apex must opt in: SOQL with WITH USER_MODE, DML with 'as user', or ...

Introduction : In Salesforce development, Data Manipulation Language (DML) operations are fundamental for interacting with the database. While working with DML statements in Apex, it's essential to understand the various exceptions that can occur during the execution of these operations. In this blog post, we will explore common DML exceptions in Salesforce Apex and how to handle them effectively. Table of Contents: 1. Introduction 2. What are DML Operations? 3. Common DML Exceptions    a. DMLException    b. LimitException    c. MixedDmlException    d. InsufficientPrivilegesException 4. Handling DML Exceptions    a. Try-Catch Blocks    b. Exception Methods    c. Custom Error Handling 5. Best Practices for DML Exception Handling 6. Conclusion What are DML Operations? Data Manipulation Language (DML) operations in Salesforce Apex are used to create, update, delete, and retrieve records in the Salesfor...