# Feature: State Saving for Workshop Pivot Tables

**URL:** <https://community.palantir.com/t/feature-state-saving-for-workshop-pivot-tables/6585>\
**Category:** Product Feedback\
**Tags:** workshop\
**Created:** [May 14, 2026, 7:53am UTC](https://community.palantir.com/t/feature-state-saving-for-workshop-pivot-tables/6585 "2026-05-14T07:53:00Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![dudonwai](https://yyz1.discourse-cdn.com/palantir/user_avatar/community.palantir.com/dudonwai/32/5842_2.png) [@dudonwai](https://community.palantir.com/u/dudonwai)\
**Post date:** [May 14, 2026, 7:53am UTC](https://community.palantir.com/t/feature-state-saving-for-workshop-pivot-tables/6585/1 "2026-05-14T07:53:00Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![Phil-M](https://yyz1.discourse-cdn.com/palantir/user_avatar/community.palantir.com/phil-m/32/4134_2.png) [@Phil-M](https://community.palantir.com/u/Phil-M)\
**Post date:** [May 14, 2026, 9:08pm UTC](https://community.palantir.com/t/feature-state-saving-for-workshop-pivot-tables/6585/2 "2026-05-14T21:08:40Z")

</div>

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](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 🥲

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.

---

<div class="post-metadata">

**Author:** ![dudonwai](https://yyz1.discourse-cdn.com/palantir/user_avatar/community.palantir.com/dudonwai/32/5842_2.png) [@dudonwai](https://community.palantir.com/u/dudonwai)\
**Post date:** [May 17, 2026, 4:25pm UTC](https://community.palantir.com/t/feature-state-saving-for-workshop-pivot-tables/6585/3 "2026-05-17T16:25:17Z")

</div>

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