# Augment interactive table widget to allow for data pull rather than automatic real-time subscription

**URL:** <https://community.tulip.co/t/augment-interactive-table-widget-to-allow-for-data-pull-rather-than-automatic-real-time-subscription/12058>\
**Category:** Product Suggestions\
**Created:** [July 26, 2024, 1:00pm UTC](https://community.tulip.co/t/augment-interactive-table-widget-to-allow-for-data-pull-rather-than-automatic-real-time-subscription/12058 "2024-07-26T13:00:37Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![sebme](https://avatars.discourse-cdn.com/v4/letter/s/439d5e/32.png) [@sebme](https://community.tulip.co/u/sebme)\
**Post date:** [July 26, 2024, 1:00pm UTC](https://community.tulip.co/t/augment-interactive-table-widget-to-allow-for-data-pull-rather-than-automatic-real-time-subscription/12058/1 "2024-07-26T13:00:37Z")

</div>

At present, Tulip’s interactive table widget automatically subscribes to the data updates of the associated table / variable. In our observation, this can become a significant resource hog because Tulip will constantly redraw the UI; particularly if multiple table widgets need to be displayed and the underlying data is changing rather often.

Unless there is a way to improve the refresh and display of data to be less resource intensive, a possible alternative would be to explicitly allow for an option to disable auto-updates and in this case switch to a pull-data approach instead. At present this can be achieved by fetching the required data via a Table API connector call and thus making the result a static variable. But this is a significant development overhead and hence reduces one’s ability to quickly adapt to changing user needs.

---

<div class="post-metadata">

**Author:** ![thorsten.langner](https://avatars.discourse-cdn.com/v4/letter/t/4bbf92/32.png) [@thorsten.langner](https://community.tulip.co/u/thorsten.langner)\
**Post date:** [July 29, 2024, 9:49am UTC](https://community.tulip.co/t/augment-interactive-table-widget-to-allow-for-data-pull-rather-than-automatic-real-time-subscription/12058/2 "2024-07-29T09:49:28Z")

</div>

As a workaround, you can pull the data with the Table API into a variable and then reload when needed.  
Another benefit is, you can prefilter the data on pull and add another Filter in the interactive table widged. Thats the only way I know to combine AND & OR filters…

---

<div class="post-metadata">

**Author:** ![sebme](https://avatars.discourse-cdn.com/v4/letter/s/439d5e/32.png) [@sebme](https://community.tulip.co/u/sebme)\
**Post date:** [July 29, 2024, 5:16pm UTC](https://community.tulip.co/t/augment-interactive-table-widget-to-allow-for-data-pull-rather-than-automatic-real-time-subscription/12058/3 "2024-07-29T17:16:43Z")

</div>

> […] At present this can be achieved by fetching the required data via a Table API connector call and thus making the result a static variable. But this is a significant development overhead and hence reduces one’s ability to quickly adapt to changing user needs.

🙃

---

<div class="post-metadata">

**Author:** ![thorsten.langner](https://avatars.discourse-cdn.com/v4/letter/t/4bbf92/32.png) [@thorsten.langner](https://community.tulip.co/u/thorsten.langner)\
**Post date:** [July 30, 2024, 6:39am UTC](https://community.tulip.co/t/augment-interactive-table-widget-to-allow-for-data-pull-rather-than-automatic-real-time-subscription/12058/4 "2024-07-30T06:39:46Z")

</div>

🙈  
sorry. my bad. Did I stop reading early? 🤔