on 07-11-2020 12:21 PM
Hi,
I see that SAC table component has some poor user experience with 10+ columns, long headers, 100+ rows etc.
Especially scrolling and table resizing is a huge problem. I see a lot of similar enhancement requests (I don't understand why it was designed in that way in the first place). The beta table is all about performance, it doesn't solve other problems.
Also, it's strange to see, dimension members can not be merged to cells for alignment purposes. (e.g. get year value on top of all months)
How do you manage such tables? Are your all end users happy with the experience?
https://influence.sap.com/sap/ino/#/idea/242046
https://influence.sap.com/sap/ino/#/idea/240615
https://influence.sap.com/sap/ino/#/idea/240391
https://influence.sap.com/sap/ino/#/idea/218764
Regards,
Erdem
Hi Erdem,
My few suggestions,
1. Use new setting 'Optimized table'(beta) option which is introduced in 2020 QRC2 , this setting can improve table performance and scrolling experience. Search 'Enhanced table experience' in this link.
2. Uncheck 'Responsive and flexible column width' if number of columns is often changing
3. Set row height by pixel in table style definition and optimize column width by mouse dragging if needed.
Best regards, William
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi William,
Optimized table has better performance for in-cell charts rendering with limits only. I've compared it to standard table with 10+ columns and 100+ rows without any in-cell charts, the performance was worse.
The other options does not help users to notice that table has more rows or columns. It's only possible if you click on the table.
Agree with you Erdem!
And some needed features like 'growing table vertically' is only released for canvas, not for responsive and not for beta tables... why??
And beta table still has many issues in my experience, including scrolling down & flickering of screen which I understood will still not be solved in 2020 QRC3, somehow only targeted for QRC4. While customers need it today, especially obvious bug fixing to get a stable experience.
User | Count |
---|---|
93 | |
11 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.