Hi,
There seems to be a bug with the drill down functionality whereby if the user clicks on the drill down control while the report is still loading, it crashes with the below error in the console.
Call StackSystem.InvalidOperationException: Document is creating.
at DevExpress.XtraReports.UI.XtraReport.DevExpress.XtraReports.IReport.CreateDocumentCoreAsync(Single progressRange, CancellationToken token)
at DevExpress.XtraReports.Native.DocumentCreator.CreateAsync(Single progressRange, CancellationToken token)
at DevExpress.Blazor.Reporting.Viewer.Internal.Services.ReportBuilderWasm.BuildAsync(IReport report, CancellationToken token)
at DevExpress.Blazor.Reporting.DxReportViewer.StartBuildAsync()
at DevExpress.Blazor.Reporting.DxReportViewer.StartPartialBuildAsync(Int32 pageIndex)
at DevExpress.Blazor.Reporting.DxReportViewer.HandleBrickClickAsync(MouseEventArgs args, BrickMapNodeWeb brick, Int32 pageIndex)
I have attached a simple example report, simply try to use the drill down controls in the header groupings during the first few seconds of loading, or within a few seconds of contracting/expanding another drill down. Because of the size of the report, it is quite natural that the user may click on a couple of headers to contract them, however they will then get the crash due to the time it takes between each drill down click before it is safe to click again.
Could you please advise how we can deal with this situation, whether we can disable drill down while the document is being created, or if the bug can be fixed so the report viewer ignores it (or queues it) instead of crashing.
Thanks
Hi John,
Thank you for the demo project. We managed to reproduce the described issue. We'll reply to you here once we have any results to share. Please consider enabling Support Center notifications in your profile in order not to miss any updates.
Hi, just wondering if this issue will be fixed with the 24.1 release?
Thanks
Hi John,
We'll do our best to incorporate the fix into the initial
v24.1.3
version, but I can't really guarantee that. The next major release is just around the corner, and we're a bit overloaded putting the final touches on it. If this is an urgent issue, I'd recommend replacing the native viewer with its JS-based counterpart that requires a separate ASP.NET Core backend (DxWasmDocumentViewer
). I ensured that it works correctly with your report — clicking any drill-down label immediately stops the current document creation and starts a new one with a new set of drill-down keys.