You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[AnalyticalTable]: Sticky first n columns, group header and table footer #6727
No.
Currently, the AnalyticalTable does not support stick/frozen first n columns, group header and footer, and these are new requirements from UX design and customer's requirement.
Describe the solution you'd like
Can we add 3 features for AnalyticalTable:
Sticky (frozen) first n columns when scroll to right
Support group header
Support footer
Here is screenshot from UX design:
Describe alternatives you've considered
No response
Additional Context
No response
Organization
SAP
Declaration
I’m not disclosing any internal or sensitive information.
Unfortunately, implementing these features is challenging due to the current structure of the AnalyticalTable and would require a complete refactoring of the component, which we don’t have the capacity to tackle in the foreseeable future.
Unfortunately, implementing these features is challenging due to the current structure of the AnalyticalTable and would require a complete refactoring of the component, which we don’t have the capacity to tackle in the foreseeable future.
Hi @Lukas742 ,
Sorry to heard that, and I will let UX and PM know.
These features are important to compensation and variable pay worksheet table, the table will be very big and could be configured by customer.
So if AnalyticalTable cannot be enhancement to support these feature in the foreseeable future, do you have any suggestion to us as an alternative?
Hi @Lukas742 ,
I synced with our UX and PMs, they want to raise priority, and want to learn from you team: can you give us a ETA even though it is in the foreseeable future?
Hi @LukewenSAP
we talked about this topic internally and decided to revisit it early next year. While I can’t promise any results yet, we’ll try to create a PoC and see how it goes. We’ll update this issue once we have more to share.
we're also in the need of this feature for a SAP Signavio DMN use case. I can provide more information if necessary, but for now, we have made a commitment to an external customer to deliver something that would rely on this functionality by the end of Q2. We are still in the investigation phase, but this feature would make us use the analytic table most likely.
On your board I see that this issue is planned for delivery on Q1 this year, is this information correct?
we plan to finish an initial experimental draft (PoC) of a new table implementation that includes these features at the end of Q1. (see this comment) Apart from that the initial feature set will still be limited.
Also, since it will only be a draft, the table will be in experimental state, therefore API changes might occur in between versions. A stable release is not yet on the horizon, as we can't assess how many resources we can put into this topic.
Just to avoid confusion, this will be a new version of the current analytic table not an entirely different table, right?
Will this PoC / draft version be made available publicly?
The current implementation of the AnalyticalTable doesn't allow implementing the requested features without a complete rebuild of the table. Due to limited capacity this is not feasible for us, as these features would require a huge refactoring of the component which in turn requires a lot of testing to not break existing implementation. Also, the underlying library (react-table) we use to create the table had a major update a while ago, which is unfortunately not compatible with our API, that's why we're still stuck on v7 which isn't maintained anymore.
That's why decided to create a new table, while still maintaining the old AnalyticalTable component.
So, to answer your questions, we won't implement these features in the AnalyticalTable component, but in a new component. A first draft should be available at the end of Q1.
So that means a new experimental version of the analytics table based on v8 of react table is suppose to be released at the end of Q1/25, it will be experimental but in theory we could start using it, right?
Hi all,
unfortunately, we have to delay the initial draft release of AnalyticalTableV2 (working title) as our priorities shifted in March and I haven’t had time to work on it since. The new ETA is now the end of Q2. Regarding the full feature, there is currently no ETA, as it has been put on hold.
Thanks, @Lukas742, and everybody's efforts and updates.
I think it's OK for us to be delayed because our project has been shifted as well for some reason.
Will keep an eye on the progress #7134 and keep in sync with UX and PM.
I'm glad to let you know that we've implemented the sticky column feature. Once this PR is merged and the next minor version is published, you'll be able to use the experimental useStickyColumns plugin hook, enabling column-freeze capabilities for the table.
We're aiming to release it in early October. If you'd like to try it earlier, please let me know and I'll publish a release candidate.
Activity
Lukas742 commentedon Dec 11, 2024
Hi @LukewenSAP
Unfortunately, implementing these features is challenging due to the current structure of the AnalyticalTable and would require a complete refactoring of the component, which we don’t have the capacity to tackle in the foreseeable future.
LukewenSAP commentedon Dec 12, 2024
Hi @Lukas742 ,
Sorry to heard that, and I will let UX and PM know.
These features are important to compensation and variable pay worksheet table, the table will be very big and could be configured by customer.
So if AnalyticalTable cannot be enhancement to support these feature in the foreseeable future, do you have any suggestion to us as an alternative?
LukewenSAP commentedon Dec 12, 2024
Hi @Lukas742 ,
I synced with our UX and PMs, they want to raise priority, and want to learn from you team: can you give us a ETA even though it is in the foreseeable future?
Thanks!
Luke Wen
Lukas742 commentedon Dec 17, 2024
Hi @LukewenSAP
we talked about this topic internally and decided to revisit it early next year. While I can’t promise any results yet, we’ll try to create a PoC and see how it goes. We’ll update this issue once we have more to share.
LukewenSAP commentedon Dec 17, 2024
Thanks @Lukas742 for your kindly updating!
I will sync these information to PM and UX so that they can re-schedule the plan.
Thanks!
Luke
steffektif commentedon Feb 17, 2025
Hey hey
we're also in the need of this feature for a SAP Signavio DMN use case. I can provide more information if necessary, but for now, we have made a commitment to an external customer to deliver something that would rely on this functionality by the end of Q2. We are still in the investigation phase, but this feature would make us use the analytic table most likely.
On your board I see that this issue is planned for delivery on Q1 this year, is this information correct?
Best
Stef
Lukas742 commentedon Feb 17, 2025
Hi @steffektif
we plan to finish an initial experimental draft (PoC) of a new table implementation that includes these features at the end of Q1. (see this comment) Apart from that the initial feature set will still be limited.
Also, since it will only be a draft, the table will be in experimental state, therefore API changes might occur in between versions. A stable release is not yet on the horizon, as we can't assess how many resources we can put into this topic.
steffektif commentedon Feb 17, 2025
Hey Lukas, thanks for the quick response.
Just to avoid confusion, this will be a new version of the current analytic table not an entirely different table, right?
Will this PoC / draft version be made available publicly?
Lukas742 commentedon Feb 18, 2025
@steffektif sorry I should have been clearer.
The current implementation of the
AnalyticalTabledoesn't allow implementing the requested features without a complete rebuild of the table. Due to limited capacity this is not feasible for us, as these features would require a huge refactoring of the component which in turn requires a lot of testing to not break existing implementation. Also, the underlying library (react-table) we use to create the table had a major update a while ago, which is unfortunately not compatible with our API, that's why we're still stuck on v7 which isn't maintained anymore.That's why decided to create a new table, while still maintaining the old
AnalyticalTablecomponent.So, to answer your questions, we won't implement these features in the
AnalyticalTablecomponent, but in a new component. A first draft should be available at the end of Q1.steffektif commentedon Feb 18, 2025
Thanks Lukas!
So that means a new experimental version of the analytics table based on v8 of react table is suppose to be released at the end of Q1/25, it will be experimental but in theory we could start using it, right?
Lukas742 commentedon Feb 18, 2025
@steffektif Correct :)
Lukas742 commentedon Mar 24, 2025
Hi all,
unfortunately, we have to delay the initial draft release of
AnalyticalTableV2(working title) as our priorities shifted in March and I haven’t had time to work on it since.The new ETA is now the end of Q2.Regarding the full feature, there is currently no ETA, as it has been put on hold.You can follow the progress here.
LukewenSAP commentedon Mar 24, 2025
Thanks, @Lukas742, and everybody's efforts and updates.
I think it's OK for us to be delayed because our project has been shifted as well for some reason.
Will keep an eye on the progress #7134 and keep in sync with UX and PM.
Thanks!
Luke Wen
Lukas742 commentedon Sep 3, 2026
Hi everyone,
I'm glad to let you know that we've implemented the sticky column feature. Once this PR is merged and the next minor version is published, you'll be able to use the experimental useStickyColumns plugin hook, enabling column-freeze capabilities for the table.
We're aiming to release it in early October. If you'd like to try it earlier, please let me know and I'll publish a release candidate.
LukewenSAP commentedon Sep 3, 2026
Good new! It's good to know about this update; thanks, Lukas and team! I'll let our PM/UX know about this upcoming update.