Salesforce Developer Console Is Changing. What Happens to the Way You Run SOQL?

For years, Salesforce developers and administrators have had a familiar place to go whenever they needed to run a quick SOQL query: Developer Console.

Need to check a few Accounts? Write a query.

Need to investigate a data issue? Write a query.

Need to see what’s sitting inside a Salesforce object? Write some SOQL, click Execute, and inspect the results.

It was simple. But Salesforce is moving toward a newer development experience with Web Console, its modern browser-based IDE.

Web Console brings capabilities such as SOQL execution, Query Plan inspection, Apex development, debugging, metadata navigation, and other development workflows into a newer interface.

That raises an interesting question: What do you actually need from a SOQL query tool?

Because sometimes, the problem isn’t writing the query.

It’s working with what comes back.

The SOQL Query Is Easy. The Results Can Be the Hard Part.

Imagine you’re investigating a Salesforce org and need to find Accounts that match a particular condition.

You write:

SELECT Id, Name, Industry
FROM Account
WHERE Industry = 'Technology'

Nothing complicated.

But now imagine that query returns: 50,000 records.

Or: 100,000 records.

Suddenly, the workflow becomes less about writing SOQL and more about figuring out how to work with a large result set.

You may want to:

  • See results while the query is still running
  • Browse thousands of records
  • Filter the returned data
  • Sort the results
  • Stop a long-running query
  • Export the records
  • Run the same query against another Salesforce org
  • Save the query for later

This is where the idea behind QueryStream comes in.

What If SOQL Results Didn’t Make You Wait?

Most people think about a query like this: Write → Wait → Get everything

QueryStream is designed around a slightly different workflow: Write → Run → Watch the results arrive

For large result sets, QueryStream uses Salesforce’s QueryMore mechanism to retrieve records in batches of up to 2,000 rows.

The results can then be rendered progressively in the browser as they arrive.

That means if you’re querying a large Salesforce org, you don’t necessarily have to wait for the complete result set before you can start looking at the data.

You can begin investigating the records that have already arrived.

See Salesforce Query Results While They’re Still Loading

This is one of the main differences in the QueryStream experience.

Suppose your SOQL query eventually returns 50,000 records.

Instead of waiting until all 50,000 records have been retrieved before displaying anything, QueryStream can begin showing the first batch while the remaining records are still being fetched.

As the query progresses, you can:

  • Watch the row count increase
  • Browse the records already retrieved
  • Sort the results
  • Filter the results
  • Stop the query when you’ve found what you need

That last capability can be useful during troubleshooting.

Sometimes you don’t actually need all 50,000 records.

You may only need enough information to answer the question you’re investigating.

If you’ve already found what you’re looking for, you can stop the query and work with the results that have already arrived.

Export Salesforce SOQL Results

Sometimes looking at query results in a browser isn’t enough. You may want to take the data into another tool. Maybe you’re analyzing it in Excel. Maybe you’re sharing the results with another team member.

Maybe you’re processing the data as part of a development workflow.

QueryStream supports both CSV and JSON export.

CSV Export – CSV can be useful when you want to work with the results in:
  • Microsoft Excel
  • Google Sheets
  • Other spreadsheet tools
  • Data analysis workflows
JSON Export – JSON can be useful for:
  • Developer workflows
  • API-related work
  • Data processing
  • Integrations

Another useful part of the workflow is that you don’t necessarily have to wait for every record to finish loading before exporting.

You can export the data that has already arrived, including while a streaming query is still running.

For an investigation, that can be useful when you already have enough information to continue your work.

Working With Multiple Salesforce Orgs

Salesforce developers and administrators rarely work with only one environment.

You might regularly switch between:

  • Production
  • Full Sandbox
  • Developer Sandbox
  • UAT
  • Development environments

When investigating a data issue, you may need to run the same or similar SOQL queries against multiple orgs. QueryStream supports multiple connected Salesforce orgs in separate tabs.

Each connected org maintains its own:

  • Authentication
  • Query history
  • Results
  • Saved queries

This helps keep the context of each Salesforce environment separate while you move between them.

Instead of mixing queries from Production and a Sandbox, you can keep each org’s query activity within its own tab.

Save the SOQL Queries You Use Repeatedly

Salesforce developers and admins often have queries that they run again and again. For example:

SELECT Id, Name, Email
FROM Contact
WHERE Email != null

Or a query you’ve created specifically for troubleshooting a recurring issue.

Or a query you use during data cleanup.

Or a query you run whenever you’re preparing for a deployment.

QueryStream allows you to save queries so you don’t have to recreate them every time.

Saved queries and query history are stored in your browser’s local storage rather than being maintained as server-side user data.

This is part of the broader browser-focused architecture behind QueryStream.

Aggregate SOQL Queries

Not every Salesforce data investigation is about looking at individual records.

Sometimes you want to understand the data at a higher level.

For example:

  • How many Accounts are there in each Industry?
  • How many Opportunities are in each Stage?
  • What’s the average value of these records?

That’s where aggregate SOQL becomes useful.

QueryStream supports aggregate queries using functionality such as:

  • COUNT
  • SUM
  • AVG
  • MIN
  • MAX
  • GROUP BY
  • HAVING

For certain aggregate scenarios where native Salesforce execution isn’t sufficient, QueryStream can use a browser-side aggregation approach and process the retrieved records locally.

This allows the browser to perform more of the analytical work on the data returned by the query.

QueryStream for Everyday Salesforce Investigation

A SOQL query tool isn’t only useful when you’re actively developing Apex.

There are plenty of everyday Salesforce tasks where being able to quickly query data is useful.

Data Investigation

You might ask:

“Why are there so many records with this status?”

A SOQL query can help you identify the records and investigate the pattern.

Debugging

You might need to answer:

“Which records are being affected by this issue?”

Instead of manually navigating through records, you can query the relevant data.

Data Cleanup

Perhaps you’re preparing for a cleanup exercise and need to know:

“How many records still contain this outdated value?”

A query can give you the data you need before making changes.

Auditing

You may want to investigate Salesforce user activity or retrieve records matching specific criteria.

Migration Preparation

Before a migration, you may need to understand:

  • How many records exist
  • Which records match your migration criteria
  • How much data you’re dealing with
Production Troubleshooting

When something goes wrong in Production, being able to quickly inspect the underlying Salesforce data can help you understand what you’re dealing with.

In many of these situations, the SOQL query itself isn’t particularly difficult.

The useful part is what you can do with the results.

Salesforce Developer Console vs Web Console vs QueryStream

It’s worth making an important distinction.

Web Console is designed as a broader Salesforce development environment.

It brings together capabilities such as:

  • Apex
  • SOQL
  • Debugging
  • Query Plan
  • Metadata navigation
  • Development workflows

QueryStream focuses on a narrower problem:

Running SOQL and working with the results.

Its focus is on areas such as:

  • Live result streaming
  • Large result sets
  • Progressive result display
  • Filtering and sorting
  • CSV and JSON exports
  • Multiple Salesforce orgs
  • Saved queries
  • Browser-based result handling

So QueryStream isn’t intended to replace a complete Salesforce development environment.

The two approaches address different workflows.

Think about it this way:

Web Console: A broader development environment for working with Salesforce development and debugging.

QueryStream: A focused SOQL experience designed around querying Salesforce data and working with potentially large result sets.

The right tool depends on what you’re trying to accomplish.

The Bigger Question Isn’t Really About Developer Console

Developer Console made one thing very easy: Ask Salesforce a question.

Web Console is bringing Salesforce development into a newer browser-based experience.

But the underlying need hasn’t changed.

Developers and administrators still need to ask questions about Salesforce data.

And sometimes the question isn’t: “Can I run this SOQL query?”

It’s: “What do I want to do with the 100,000 records that come back?”

Do I want to watch the results arrive?

Do I want to filter them?

Do I want to sort them?

Do I want to export them?

Do I want to save the query?

Do I want to run the query against another Salesforce org?

Do I want to stop the query once I’ve found enough information?

Those are the problems QueryStream is designed to focus on.

Try QueryStream

If you regularly work with Salesforce SOQL and large result sets, QueryStream provides a focused environment for running queries and working with the returned data.

Launch QueryStream: QueryStream App

See How QueryStream Works: QueryStream: How It Works

Explore the Architecture: QueryStream Architecture

Final Thought

The way Salesforce developers access their development tools may continue to evolve.

Developer Console.

Web Console.

Browser-based development tools.

But one thing remains constant: Salesforce data needs to be queried, investigated, and understood.

And when a simple SOQL query returns tens of thousands of records, the important question isn’t just whether you can execute the query.

It’s: How do you want to work with the answer?

That’s where QueryStream is designed to help.

Leave a Reply

Your email address will not be published. Required fields are marked *