Execute Other
When you click on the Execute button, query module executes the query in default mode which is what you need more of
the time. The default mode is,
query rest api, show only non-deleted records and fetch the first batch of records.
However, sometimes you want to execute a query with a variation. These variations are grouped as Execute Other
options. These options can be
accessed by clicking on the dropdown next to Execute button as shown below

Note that some options are available only in certain editions, and if so, they would be mentioned in each of the sections below.
Execute and Fetch All
Brobench by default shows you the first batch of records matched by a Query. This is efficient and quick, so you can review the first batch of records and fetch more if required. However, in certain situations, you’re sure that you want to view all matched records, and in such cases, you can make use of this option.
While Query is executed and fetching records, it shows Cancel button and if you cancel, it cancels fetching more
batches and shows the records that
are fetched till then.
Execute with Include Deleted/Archived
This option executes the query to include the deleted records. Note that you can also query to include deleted records
using All Rows clause. Deleted records would be included when this option is selected or if query
has All Rows clause hence you need not do both.
Execute in Connection
ProfessionalThis option allows you to execute a query in a different connection than the current one. Check out Cross Org Query for more info.
Execute via Bulk API
If you have a Query that matches a lot of records, it can take time to download all of those records via Batch API,
which is the default API that Brobench uses. Execute via Bulk API will change the underlying API to Bulk API V2. The
app will
do all the heavy lifting behind the scenes and shows the first batch of results, up to 50k. You can continue to fetch
the next batch of 50k records until results are exhausted.
Execute via Tooling Api
The app automatically uses Tooling API if you’re querying a SObject which is available only in Tooling API. However,
there
may be objects that are available in both Partner API and Tooling API, and in such cases, the app will use Partner API
by default. If you want to force the app to use Tooling Api, execute the query with Execute via Tooling Api
Execute Query in Clipboard
If you’ve copied a query from somewhere you want to execute, you don't need to paste into an editor, select and
execute it. Click on Execute Query in Clipboard, which will save you some clicks.
Query Records by Ids in Clipboard
This is the same as Query Records by Ids which automatically uses the text in clipboard
Query Records by Ids
This option helps you view the records by set of ids or extracted ids from blob of the text. When you select this option, it shows the following dialog.

Enter ids or text containing ids and click View Records. The app will extract the ids and view those records.

Please keep these points in mind when you use this feature.
- You can enter ids that belong to different objects. The app would group by the object and show multiple result tabs, one for each Object
- You can enter blob of text and in such cases, the app would try to extract the ids and show the result
Query Records by Ids in Clipboard
This action runs the Query currently in Clipboard so you don't have to paste the query into the editor, select it and run it.