asked 1 day ago
Hello,
We are using Microsoft Analysis Services with several cubes as our data warehouse backend. In our React/TypeScript application, we are connecting via flexmonster-react and Flexmonster Accelerator.
We're encountering an issue where, for certain cubes, drill-down returns no data after applying filters — even though the data exists.
Here's what we observed:
The client component sends Execute requests in chunks.
The response for the first chunk contains aggregated data.
The second chunk returns empty, and no further requests are made — although additional data should be present.
Based on the Accelerator logs, we believe this may be due to paging behavior:
The default page size appears to be 32k.
Chunk 0 contains the aggregate.
Chunk 1 — which should contain details — is empty.
According to the logs, chunk 1 is supposedly for subset (500, 322580), but we suspect it's actually for (500, 32258) (note: 32k, not 320k).
No MDX is logged for chunk 1, so we cannot confirm this directly, but if we run the MDX manually with a subset of 32k, it’s empty — while with 320k, we get results.
It seems the client logic stops if the next chunk is empty, but the empty chunk might be caused by an incorrect subset range.
We’ve attached a partial log to support our findings.
Please advise on how to resolve this or provide a workaround.
Thank you,
Andras Nagy
