# Property not bindable Vision

**URL:** <https://forum.inductiveautomation.com/t/property-not-bindable-vision/55907>\
**Category:** Ignition\
**Tags:** ignition80, vision\
**Created:** [February 9, 2022, 2:03pm UTC](https://forum.inductiveautomation.com/t/property-not-bindable-vision/55907 "2022-02-09T14:03:59Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Remco\_Thijssen](https://avatars.discourse-cdn.com/v4/letter/r/9fc29f/32.png) [@Remco\_Thijssen](https://forum.inductiveautomation.com/u/Remco_Thijssen)\
**Post date:** [February 9, 2022, 2:03pm UTC](https://forum.inductiveautomation.com/t/property-not-bindable-vision/55907/1 "2022-02-09T14:03:59Z")

</div>

Hi there!

I have a question about property binding in Vision, if I want to set a property binding I don’t have all the properties to chose, for example I want to set the Enabled button to a different state using property binding, but I don’t have the option Enabled (see picture below),

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/5/9/5988828838c46eda1f86c5e78b323a8e0ac1d3b1.png)

When I use python script on a click event, the option is Enabled is possible, but I want it on a state from the PLC.

Is there a way to enabled the options which is missing, or an other solution?

Thankyou all

---

<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:** [February 9, 2022, 3:15pm UTC](https://forum.inductiveautomation.com/t/property-not-bindable-vision/55907/2 "2022-02-09T15:15:10Z")

</div>

No, the source of a property binding must be a one that fires propertyChange events. There’s no magic that could make a property do so if not built in. The developers of a component mark which properties do that, so the designer can show them as eligible source properties.

If you used a binding to drive `enabled` on a component, create a custom boolean property and move the original binding there. Then bind enabled to the new component. Wherever else you need that status in a binding, bind to the custom property.