Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
I saw news that Qlik is retiring the Table visualization and replacing it with the new Straight Table visualization. If Qlik follows through with that it would be severely detrimental to our reporting. Setting aside the additional work our developers would have to put in replacing/reformatting every existing table across the companies we work with, the Straight Table visualization lacks much of the functionality that made the simple Table visualization so compelling. As an example, a user can't easily use the search magnifying glass to filter a column - that is now buried behind three clicks in the hamburger menu that appears on each column in the Straight Table. Is there any way to submit feedback to Qlik and tell them this is a terrible idea and they should keep the old Table visualization?
Hi @rcooper : you can definitely use the Ideation page to provide feedback to our product team. I will also report your feedback to the team.
Hi @rcooper : you can definitely use the Ideation page to provide feedback to our product team. I will also report your feedback to the team.
Posting an idea that is "Keep the old object" is basically yelling into the void, so I'd suggest posting an Idea of what needs to be added to the new object to make it usable.
Completely agree with you @rcooper , the new table is not very user friendly.
Sort and search is not easy with the new table.
And it's the same from the developer side, add dimensions and measure take too much time...
+1 for retaining the classic Table visualization. I really want to like the new Straight Table, but it is still lacking important functionality. In addition to what has already been noted about difficulties with columnar sort and search, I will add the following:
1. The new Straight Table lacks the ability to (re)order columns without enabling Chart Exploration. In the classic visualization, columns can be easily reordered via drag-and-drop.
2. There is no way to automatically order Measures and Dimensions in the Chart Exploration pane, e.g. alphabetically, by state (active or alternative column), etc. Manual reordering makes for a frustrating user experience, particularly when the number of possible Measures and Dimensions is large and may require scrolling to expose the entire list.
3. More ideally, Measures and Dimensions should be in separate categories within the Chart Exploration pane. Presently, they are intermingled with only a faint gray-on-gray icon to distinguish between the two.
The new visualization has some nice enhancements, but the absence of important useability features makes it a non-starter for many applications.
Hello, we had the same conclusion here, we understand the evolution of the table and are ready to migrate our old tables into the new format but in the current state it is simply impossible, the lack of quick access to magnifying glass (big impact) and reordering is a regression that has received many complains for our users.
For those responding here or lurking, I've collected a list of open Ideas for the Straight Table object that are currently open. You're welcome to review and vote for ones you like, though I can't say how much of an impact that might have on Qlik's priorities. If anything is missing from my list and/or you open a new idea for it, leave a note in this thread as well.
@Daniele_Purrone Maybe we can get a pinned post for the Straight Table open ideas somewhere so it's easier for people to find? I think this is an issue that concerns a lot of people so it may pay to get ahead of the questions.
Open Ideas as of July 10th 2025:
Search directly from header:
https://ideation.qlik.com/app/#/case/384409?cpid=c99f681a-737c-4909-b826-ab563fedfe31
Mark certain columns as "Mandatory":
https://ideation.qlik.com/app/#/case/443935?cpid=ec180be3-420f-4877-bda4-d7ce1ef2a6cc
Export CSS styling to Excel:
https://ideation.qlik.com/app/#/case/396807?cpid=284d9c4d-fbb2-4240-8dc2-4d9df76ed828
Add Subtotals:
https://ideation.qlik.com/app/#/case/280077?cpid=f5122742-87ac-43d5-b8d5-51e842394cf3
(Author's note: This is an idea from the original Table object, near as I can tell, and I'm pretty sure it's on Qlik's "Not going to happen" list)
Good job summarizing already open ideas, and good idea to pin it on ideation!
Thanks, @Daniele_Purrone !