Analytics

How to Fix the 2,000-Row Cap On Salesforce Report Exports

Alex Tarasevich

By Alex Tarasevich

Updated November 17, 2026
Branded content with Xappex

If a scheduled spreadsheet refresh or BI dashboard suddenly started returning exactly 2,000 rows this summer, or began failing with a “Verify your identity” page, your report probably isn’t broken. The data is still in Salesforce. The report may even run perfectly normally when you open it in the browser. What changed is how that data gets out of Salesforce. 

The Summer ’26 security changes added step-up authentication to report exports. That forced many tools that move report data into Excel, Google Sheets, and BI platforms to change how they access reports. For some workflows, that also exposed limits most admins had never needed to think about. Here’s what changed and what you can do about it.

What Has Changed?

Salesforce began enforcing step-up authentication for report exports and printing on July 1, 2026. Users have to complete an additional identity check, even if they’ve already signed in with MFA.

After the sandbox rollout, Salesforce narrowed the scope. Simply viewing or running a report doesn’t trigger the challenge, but exporting and printing still do.

Admins can configure the policy under Setup → Identity Verification → Session Security Level Policies → Reports and Dashboards, with a step-up period of 1 to 120 minutes.

The bigger surprise was the effect on integrations.

A browser export now needs a person to complete the identity check, and a scheduled refresh running at 2 AM can’t do that. Spreadsheet and BI tools therefore retrieve report data through the Analytics API, which uses an OAuth-authenticated connection and doesn’t trigger the challenge. That route has its own limits, though.

Why Some Salesforce Report Exports Now Stop at 2,000 Rows

The Analytics API returns a maximum of 2,000 rows from a report run. Salesforce recommends narrowing the report with filters when you hit the limit. There isn’t a permission, license, or setting that simply raises the cap.

The limit itself isn’t new. What’s new is how many workflows now depend on the API due to the authentication changes.

There are other limits to keep in mind, too: 500 synchronous report runs per hour, 1,200 asynchronous requests per hour, 20 custom field filters per run, and 100 columns per report. These limits are shared across the org, so a few heavy scheduled refreshes can affect other processes.

The crucial difference is this: the 2,000-row limit is a limit on the report retrieval method, not on the amount of data stored in Salesforce.

4 Ways to Adapt

There isn’t one perfect solution. The right choice depends on whether you need the data once, on a schedule, or in a format that matches the existing Salesforce report.

1. Export It Manually

For a one-off request, the easiest answer may be the simplest one: export the report directly to CSV or Excel using a Details Only export.

You complete the step-up check yourself, and the 2,000-row Analytics API limit doesn’t apply.

It’s great for an occasional pull. Obviously, it doesn’t help much if the same export needs to happen automatically every morning.

2. Narrow the Report

This is also Salesforce’s own recommendation, and it’s often enough.

Look at the report filters, date range, scope, and columns. A report shared with an entire team may be pulling far more data than any individual refresh actually needs.

Using filters such as My or My Team’s, removing unnecessary columns, or limiting the date range can bring the result below 2,000 rows. It can also make the report faster. If several people rely on the same shared report, consider applying the narrower filters in your own pull rather than editing the report everyone else uses.

3. Use a Connector Built for the Change

If the report needs more than 2,000 rows and has to refresh on a schedule, check whether your spreadsheet or BI connector has been updated for step-up authentication.

The better connectors pull reports through the Analytics API, so scheduled refreshes keep running without anyone stepping in to complete an identity check.  Some also retrieve the full report past the 2,000-row cap. 

That saves you from splitting the report into monthly or regional pieces, appending the results, and hoping none of those pieces has grown past the limit and started dropping rows.

When you evaluate a connector, a few questions are worth asking. Does it use the Analytics API for report pulls, so scheduled refreshes run unattended? What happens when a report exceeds 2,000 rows: does it stop silently, warn you, or retrieve everything? Does full retrieval depend on the plan you’re on? Can you filter the data on the way in without changing the shared report in Salesforce?

4. Move Recurring Extracts to SOQL

If you’re regularly moving large amounts of Salesforce data into a spreadsheet or BI tool, SOQL is usually the cleaner long-term option.

SOQL reads the records directly, so the report export limit, step-up authentication, and the Analytics API’s hourly report limits don’t apply.

The drawback is that you receive raw underlying records instead of a fully formatted report. Groupings, subtotals, bucket fields, and report formulas may need to be recreated elsewhere, and some reports don’t translate neatly into SOQL.

The other traditional obstacle, knowing the syntax and the API name of every object and field, is much smaller than it used to be. Many tools now offer AI query builders that turn a plain-English request such as “all open opportunities closing this quarter, with account name, owner and amount” into SOQL, report-to-query converters, and point-and-click query editors. 

Whichever route you use, review the query before relying on it, and check that its filters match the logic of the report it replaces.

How Xappex Connectors Handle Both Routes

Xappex XL-Connector, XL-Connector 365, and G-Connector support both approaches: pulling your existing Salesforce reports and pulling records directly with SOQL. 

For existing reports, the connectors use the Analytics API for report pulls, so scheduled refreshes keep running without an identity check at 2 AM.  Paid plans retrieve the full report beyond the 2,000-row cap, with the report kept exactly as it’s defined in Salesforce. 

On the free plan, fields and filters with live data preview let you add your own AND/OR filters, pick columns, and see the row count before and after filtering, without changing the shared report.

For recurring extracts, the AI query builder writes SOQL from a plain-English description, the free Report-to-SOQL converter (beta) turns an existing report into an editable query, and the visual query editor lets you build one point-and-click, with dynamic filter placeholders you fill in at refresh time. 

Summary

A report that stops at 2,000 rows, or a refresh that hits a “Verify your identity” page, is a side effect of a security change, not a sign that your data or your report is broken. Step-up authentication now protects report exports, so integrations now retrieve report data through the Analytics API, along with its long-standing limits 

Match the fix to the need: a manual Details Only export for a one-off pull, tighter filters when a report pulls more than anyone uses, a connector that handles step-up authentication and the row cap when a report has to refresh on a schedule, and SOQL for large, recurring extracts. Because the Analytics API limits are shared across the org, it’s also worth reviewing your scheduled refreshes now, before they start competing with each other.

If you want your existing Salesforce reports to keep refreshing without rebuilding them, Xappex connectors handle step-up authentication and the 2,000-row cap for you. 

The Author

Alex Tarasevich

Alex Tarasevich

Alex is the Founder and CEO of Xappex, the company behind XL-Connector and G-Connector. Its solutions help Salesforce teams simplify data management, reporting, and automation using Excel and Google Sheets.

Leave a Reply