There are actually three suggestions, but they all relate to KPIs (link to what these are below).
%DeepSee.KPI
https://docs.intersystems.com/iris20252/csp/documatic/%25CSP.Documatic.cls?LIBRARY=%25SYS&CLASSNAME=%25DeepSee.AbstractKPI
1. Provide the ability to change the number of rows displayed and exported for KPIs.
https://docs.intersystems.com/iris20252/csp/docbook/DocBook.UI.Page.cls?KEY=D2MODADV_ch_kpi#D2MODADV_kpi_query_form
In scenarios where we create a table using KPIs, the number of rows always significantly exceeds 1000. It seems entirely appropriate to remove the row limit and provide the option to specify the row limit with a parameter.
2. Create a parameter for retrieving shared filters from the dashboard. In scenarios where a KPI doesn't have any filters defined but needs to retrieve them from the dashboard, there's no convenient parameter. Currently, %request.Content.FILTERS is used, but it retrieves filters in an unstructured array and in the MDX format [name].[hierarchy].[name].
3. In scenarios where a table is built using KPIs, add a "No data" placeholder for empty KPI data. Currently, only an empty table is displayed, without any user feedback. Hence user don't know what is wrong with the pivot.
Thank you for submitting the idea. The status has been changed to "Needs review".
Stay tuned!