Skip to main content
Announcements
Qlik Launches Open Lakehouse and advanced agentic AI experience in Qlik Answers! | LEARN MORE
cancel
Showing results for 
Search instead for 
Did you mean: 
JonathanKelly
Contributor III

Multi KPI removal

I've had pop ups now on all my multi KPI's as below 

JonathanKelly_0-1742912625978.png

Looking at the Qlik documentation it is being removed from use in April and appears that it will be fully removed even on apps where it is currently in use in November 

JonathanKelly_1-1742912782917.png

Is there any news on something that will be replacing this or will it be a case of having to replace all multi KPI's with individual KPI's? I use the multi KPI's for CSS as well, is this functionality being removed too? 

 

 

Labels (4)
1 Solution

Accepted Solutions
Patric_Nordstrom
Employee

Yes, the Multi KPI will be deprecated, it's a major cause of errors and is a pain to govern. The notice is a heads up to customers to start looking at native solutions. First the object will be removed from the asset panel so new objects cant be created. Old apps will continue to work over some time, there will be more notices made. There are now many built in functions that should be used instead: check out all the styling settings, the layout container and the nav menu. We know that many use the dimension feature to multiply KPIs, therefor we will add native trellising to charts, starting with the KPI, hopefully we can show that already at Qlik Connect.

Concerning CSS modifications. CSS is great if you what know what you're doing and can react to changes. But it's not for the faint of heart, so native styling properties are of course preferred. I started with an FAQ here https://community.qlik.com/t5/App-Development/Obsolete-CSS-modifications/td-p/2511714. There will be some suggestions also in the help on how best to replace the Multi KPI.

Thanks,

Patric

View solution in original post

6 Replies
Or
MVP

I'm assuming they're meant to be replaced with layout containers from a functionality perspective, but that's just guesswork. No idea about the CSS, though.

Patric_Nordstrom
Employee

Yes, the Multi KPI will be deprecated, it's a major cause of errors and is a pain to govern. The notice is a heads up to customers to start looking at native solutions. First the object will be removed from the asset panel so new objects cant be created. Old apps will continue to work over some time, there will be more notices made. There are now many built in functions that should be used instead: check out all the styling settings, the layout container and the nav menu. We know that many use the dimension feature to multiply KPIs, therefor we will add native trellising to charts, starting with the KPI, hopefully we can show that already at Qlik Connect.

Concerning CSS modifications. CSS is great if you what know what you're doing and can react to changes. But it's not for the faint of heart, so native styling properties are of course preferred. I started with an FAQ here https://community.qlik.com/t5/App-Development/Obsolete-CSS-modifications/td-p/2511714. There will be some suggestions also in the help on how best to replace the Multi KPI.

Thanks,

Patric

JonathanKelly
Contributor III
Author

Thank you, I appreciate the update, and i understand why this is happening now. I can start moving everything away from the Multi KPI extension. The biggest use I had was affecting the opacity to make the charts slightly transparent to put up on TV's as dashboards. This allowed backgrounds to come through and not lose any of the information presented. I can see from your link you are adding more and more property styles to replace what was done with CSS which from a usability standpoint is helpful. 

The main CSS uses I had that currently cannot be matched with the native properties are:

  • Stretching visualisations to the edges 
  • Wrapping Title text in KPIs
  • Bold Bar/Line/Combo Chart axis labels and titles

I can replace a lot of tables I have used with the Straight Table or Pivot Table from the Visualisation Bundle. I am looking to see additional CSS I have used that are not covered as of yet. I can see however, that Qlik is working towards the more user friendly properties to make personalisation easier.  

SamKng
Contributor III

We've been using the multi KPI object to create a management dashboard which shows many different KPI at first glance (see "current solution" attached). As the multi-KPI object will be deprecated, I'm forced to look for a new solution. Options for my use case I've so far detected are the following:

A) Use the normal KPI object (see "approach single KPIs")

  • Advantage: high flexibility in formatting every single KPI
  • Disadvantage: very very bad performance, since every KPI is a separate object (With that approach, I end up with around 300 objects on 1 sheet, taking around a minute to load --> no-go for the users

B) Use the "Text" object from the dashboard bundle by inserting a table (see "approach text object")

  • Advantage: Lightning fast, loads below 1 sec (which is also a proof that my data model is not the issue in this case)
  • Disadvantage: Poor formatting possibilities for the table itself, table columns are detached from the "visualization grid", I cannot add a bar chart which is properly aligned to the KPIs included in the table.

Does anybody have a good idea beside A) and B) how I could reach a similar design that I currently have (see "current status")? 

Looking forward to your creative solution approaches 😉

Thanks, Sam

P.S.: I still have a bit the feeling that Qlik is rather weak when it comes to creating such extensive management dashboards, showing KPIs originating from many different apps (which is however a strong business need, since managers don't want to check many different apps on a regular basis, but get a fast overview of how things are going) in the different org units. But I'm of course fully open to get convinced by the opposite 😉

 

 

Qlik-Michael
Contributor

I completely agree with you. The MultiKPI was fast loading when using multiple KPI's. The business usually likes a current month, last month and ytd as well. So it multiplies fast!

I do think you mentioning 300 objects is too many. 5-30 seems reasonable and that is slow already. I cannot perceive that 300 objects would even finish loading.

Perhaps its wise to put your question in a new thread as the iniitial question already has an answer which is marked as the solution 🙂

SamKng
Contributor III

Thanks for the hint, I'll do that! 🙂