ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Learn how Salesforce Batch Apex splits large datasets into chunks, the best‑practice workflow, a hands‑on example, and key trade‑offs that can save you from hitting governor limits.
How Database.Batchable splits million-record jobs into governor-limit-isolated chunks: the start/execute/finish contract, QueryLocator vs Iterable, batch sizing, and partial-failure handling with a worked example.
How to declare and read configuration in Salesforce using Custom Metadata Types, accessed in Apex without SOQL queries, plus limits and pitfalls to avoid.
A concise decision guide for choosing Salesforce Flow versus Apex triggers, with a comparison table, trade‑offs, and a validation example for updating an Opportunity when a Project is closed won.
Apex batch jobs often hit the 100‑SOQL‑query limit. This guide shows how to spot the symptom, identify the root cause with a concise table, run ordered checks, apply targeted fixes, and know when to raise the issue to a senior developer.
Learn how to implement a Cache Service wrapper in Apex to reduce SOQL consumption and avoid governor limits using Platform Cache Org and Session scopes.
Facing governor limits when updating thousands of records? Batch Apex splits work into 200-record chunks, keeping you within limits. This guide shows how to build, test, and monitor a batch that updates Account.Status, plus trade-offs you should know.
Goal The goal is to determine whether an @future method can see changes made to a record in the transaction that invoked it, such as those performed by a trigger or a DML operation. Constraints & Uncertainty @future methods run in a separate transaction, which means they do not inherit the data context of the calling transaction. Governor limits (e.g., 5
Goal: Process 200,000 records efficiently while staying within Salesforce governor limits. Constraints: Batch Apex can handle up to 50,000 records per batch and allows a configurable batchSize , but requires careful start/execute/finish handling to avoid CPU and heap limits. Queueable Apex limits each job to 200 records and the system to 50 queued jobs per 2
salesforce