# Component's custom property in python class **URL:** \ **Category:** Ignition\ **Tags:** ignition80, vision, scripting\ **Created:** [September 23, 2022, 4:14pm UTC](https://forum.inductiveautomation.com/t/components-custom-property-in-python-class/64427 "2022-09-23T16:14:21Z")\ **Posts on this page:** 1\ **Showing post:** 2
**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:** [September 23, 2022, 11:03pm UTC](https://forum.inductiveautomation.com/t/components-custom-property-in-python-class/64427/2 "2022-09-23T23:03:07Z")
There is a long-standing flaw in Vision's delivery of a `PyComponentWrapper`--that is, it only delivers a fully-functional component from certain component methods. For other cases, the work-around is to install my [Simulation Aids](https://inductiveautomation.com/moduleshowcase/module/automation-professionals-llc-simulation-aids) module, which inserts a jython adapter to ensure Vision components are always properly wrapped. If you want the gory details, read this entire topic: > [@Transaction groups triggered expression item updating when trigger is false](https://forum.inductiveautomation.com/t/transaction-groups-triggered-expression-item-updating-when-trigger-is-false/17196): > > Having a transaction group with triggered expression/SQL items and a run always expression item used as trigger for the group. When the trigger (run always item) references any of the triggered items, these updates even though the trigger is false. Is there any way to stop this behavior as the triggered items stores relevant information I need between triggers? { The flaw affects access to custom component **methods** , too. } --- _[View the full topic](https://forum.inductiveautomation.com/t/components-custom-property-in-python-class/64427)._