Learn one feature at a time
A random page of the ORGanizer documentation, so you pick up something new without reading all of it at once.
Quick Console
The Quick Console is a set of plugins that open over the Salesforce page you are on. Open it with CTRL + SHIFT + V or from the ORGanizer button:
Jump straight to a plugin with CTRL + SHIFT + [index]. The index of each plugin is shown on the Plugins tab:
Some plugins also have a quick action: CTRL + ALT + [index] runs the plugin's main action without opening the console at all. This is available for SObject fields (index 4), Replace API names (index 6) and Salesforce ID converter (index 7). Every shortcut can be changed in the Options page.
In its own tab
New in 1.0
The console can now be opened as a full browser tab instead of an overlay: use the open in tab icon in the console header, or the Quick Console action next to a live ORG in the popup's ORGs tab. You get the whole viewport for long queries, wide result sets and debug logs, and the console stays open while you navigate the ORG in another tab.
Two things behave differently in the dedicated tab, by design: there is no close button (it is a tab — close the tab), and Replace API names is disabled, because it rewrites a Salesforce page and there is no Salesforce page underneath.
Home
The landing plugin: everything about the ORG you are in.
- Organization Id
- Server domain
- Session Id
- ORG info (REST API)
- User info (SOAP API)
- Apex test coverage
Quick Query
SOQL, SOSL and Tooling API queries, including parent references and subqueries:
- Results are sortable and searchable locally, and downloadable as JSON.
- The last 50 queries per ORG are kept in a history you can pick from.
- CTRL + SPACE autocompletes SOQL keywords, custom fields, relationships and objects. The
*wildcard expands to all, all custom or all standard fields. - The Tooling API button switches the query to the Tooling endpoint.
- Typing a plain search term runs a SOSL search, with results grouped by object.
- The editor resizes from its bottom-right corner.
Queries worth keeping go into Very Important Queries (V.I.Q.), named and shared across ORGs.
V.I.Q.s are stored locally and are not synced. They ride along in the Import / Export file and in the automatic backups — which is also how you move them to another browser. The separate Backup V.I.Q. & V.I.S. button that used to sit in the Options page was removed in 1.0: the regular export already carried them.
Execute Anonymous
Run anonymous Apex without opening the Developer Console:
- Pick the debug level per category; Download log saves the generated log.
- The last 50 scripts per ORG are kept.
- CTRL + I re-indents the code.
- The editor resizes from its bottom-right corner.
Scripts worth keeping go into Very Important Scripts (V.I.S.), same as V.I.Q.:
SObject fields
Query every field of one record. Type a Salesforce Id, or let ORGanizer take it from the current
page URL (it also picks up an id query-string parameter):
Every updatable field is editable inline, with a rollback button, and saved individually:
The quick action CTRL + ALT + 4 opens the plugin and runs the query straight away.
Quick ORG Describe
Describe the ORG's objects:
… and every field of each one:
Replace API names
Swap every custom field label on the page for its API name. Works on the Classic and Lightning standard layouts, the field set editor and the page layout editor:
On the field set and page layout editors, switch back to the label view before saving a layout on an object with a lot of fields — otherwise the tab can freeze for a while. The plugin is disabled in the dedicated tab, where there is no Salesforce page to rewrite.
Salesforce ID converter
Convert 15-character Salesforce Ids to their 18-character form, in bulk:
The quick action CTRL + ALT + 7 turns it into a URL clipper: the Id of the record you are looking at goes straight to the clipboard.
Login As…
Log in as another internal user. Search by name or username, then open the user's detail page, log in on a new tab, or log in in a private window (if ORGanizer is allowed there):
Field Usage new in 1.0
The question every long-lived ORG ends up asking: which of these fields is anybody actually filling in? Pick an object and Field Usage goes through its fields one by one, counting how many records carry a value and what share of the object that is — the quickest way to tell a field that is doing work from one that has been empty since the day it was created, before a clean-up, a migration or a page layout review:
The numbers are what your user can see: the analysis runs with your session, so sharing rules and field-level security apply to it exactly as they do to any other query. Run it as an administrator for a picture of the whole object.
Show me another one