topic Re: Obsolete CSS modifications in App Development

Obsolete CSS modifications

Patric_Nordstrom — Tue, 01 Apr 2025 13:54:54 GMT

Here's a list of CSS modifications that used to be common, but no longer are necessary as there are styling settings and other functions that are easier to use and maintain.

CSS Modification	Area	How to do instead
Add sheet background color and image.	Sheet	Use the sheet styling property.
Remove the sheet title.	Sheet	Use the app UI settings.
Remove the toolbar.	Sheet	Use the app UI settings.
Hide the buttons in the pivot table.	Pivot	Use the new pivot table.
Change the null color in the table.	Table	Use the null value styling settings in the new tables.
Pajama stripes in the table	Table	Use the zebra stripe styling setting in the new table.
Chart background color and image	Chart	Use the chart styling settings.
Chart border and shadow, color, radius and size.	Chart	Use the chart styling settings.
Change font family, weight, color and size.	Chart	Use the chart styling settings.
Change selection bar colors.	App	Use theme styling properties.
Hide popup buttons.	Chart	Turn off in app settings or per chart in chart settings.
Modify the context menu.	App	Customize in app UI settings.
Highlight rows on hover in table.	Table	Use styling settings in the new table.
Hide table header.	Table	Use styling setting in the new table.
Color the filter.	Filter pane	Use styling settings in the filter pane.
Hide buttons and options in the top bar.	App	Use the app UI settings.
Group charts together.	Chart	Use the Layout container.
Modify the sheet selector.	App	Use the Navigation menu object.
Change the sheet grid.	Sheet	Use sheet properties or the Layout container.
Remove the search icon in the table.	Table	Use the new tables.
Change the context menu	App	Use the UI settings in app settings.
Change the app logo	App	Use the UI settings in app settings.
Hide navigation	App	Use the UI settings in app settings.

Re: Obsolete CSS modifications

mattqlikuser — Wed, 26 Mar 2025 21:43:59 GMT

Hello,

I used a multi KPI to set up barcodes from a previous response you had years back. Are you able to provide the example custom theme template? I have not been able to get it to work. Any help would be greatly appreciated.

Thanks!

Re: Obsolete CSS modifications

jmcy2408 — Thu, 27 Mar 2025 21:16:17 GMT

Great discussion here! While I appreciate the ability to style individual objects, one of the key advantages of CSS was the ability to apply styles globally through a theme.

With the new approach, it seems like styles now need to be applied individually per object, which can be cumbersome when managing multiple dashboards. It would be incredibly helpful if we could define styles for all instances of a specific object type (such as the Straight Table or New Pivot Table) within a custom theme—just as we could with CSS—so that updates apply universally without modifying each object separately.

Interestingly, with the recent update, my previous CSS styles for these objects no longer work. I’ve been trying (and failing) to find a way to achieve the same result by editing my CSS code.

Is there any roadmap for improving this, or are there best practices for achieving a more global styling approach by theme in the current setup?

Re: Obsolete CSS modifications

Lech_Miszkiewicz — Fri, 28 Mar 2025 01:20:19 GMT

Hi @Patric_Nordstrom

I echo @mattqlikuser comment - we use barcodes in our applications. How do we go about it moving forward?

thanks

Lech

Re: Obsolete CSS modifications

cezario-abrantes — Fri, 28 Mar 2025 15:44:50 GMT

I am totally in favor of ending the use of CSS in Qlik applications. With the visual improvements you have implemented, there is absolutely no need to use CSS. Qlik's standard objects, along with a good theme, already allow for very beautiful visualizations.

Moreover, Qlik is not meant to be a Christmas tree. It should be straightforward and to the point. In fact, no BI tool should look like a Christmas tree, but we know that many tend to go in that direction.

I hope Qlik continues following this path of visual improvements within the standard objects. My suggestion is to improve the documentation for theme editing, which is already outdated or incomplete in some areas. Some objects are missing there.

Thank you.

Re: Obsolete CSS modifications

lftensini — Fri, 28 Mar 2025 16:59:18 GMT

My dear friend, we are happy to have these additions natively. Thank you and congratulations on your efforts.

I would like to point out that there are situations where we need greater customizations, such as: hiding some objects, changing layouts in a specific way or even reproducing an effect beyond what is offered. Today we can achieve these effects through CSS and code injection through the MultiKPI object.

What I suggest is that the Sheet have an option for additional CSS properties, from which we could inject custom codes at an advanced level. When in doubt, I think it is worth keeping the CSS injection via MultKPI for now. Removing the option to insert CSS would be a step backwards for me.

Or maybe even... An object that has this exclusive functionality. Just by injecting CSS codes into the sheet.

I hope my suggestion is considered and we have the opportunity to continue including our own custom codes when necessary.

Re: Obsolete CSS modifications

Mohallem — Fri, 28 Mar 2025 17:11:36 GMT

Creio que tem muita opção sim nativamente, mas tem coisas ali que não agrada a todos, por exemplo o novo layout da nova tabela...uma opção viável seria fazer um objeto apenas para este fim, mas falo isso como um desenvolvedor leigo.E é como o Tensini falou abaixo, tem muitas outras customizações que não estão listadas ai que deixa o layout mais agradável.

Re: Obsolete CSS modifications

MatheusC — Fri, 28 Mar 2025 17:19:59 GMT

I understand that there have been great advances in the styling of components, among others.

However, I agree that having an alternative for inserting CSS code is still interesting, as an option in the Qlik native KPI tab.

Re: Obsolete CSS modifications

igoralcantara — Fri, 28 Mar 2025 20:49:42 GMT

This is very good, @Patric_Nordstrom. A lot has improved in Qlik apps interface but there are use cases where we need to inject custom CSS. Is there something on the roadmap to allow this to happen?

Re: Obsolete CSS modifications

BrandonFontes — Fri, 28 Mar 2025 21:46:25 GMT

Dear friends,

Today, we can natively use some options that previously required MultiKPI for inserting CSS. However, as some have pointed out, there are still cases where we need more advanced customizations—such as hiding the scroll bar, applying effects, or concealing specific items.

It would be great to have a built-in alternative, like leveraging the existing folder option we use for actions and alternative states, to insert CSS directly. Or perhaps even a dedicated object designed specifically for this purpose.

Re: Obsolete CSS modifications

Vegar — Sat, 29 Mar 2025 06:16:39 GMT

I get an idea on what's coming by reading this post by @Patric_Nordstrom., but could someone please add a link to a post that explains what's coming and when?

At first I understood this as a nice tricks and tips post, then I found that the Multi KPI will be discontinue, but reading the comments I now get the feeling that the change includes any type of custom CSS modifications, including custom themes (?)

I would really appreciate a link to an "official" Qlik statement about this in form of a blog post, forum thread or other.

Re: Obsolete CSS modifications

JandreKillianRIC — Sat, 29 Mar 2025 07:43:15 GMT

We need custom CSS. Although this is not used a lot (in my case) I have quite a few clients that demands this.

If needed I can drop some CSS code here that we cannot do with native Qlik capabilities.

Its already a massive (additional work and additional hours the client has to pay to move the Multi KPI to KPI and Layout containers) which the client didn't ask for now we need to tell them we are losing the CSS stuff too.... We need an alternative.

Re: Obsolete CSS modifications

marksouzacosta — Sat, 29 Mar 2025 22:08:32 GMT

Injecting CSS at the sheet level—whether through multi-KPI or other means—is absolutely essential given how severely Qlik falls short on basic visual customization. We have clients whose entire user experience depends on the custom CSS we've implemented using both Themes and multi-KPI objects. Stripping away this capability would be a drastic regression and a serious blow to the platform’s flexibility and user satisfaction.

Re: Obsolete CSS modifications

Patric_Nordstrom — Mon, 31 Mar 2025 16:11:42 GMT

Hi Matt,

I would recommend to use a custom theme and import the font, then you can use the font directly by picking the font in a drop down in the font picker for the table.

https://qlik.dev/extend/create-custom-themes/custom-themes-fontfamily-examples/

Thanks,

Patric

Re: Obsolete CSS modifications

Patric_Nordstrom — Mon, 31 Mar 2025 16:15:20 GMT

Themes are not affected by the retirement of the Multi KPI, no changes there. The new stylings settings should also be available as them settings, that's the intention.

Yes, that's the downside of CSS modifications, have to be able to react to changes.

Yes, we hope to introduce UI settings on app level for all charts, or all bar charts etc, stay tuned.

Re: Obsolete CSS modifications

Patric_Nordstrom — Mon, 31 Mar 2025 16:16:47 GMT

Either place the CSS in a custom theme or import the font in a theme and pick the font.

https://community.qlik.com/t5/App-Development/Obsolete-CSS-modifications/m-p/2512386/highlight/true#M105205

Re: Obsolete CSS modifications

Patric_Nordstrom — Mon, 31 Mar 2025 16:18:34 GMT

Hi,

The CSS can still be replaced in a custom theme. That said we're investigating other options for CSS injections.

Thanks,

Patric

Re: Obsolete CSS modifications

Patric_Nordstrom — Mon, 31 Mar 2025 16:20:15 GMT

The CSS can still be replaced in a custom theme. That said we're investigating other options for CSS injections.

Thanks,

Patric

Re: Obsolete CSS modifications

tan123qlik — Tue, 01 Apr 2025 08:07:06 GMT

I am using CSS to hide the home button (house) in the map object. How can I do that without Multi KPI.

Re: Obsolete CSS modifications

Or — Tue, 01 Apr 2025 08:23:47 GMT

It definitely sounds like there needs to be a CSS option to replace Multi KPI... I don't think there's ever going to be enough functionality built in to replace every single reasonable use case.