# Function to set component property

**URL:** <https://forum.inductiveautomation.com/t/function-to-set-component-property/15074>\
**Category:** Ignition\
**Created:** [August 15, 2017, 7:51pm UTC](https://forum.inductiveautomation.com/t/function-to-set-component-property/15074 "2017-08-15T19:51:46Z")\
**Posts on this page:** 1\
**Showing post:** 9

<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:** [April 4, 2018, 12:31pm UTC](https://forum.inductiveautomation.com/t/function-to-set-component-property/15074/9 "2018-04-04T12:31:40Z")

</div>

> [@pturmel](#):
>
> or were python-wrapped before the custom type converter was registered with Py.java2py()

If you visit [this thread](http://forum.inductiveautomation.com/t/transaction-groups-triggered-expression-item-updating-when-trigger-is-false/17196/13) you'll see that Ignition was not registering its wrapper at all. If you install the release candidate of Simulation Aids posted at the end of that thread, you won't have to use the getPropertyValue/setPropertyValue methods any more. The python property substitution for custom properties will "just work" in all cases.

---

_[View the full topic](https://forum.inductiveautomation.com/t/function-to-set-component-property/15074)._