asked on August 4, 2026
Hello,
We regularly encounter the following error message at our customers' sites when performing a full expansion of the data:
"The dataset is too large. Some data cannot be displayed. Please refine the dataset."
As this tool is heavily used for data reporting, the issue is recurring and is becoming highly impactful for our customers, including in cases where the underlying data volume is not particularly large. For example:
My first question is: Is it possible to obtain a resolution for this issue? I am concerned that, in the long term, we may be forced to move to a different technology if this limitation cannot be addressed.
My second question is: In the meantime, is it possible to obtain clear metrics regarding the display capabilities and limitations of the component? Knowing the maximum supported volume of data would help us better manage customer expectations and design appropriate workarounds.
Thank you.
⋅ August 5, 2026
Hello, Emmanuel!
Thank you for reaching out to us.
As a first step, we'd like to clarify that the "The dataset is too large..." message appears due to the resource-intensive expand all operation on 11 levels of nested columns, rather than from simply loading the data into Flexmonster.
Regarding your questions:
Is it possible to obtain a resolution for this issue?
To improve the data loading experience, we recommend the following:
reportFilters to reduce the amount of data displayed at once.expand all operation. By default, we wait for 9s for expand operation to complete before showing the "The dataset is too large..." message.expand all operation. You can configure expands only for specific nodes or hierarchy levels and allow users to drill down into the data as needed.In the meantime, is it possible to obtain clear metrics regarding the display capabilities and limitations of the component?
Kindly note that Flexmonster itself has no limitation on data size. Since our component runs in the browser, the practical limits are determined by the browser's available resources.
However, the issue discussed here is not caused by reaching the browser's data capacity while loading the data. The "The dataset is too large..." message is triggered when the expand operation exceeds the default 9-second execution timeout. This timeout exists to prevent the browser from becoming unresponsive or running out of memory while performing large expand operations, and it can be configured using the expandExecutionTimeout option.
You can increase this timeout if desired. Please note that the actual execution time depends on factors such as the number of hierarchy levels, the number of members at each level, and the client's browser resources. Because these factors vary from one dataset to another, there is no generic timeout value that can be recommended.
Hope you will find our answer helpful.
Kind regards,
Solomiia