# How to store the Thread that results from the system.util.invokeAsynchronous call in a container property?

**URL:** <https://forum.inductiveautomation.com/t/how-to-store-the-thread-that-results-from-the-system-util-invokeasynchronous-call-in-a-container-property/81212>\
**Category:** Ignition\
**Tags:** vision, scripting\
**Created:** [October 31, 2023, 1:06am UTC](https://forum.inductiveautomation.com/t/how-to-store-the-thread-that-results-from-the-system-util-invokeasynchronous-call-in-a-container-property/81212 "2023-10-31T01:06:11Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![dustin.cooper](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/dustin.cooper/32/29963_2.png) [@dustin.cooper](https://forum.inductiveautomation.com/u/dustin.cooper)\
**Post date:** [October 31, 2023, 3:35am UTC](https://forum.inductiveautomation.com/t/how-to-store-the-thread-that-results-from-the-system-util-invokeasynchronous-call-in-a-container-property/81212/3 "2023-10-31T03:35:57Z")

</div>

I tried to do something similar in [this post](https://forum.inductiveautomation.com/t/ign-5244-using-class-instance-as-view-custom-object-property/53676). There is a workaround proposed using the system globals dictionary in that thread.

Essentially, Ignition doesn’t currently expose Python objects natively, but rather as “script wrapper” objects. Would be cool if the dev team had many some progress on it 😉

---

_[View the full topic](https://forum.inductiveautomation.com/t/how-to-store-the-thread-that-results-from-the-system-util-invokeasynchronous-call-in-a-container-property/81212)._