Feature: State Saving for Workshop Pivot Tables

Product Feedback
1

Ask: Expose row groupings & aggregations as workshop variables, so that state can be saved.

Sample scenario:

  1. FDE builds a rich pivot table, with multiple complex aggregation
  2. Some row groupings are set to expandable/hidden to allow for both high-level summary & low level drilldown
  3. Some aggregations are also set to hidden
  4. User agrees to the defaults shown & hidden
  5. PAIN: Power users want to create saved views with a custom setting for row groupings & aggregations. They have multiple views, and also want to share them with other users. This is not possible, instead they need to start from the defaults and adjust them each time.
2

Pivot tables are so powerful, but there are soooo many things that could be improved on them. And bugs to be fixed…

https://community.palantir.com/t/enhancement-proposals-to-unleash-the-potential-of-pivot-tables/3770

Unfortuntely, I am not sure if we will ever see that day :smiling_face_with_tear:

We decided to develop our own as custom widget. It works, but as long as custom widgets can’t easily be made object type agnostic, it is not as plug-and-play as the built-in.

3

Thanks for surfacing the other thread, very useful requests there.

For the custom widgets, did you hit any limitations with the number of simultaneous row groupings, buckets or memory?

If I recall, workshop is:

  • 7 inner groupings
  • 10,000 buckets
  • ~100MB