# Perspective MenuTree Additional props in Items

**URL:** <https://forum.inductiveautomation.com/t/perspective-menutree-additional-props-in-items/24398>\
**Category:** Ignition Early Access\
**Created:** [April 25, 2019, 4:34pm UTC](https://forum.inductiveautomation.com/t/perspective-menutree-additional-props-in-items/24398 "2019-04-25T16:34:34Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![WildeKurt](https://avatars.discourse-cdn.com/v4/letter/w/50afbb/32.png) [@WildeKurt](https://forum.inductiveautomation.com/u/WildeKurt)\
**Post date:** [April 25, 2019, 4:34pm UTC](https://forum.inductiveautomation.com/t/perspective-menutree-additional-props-in-items/24398/1 "2019-04-25T16:34:34Z")

</div>

I’m driving the items prop on a perspective menuTree via database table. I’d like to store the item’s ID along with it’s other properties. I’m able to do it and the tree behaves appropriately, however a little red error icon appears in the designer telling me not to do it (i.e. ‘additional properties are not allowed’). Should I approach this a different way?

---

<div class="post-metadata">

**Author:** ![ggross](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/ggross/32/12668_2.png) [@ggross](https://forum.inductiveautomation.com/u/ggross)\
**Post date:** [May 14, 2019, 11:42pm UTC](https://forum.inductiveautomation.com/t/perspective-menutree-additional-props-in-items/24398/2 "2019-05-14T23:42:35Z")

</div>

Hi @WildeKurt,

While the error appears, nothing prevents additional properties from being used within Perspective. The danger in adding properties like this is one of the following things could occur:

1. The property you add could be an actual property that is hidden by default for the component. This could lead to unintended consequences when using component.
2. In the future, we could add that property causing similar unintended consequences that may impact your users when you least expect it.

What we would recommend doing is bind the SQL Query with the additional content to a custom property. Then bind `items` to the custom property you created using a transform to only return the specific properties our schema has defined. You would then use scripting within components to match up the current menu tree with the values your project needs.

Garth

---

<div class="post-metadata">

**Author:** ![WildeKurt](https://avatars.discourse-cdn.com/v4/letter/w/50afbb/32.png) [@WildeKurt](https://forum.inductiveautomation.com/u/WildeKurt)\
**Post date:** [May 15, 2019, 12:03pm UTC](https://forum.inductiveautomation.com/t/perspective-menutree-additional-props-in-items/24398/3 "2019-05-15T12:03:21Z")

</div>

Thanks, that seems like a reasonable solution.

---

<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:** [May 15, 2019, 12:42pm UTC](https://forum.inductiveautomation.com/t/perspective-menutree-additional-props-in-items/24398/4 "2019-05-15T12:42:15Z")

</div>

I think the ability to add custom properties (nearly) anywhere is valuable and helps keep code simple. I’d like to see the property name ‘custom’ be reserved for such use everywhere, similar to the way it works for session and view.