OrgSprint

Edit, compare, and deploy Salesforce code and metadata between orgs without leaving the browser.

OrgSprint — What's new (v0.39.53 → v0.39.142) METADATA EXPLORER • Browse, retrieve, and import any metadata type in your org • Dependency check (with transitive tracing) and "Where Used" lookup, with Setup deep-links • Automation Stack: every trigger, flow, and rule on an object in one view • Cross-org Metadata Compare: side-by-side diff and deploy between orgs, with per-component error details when a deploy fails APEX • Apex Class panel: edit with syntax colors, save, delete, and push classes across orgs (sandbox and Production) • Compare several classes at once: check them in the list, and each one opens as its own tab in the Compare window • Apex Compare window: side-by-side diff between orgs, batch push, and Validate-only runs • Production deploys run only the tests you eploy are used automatically, and if thereare none you're asked which to run, so one unrelated failing test no longer blocks your deploy. The last answer is remembered. • Push errors show the exact line, with a cl • Run Apex tests on their own, outside of a deploy LIGHTNING WEB COMPONENTS • LWC editor: list, open, edit, and save bundles, with syntax colors and a Compare button • Production LWC deploys no longer run your org's Apex tests FLOWS • Flow Scanner: lint-style analysis of your flows • Subflow wiring view: see what each flow sepe-mismatch warnings • Clearer, de-duplicated Flow save errors • A warning when a deployed flow lands as an inactive version, so you know to activate it SOQL & NAVIGATION • SOQL result paging and an ID/value-list helper for WHERE IN with thousands of values • Jump to any record by Id from the header • Org favicon badge: green for Production, red for sandbox • Target org picker shows each org once, even when it's open under several URLs SAFETY • Production guard: changing metadata in a Pws, permissions, deploys) requires apassword. Sandbox work and same-org sandbox → Production promotions skip the prompt. • Validate-only deploys never change the tar • Apex and LWC saves are read back from the org afterwards, so "Done" means it actually landed FIXES • Deploys that failed on tests or coverage no longer show as "Done" • Metadata Compare no longer reports components as deployed when they couldn't be retrieved from the source org • An LWC save that fails partway is retried ploy, so a bundle is never left half-saved • Deploy errors list only the classes under 75% coverage • Cross-org Apex push is more reliable: clear stub classes, longer timeout • Many stability fixes across Flow cleanup, dependency scans, and cross-org deploys