# \[BUG-14025\] Menu Tree selected value

**URL:** <https://forum.inductiveautomation.com/t/bug-14025-menu-tree-selected-value/27797>\
**Category:** Ignition Early Access\
**Created:** [August 27, 2019, 1:33pm UTC](https://forum.inductiveautomation.com/t/bug-14025-menu-tree-selected-value/27797 "2019-08-27T13:33:24Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![Shindig](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/shindig/32/8955_2.png) [@Shindig](https://forum.inductiveautomation.com/u/Shindig)\
**Post date:** [August 27, 2019, 1:33pm UTC](https://forum.inductiveautomation.com/t/bug-14025-menu-tree-selected-value/27797/1 "2019-08-27T13:33:24Z")

</div>

Hi  
Is it possible to get the value of the item selected / click on on a menu tree?  
Thanks

---

<div class="post-metadata">

**Author:** ![cmallonee](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/cmallonee/32/6416_2.png) [@cmallonee](https://forum.inductiveautomation.com/u/cmallonee)\
**Post date:** [August 27, 2019, 2:09pm UTC](https://forum.inductiveautomation.com/t/bug-14025-menu-tree-selected-value/27797/2 "2019-08-27T14:09:33Z")

</div>

The Menu Tree has on `onItemClicked` Event, but we recently found that the event is not behaving correctly. When the event is repaired, you should be able to script against an event object with the following attributes:

- enabled (bool): Whether the item interacted with is enabled.
- label (str): Text to display for this option.
- path (list): A list containing the item indexes leading to the item that was clicked.
- target (str): A url (external) or a mounted path to a page.

---

<div class="post-metadata">

**Author:** ![Shindig](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/shindig/32/8955_2.png) [@Shindig](https://forum.inductiveautomation.com/u/Shindig)\
**Post date:** [August 27, 2019, 2:16pm UTC](https://forum.inductiveautomation.com/t/bug-14025-menu-tree-selected-value/27797/3 "2019-08-27T14:16:18Z")

</div>

Thanks for your reply. Is there any workaround available for the time being?

---

<div class="post-metadata">

**Author:** ![cmallonee](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/cmallonee/32/6416_2.png) [@cmallonee](https://forum.inductiveautomation.com/u/cmallonee)\
**Post date:** [August 27, 2019, 2:35pm UTC](https://forum.inductiveautomation.com/t/bug-14025-menu-tree-selected-value/27797/4 "2019-08-27T14:35:06Z")

</div>

Not at this time, no.

---

<div class="post-metadata">

**Author:** ![osolorzano](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/osolorzano/32/6432_2.png) [@osolorzano](https://forum.inductiveautomation.com/u/osolorzano)\
**Post date:** [August 27, 2019, 6:39pm UTC](https://forum.inductiveautomation.com/t/bug-14025-menu-tree-selected-value/27797/5 "2019-08-27T18:39:18Z")

</div>

If it helps, the fix for this has been implemented and tested. It should be in one of the upcoming nightly builds for 8.0.5 but has missed the cutoff for 8.0.4 currently.

---

<div class="post-metadata">

**Author:** ![Shindig](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/shindig/32/8955_2.png) [@Shindig](https://forum.inductiveautomation.com/u/Shindig)\
**Post date:** [August 27, 2019, 7:20pm UTC](https://forum.inductiveautomation.com/t/bug-14025-menu-tree-selected-value/27797/6 "2019-08-27T19:20:46Z")

</div>

Thanks for the update …I’ll keep an eye out for it.

---

<div class="post-metadata">

**Author:** ![osolorzano](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/osolorzano/32/6432_2.png) [@osolorzano](https://forum.inductiveautomation.com/u/osolorzano)\
**Post date:** [September 23, 2019, 6:09pm UTC](https://forum.inductiveautomation.com/t/bug-14025-menu-tree-selected-value/27797/7 "2019-09-23T18:09:25Z")

</div>

Oh yeah, this feature was added in the 8.0.5 nightly build that was uploaded 8/29. So should be in the latest 8.0.5 builds.  
As a side note, a similar issue occurs with the tree component which is currently being fixed/tested and will be in an upcoming 8.0.5 nightly build.
