# \[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:** 3\
**Page:** 1

<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, 6:22am UTC](https://forum.inductiveautomation.com/t/bug-private-custom-property-returns-undefined-in-popup-title/108129/1 "2025-07-04T06:22:54Z")

</div>

When passing a `private` custom property to a popup window's title via a Popup Action, the value returns as **undefined** instead of the expected property value. Is it normal or a bug? 🤷

P.S. I haven't tried it via script.

![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/7/f/7f7e5a9ca9cad8b7adc7c3a7aa7e41d9b2d6baac.png)

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/e/8/e843778f6bde93932a74bd99705ea8e006805875.png)

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/1/5/15d7d739e56f86575d885eb33bf7e35633db095d.png)

---

<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:** [July 4, 2025, 1:18pm UTC](https://forum.inductiveautomation.com/t/bug-private-custom-property-returns-undefined-in-popup-title/108129/2 "2025-07-04T13:18:44Z")

</div>

Actions other that Script run in the browser, and therefore do not have access to private properties (that's the point--private means it stays in the gateway).

---

<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.