Suggest an Idea

[b_garside]

The QlikSense table feature under "Representation" for the Mini chart needs to be upgraded to handle more than 100 data points. This is a documented bug under ID: HLP-8345

For reference for those that don't use QlikView it can handle 300+ data points in its straight table mini chart feature when rendering this visual.

The 'Mini chart' is officially limited to 100 along the X axis. The bug ID indicates this was not documented prior to this discovery earlier in September of 2020. Maybe it was assumed no one would care or notice. I would argue many customers would like to use more than 100 data points such as 365 days in a year for tracking the stock market on a day by day basis and many other scenarios that would require far more than 100 data points. Performance wise it faster at rendering than a Trellis chart so it has that added potential when a Mini chart would be a better fit.

For reference this is the response received from support after this bug was validated with R&D once the case was submitted.

"The feature in question about mini chart has a limitation. The reason we see for this behavior is because Qlik Sense Table Mini Chart should allow only 100 points to render the visual properly. The documentation doesn't show this limitations and soon this would be fixed by the bug to show the limit in our help page. R&D is going to fix this issue in future release by allowing only 100 values in selection."

Please join me in supporting this suggestion to make this feature a more useable visual with more use cases where it makes sense to use a Mini chart above anything else.

Brian Garside

[Meghann_MacDonald]

Hi @b_garside , thank you for submitting your idea.

In the future, please only add 1 label per idea. If you have any questions about the Ideation requirements, please read the Ideation guidelines in the forum.

Meghann

[b_garside]

Thanks, I take it you already modified it down to one?

[Meghann_MacDonald]

Yes! If there is any confusion about Qlik Sense Business vs Qlik Sense Enterprise, just select Enterprise and you can add further clarification to the tags.

Meghann

[Patric_Nordstrom]

Thank you for your feedback on ways to improve our product. While this is something we understand would be useful, it's not on the short-term roadmap. Please continue to show your support for this idea.

There is always a tradeoff between data to be shown and performance for the end user. The intention of the limit is steer towards a suitable aggregation level given the small size of the chart and the potential high number of charts. In the case with stocks I would suggest to show by weeks or days of the last 3 months and switch to higher resolution line chart when the selection is smaller.

Thanks,
Patric

[b_garside]

Aggregation could be helpful in some cases. In scientific use cases it's not as useful. The customer I'm working with uses sensors that need resolution, but still able to see many at a time in a table like we did in QV?
The point I guess I'm making is can we at least match the ability of QlikView. Thanks for the update.

[Patric_Nordstrom]

@b_garside  There are always limits in all chart rendering, chosen to fit most customer configurations with a balance between number data points, time to render, bandwidth required, server capacity needed etc.

In special cases, for instance IoT customer may want a different priority much more data per chart, and scale the system with fewer users, more server power and more bandwidth. 

For cases like that one way could be to expose the limit as configurable as we do in for number of items in the map chart layers. There are similar needs raised for the scatter and the line chart.

Thanks,
Patric

[Meghann_MacDonald]

From now on, please track this idea from the Ideation portal. 

Link to new idea

Meghann

NOTE: Upon clicking this link 2 tabs may open - please feel free to close the one with a login page. If you only see 1 tab with the login page, please try clicking this link first: Authenticate me! then try the link above again. Ensure pop-up blocker is off.