Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
I have a table object (non-pivot) with about 100 rows. However, when the user scrolls down the table, eventually the table ends and a Load More button appears which the user has to click in order to see the rest of the rows.
This is very annoying to users who just want to continuously scroll through the data, especially when a bar chart on the same page shows all 100 bars at once. Is there any way to force the table to load all of the data at once?
Hi Tim, I've you tried on Firefox ?
It appears to act the same on Firefox. Regardless, I'm making this for clients who use IE and Chrome.
I don't have this behavior on Firefox ?
Anyway, Qlik should provide a solution to let us choose the way we want to display the data as most of users use IE or Chrome.
+1 this request. Our users are also not happy with this behavior.
Same problem here. Does anybody has a solution for this?
Strange thing is that I don't have this button when I login using my own laptop.
Using :
- the same Qlik user
- the same Windows user
- the same Browsers (IE, firefox and Chrome)
- the same URL
Even when I log on to a terminal server on premise, I dont have the button.
But if I do the same from the customers PC or Laptop the button appears when scrolling down.
Does anybody know when the button appears and when not? I can not find any locigal beheaver in it.
Qlik Sense 3.2 SR4
Qliksenseserver 10.28.2
You don't have the button because you are able to see all the rows? Or you are not able to load the remaining rows?
Wel some users do have the button and others dont.
When I scroll down it just gives me all the rows (or it loads them while scrolling) and that is what we want.
People who do have the button, they scroll down, the list stops, the button appears, and after clicking the button the next page(s) shows.
The button gives the user the feeling that the data is incomplete.
Do you know what triggers the button? Why there is a difference between sessions?
It may be tied to the Display properties. Play around with the resolution and see if that makes a difference.