# Best Way to Return Data from Vision Popup

**URL:** <https://forum.inductiveautomation.com/t/best-way-to-return-data-from-vision-popup/92912>\
**Category:** Ignition\
**Tags:** ignition81, vision\
**Created:** [July 8, 2024, 5:49pm UTC](https://forum.inductiveautomation.com/t/best-way-to-return-data-from-vision-popup/92912 "2024-07-08T17:49:41Z")\
**Posts on this page:** 1\
**Showing post:** 20

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [July 9, 2024, 6:36pm UTC](https://forum.inductiveautomation.com/t/best-way-to-return-data-from-vision-popup/92912/20 "2024-07-09T18:36:37Z")

</div>

Hmmm, this is one of the `PyComponentWrapper` gotchas, where jython won't recognize custom properties nor component custom methods.

If you can, install my Integration Toolkit to fix that for all cases. See more here, including a non-module solution:

> [@Why can't custom properties and methods be accessed from a component that is obtained using SwingUtilities.getAncestorOfClass?](https://forum.inductiveautomation.com/t/why-cant-custom-properties-and-methods-be-accessed-from-a-component-that-is-obtained-using-swingutilities-getancestorofclass/78606/2):
>
> Custom properties are added to the java standard jython conversion by IA's PyComponentWrapper. For a complete discussion, read this entire topic: TL/DR: Install my Simulation Aids Integration Toolkit module to magically fix this, everywhere in Ignition. There is no other solution until IA eventually does this first party. See below.

---

_[View the full topic](https://forum.inductiveautomation.com/t/best-way-to-return-data-from-vision-popup/92912)._