salesforce-developer

Collect all record IDs into a Set before any loop, run a single SOQL query outside the loop, and delegate logic to a handler class rather than putting code in the trigger body. Never execute SOQL or DML inside a for loop, as this violates governor limits at scale.

Use Batch Apex when processing more than 10,000 records, since it handles up to 50 million records via QueryLocator. Use Queueable for job chaining and complex async logic with smaller datasets, and Future methods only for simple callouts.

Parent-to-child uses @api public properties, child-to-parent uses CustomEvent dispatch, and sibling or cross-page communication uses Lightning Message Service with a message channel. LMS requires subscribing in connectedCallback and unsubscribing in disconnectedCallback.

Synchronous transactions allow 100 SOQL queries and 50,000 rows; asynchronous contexts allow 200 queries. Other key limits include 150 DML statements, 6 MB heap synchronously, and 10 seconds CPU time.

Use Salesforce DX with the sf CLI: authenticate via JWT or sfdx-url, create a scratch org, push source with sf project deploy start, run Apex tests, then validate and quick-deploy to production. GitHub Actions or GitLab pipelines can automate this flow.

Salesforce blocks synchronous callouts from triggers and prevents mixing DML with callouts in the same transaction. Move the callout to a @future(callout=true) method or a Queueable class implementing Database.AllowsCallouts.