# Access to involved items in ScriptColumnData

**URL:** <https://resource.dopus.com/t/access-to-involved-items-in-scriptcolumndata/57758>\
**Category:** Help & Support\
**Tags:** script\
**Created:** [November 12, 2025, 9:54pm UTC](https://resource.dopus.com/t/access-to-involved-items-in-scriptcolumndata/57758 "2025-11-12T21:54:58Z")\
**Posts on this page:** 1\
**Showing post:** 9

<div class="post-metadata">

**Author:** ![errante](https://resource.dopus.com/user_avatar/resource.dopus.com/errante/32/61692_2.png) [@errante](https://resource.dopus.com/u/errante)\
**Post date:** [December 1, 2025, 8:30pm UTC](https://resource.dopus.com/t/access-to-involved-items-in-scriptcolumndata/57758/9 "2025-12-01T20:30:48Z")

</div>

Revisiting this.

To avoid issues like [this](https://resource.dopus.com/t/crash-when-trying-to-use-a-tab-var-as-a-cache/57929), what if the script could return `false` when Opus calls it for an item? If it does, Opus will call the script again. You could use that to build a list of items on the first call, return false, and then on the second call process all related items in bulk.

---

_[View the full topic](https://resource.dopus.com/t/access-to-involved-items-in-scriptcolumndata/57758)._