"The dataset is too large. Some fields can't be expanded" — Cell count limit with large datasets and multiple measures

Re-Open
FERNANDO GUZMAN asked on July 21, 2026

Description:

We are using Flexmonster version 2.9.43 embedded in a JavaScript web application with a JSON inline data source.

Issue: When loading a report with a large dataset and a layout that has multiple row dimensions and several active measures, Flexmonster displays the following message and prevents expanding nodes:

"The dataset is too large. Some fields can't be expanded. Please narrow down the dataset."

 

Steps to reproduce:

  1. Load a JSON data source with approximately 30,000–40,000 rows.
  2. Configure a pivot layout with:
  • Multiple row dimension fields in a nested hierarchy
  • One of those dimensions having high cardinality (e.g. a unique ID field with ~30,000+ distinct values)
  • 8 or more active measures
  • 1 column dimension with ~15–20 distinct values
  • expandAll: true and drillAll: true in the slice

    3. Load the report — the error message appears and nodes cannot be expanded

Analysis: Even at the leaf cell level alone, before any subtotals are counted, the total number of cells required already exceeds what appears to be Flexmonster's internal rendering limit:

~30,000+ unique values (high-cardinality row dimension) × ~18 column values × 8 active measures

= ~4–5 million leaf cells

 

Questions for Flexmonster support:

  1. What is the exact cell materialization limit in v2.9.43, and is it documented anywhere?
  2. Is there a configuration option or API to raise or disable this limit?
  3. Is there an event or callback that fires when this limit is reached, so the application can intercept it and show a custom message?
  4. Has this limit been raised in a more recent version of Flexmonster? If so, which version?
  5. Is there a recommended pattern for handling layouts with high-cardinality dimensions and many measures without hitting this limit?

Environment:

 

  • Flexmonster version: 2.9.43
  • Data source type: JSON (inline array)
  • Framework: JavaScript (AngularJS)
  • Browser: Chrome / Edge (latest)

 

3 answers

Public
Maksym Diachenko Maksym Diachenko Flexmonster July 21, 2026

Hello,

Thank you for writing to us.

Expanding all nodes with a high-cardinality dimension in rows and many measures is a heavy operation, so hitting this message is expected in your scenario.

To answer your questions:

  1. There is no cell count limit - the message is triggered by a time-based cutoff of 9 seconds. It exists to prevent the browser's "page unresponsive" warning or an out-of-memory crash while performing expands.
  2. Flexmonster provides a way to raise this limit. It is controlled by the expandExecutionTimeout option. You can increase it, but keep in mind users will have to wait longer for expands to complete.
  3. No event or callback fires when this limit is reached. However, you can override the default pop-up message through the localization to show a custom message instead. Please refer to our localization guide for more details: https://www.flexmonster.com/doc/localizing-component/
  4. This limit was not changed in more recent versions.
  5. We recommend narrowing the dataset with filters before expanding. High-cardinality dimensions combined with many active measures are a known weak spot for expandAll.

Please let us know if our answer was helpful.

Best regards,
Maksym

Public
Maksym Diachenko Maksym Diachenko Flexmonster 6 hours ago

Hello,

Hope you are doing well.
We are wondering if you have time to review our recommendations and if increasing expandExecutionTimeout, or pre-filtering the dataset resolved the issue.
Looking forward to hearing from you.

Best regards,
Maksym

Public
FERNANDO GUZMAN 2 hours ago

Mksym,

 

Thank you for following up.

We increased the timeout but still it after a number of cells in our expanded report it stops.  Somehow my team found that 500-1000 million of cells is the mas will expand.

Sure filtering works, and not expanding all data at once works.  So at this point expanding by the higher group works but ..... This is not the requirement, the customer is quite upset that they cannot expand all and have a full view of their data in expanded mode where they can navigate quickly.

 

I used the data server and that seems to make it fine but, we don't usually provide that with our application so it is only a future option.

Honestly, with the amount of cells it is reasonable to wait.  We are ok displaying a message about the wait while it expands.

The browser seems to cope well with the data, memory is ok.

 

I can provide a dataset and the save report so you can run the analysis and see if this is a feature you want to support.  Do you want it?  I can do it by tomorrow.

 

Unfortunately for me, I'm currently asking them to use excel for that expanded dataset/calculation.

 

 

Please sign in or register to submit your answer