SOQL Studio#

SOQL Studio is a read-only query surface over a connected org. Write a SELECT, run it, read the results in a grid — then send exactly the rows you want to change straight into a snapshotted, reversible managed load. It replaces the old Inspector → export CSV → edit on the desktop → re-upload loop.

The studio itself never writes. Every write leaves through Forge Load's safety gates: snapshot before write, verify after, one-click rollback.

Query, edit, push — in one place#

1. Run a SELECT. Results land in a grid. Relationship columns (Account.Name) are flattened for reading.
2. Edit inline. Loadable cells are editable in place. An edited cell is marked, and the row it's in is flagged as changed.
3. Pick the rows to write. Each row has a checkbox. Editing a cell selects its row automatically, so your edits ship by default.
4. Queue as load. The selected rows stage as a DRAFT managed load. You finish it under Loads — preview, snapshot, execute, roll back.

Change-aware push — only what you changed#

This is the important guarantee. If you pull 100 records and edit one, SOQL Studio writes one — not 100.

• An update writes only the rows you actually changed. Selecting a row you didn't edit doesn't queue an unchanged write.
• Pulling a set and changing nothing writes nothing — the Queue button disables and tells you so.
• You stay in control per row: deselect a changed row to hold it back, or (for insert/upsert/delete) select exactly the rows you mean to include.

Writing 99 unchanged records back is not harmless — it's audit-log noise, wasted API calls, and a real risk of clobbering someone else's concurrent edit. SOQL Studio stages only the rows you chose, so none of that happens.

Mapping is inferred for you#

A SOQL result's columns are already field API names, so there's no separate "map the columns" step to grind through. When the inferred mapping is unambiguous — every column resolves to a real, writeable field, checked against a live describe of the org — SOQL Studio applies it automatically and Preview is ready immediately.

If a column is genuinely ambiguous (it doesn't match a field, or the field isn't writeable — a formula or system field), that column drops to the manual mapper so you can resolve it. You can always open the mapping to adjust it.

Safety, end to end#

Tip: Because every SOQL-Studio write becomes a managed load, there's exactly one write path in the platform — and it's the snapshotted, reversible one.

• Read-only studio. SELECT only; any write is a managed load.
• The server re-runs your query. The staged rows are exactly what the org returns when the load is built — never a row body sent from the browser. Row selection only narrows that fresh result; it can't introduce a row your query didn't return.
• Every gate still applies. Snapshot before write, verify after, conflict- aware three-way rollback.