# \[BUG?\] Private custom property returns undefined in popup title

**URL:** <https://forum.inductiveautomation.com/t/bug-private-custom-property-returns-undefined-in-popup-title/108129>\
**Category:** Ignition\
**Tags:** perspective, ignition81\
**Created:** [July 4, 2025, 6:22am UTC](https://forum.inductiveautomation.com/t/bug-private-custom-property-returns-undefined-in-popup-title/108129 "2025-07-04T06:22:54Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![andrew.budaiev](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/andrew.budaiev/32/72921_2.png) [@andrew.budaiev](https://forum.inductiveautomation.com/u/andrew.budaiev)\
**Post date:** [July 4, 2025, 2:08pm UTC](https://forum.inductiveautomation.com/t/bug-private-custom-property-returns-undefined-in-popup-title/108129/3 "2025-07-04T14:08:18Z")

</div>

Thanks, that’s good to know. I’ve been reading this topic and I think I took it too literally.

> [@Perspective Property Access Modes](https://forum.inductiveautomation.com/t/perspective-property-access-modes/97927/4):
>
> There's basically no cases where a custom prop shouldn't be made private, and it'll probably eventually be the default state for them. Offline mode may complicate that a little bit, eventually, but yeah, basically, there's no way to interact with custom props on the frontend outside of JS injection or a custom frontend component, so there's no harm in making them private.

---

_[View the full topic](https://forum.inductiveautomation.com/t/bug-private-custom-property-returns-undefined-in-popup-title/108129)._