----------------
- stimulsoft-dashboards-js 2026.3.3
- stimulsoft-dashboards-js-angular 2026.3.3 (Angular 21, TypeScript 5.9)
- Stimulsoft Designer (Desktop) 2026.3.3
Part 1 - Dashboards.JS / Angular viewer 2026.3.3: filtering empties the whole report
------------------------------------------------------------------------------------
Steps to reproduce:
1. Open the report (Filter_items.mrt) in the JS viewer (stimulsoft-dashboards-js-angular 2026.3.3).
2. The report renders correctly with "Filter_var = (All)" - all rows are listed.
3. Open the "Filter_var" drop-down on the parameters panel and check one or more
values (e.g. the first two items).
4. Press Submit.
Actual result:
The report area becomes completely empty - not a single row is rendered, not even the
rows whose Code values were explicitly selected. Once this happens, the viewer never recovers: changing the selection again or
pressing Reset/Submit keeps returning an empty report. The only way to get the reportback is to fully reload the report (recreate the viewer / reload the page).
Expected result:
Only the rows matching the selected values should be rendered, and it should be possible to change the selection repeatedly without reloading.
The same report, the same data source and the same filter expression work correctly in
the desktop Designer (see Part 2 - there the filtering itself works), so this looks like a viewer/engine issue specific to the JS build.
- screenshot1.png (135.31 KiB) Viewed 38 times
- screenshot2.png (288.51 KiB) Viewed 38 times
--------------------------------------------------------------------------
In the desktop Designer the same report filters correctly as long as the values are
picked directly from the list:
1. Open the "Filter_var" drop-down, check e.g. 3 items, Submit.
-> The report correctly shows exactly those 3 rows. This works fine.)
The problem appears when the drop-down's "Type to search" full-text box is used to
narrow down the list first:
2. Open the "Filter_var" drop-down.
3. Type a substring into the "Type to search" box, e.g. "1772".
-> The item list is correctly narrowed down to the 4 matching values, and all 4 are
shown as checked because "Select All" is checked.
4. Press Submit.
Actual result:
The report is generated for ALL values of the variable (303 pages), not for the 4
values that the search box had narrowed the list down to. The visible checked state of
the 4 items is not what is actually passed to the filter - "Select All" still means
"the entire item set", ignoring the active search filter.
Workaround that proves the point:
5. Uncheck "Select All", then manually tick the same 4 items (which are the only ones
the search box left visible) and press Submit.
-> Now the report correctly returns exactly those 4 rows.
Expected result:
When a search/full-text filter is active in the drop-down, "Select All" should apply to
the currently filtered subset only, i.e. checking it should select exactly the items
that are visible. When the search filter is cleared, "Select All" should again mean the
whole item set. Having to clear "Select All" and tick every visible item one by one
defeats the purpose of the search box - the set is already pre-filtered.
- screenshot3.png (29.14 KiB) Viewed 38 times
- screenshot4.png (56.26 KiB) Viewed 38 times
- screenshot5.png (40.9 KiB) Viewed 38 times