# Need Help Controlling Tag Browser in Power Chart Component

**URL:** <https://forum.inductiveautomation.com/t/need-help-controlling-tag-browser-in-power-chart-component/106846>\
**Category:** Ignition\
**Tags:** ignition81, perspective\
**Created:** [May 30, 2025, 6:31am UTC](https://forum.inductiveautomation.com/t/need-help-controlling-tag-browser-in-power-chart-component/106846 "2025-05-30T06:31:07Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![nminchin](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/nminchin/32/6911_2.png) [@nminchin](https://forum.inductiveautomation.com/u/nminchin)\
**Post date:** [June 2, 2025, 8:47pm UTC](https://forum.inductiveautomation.com/t/need-help-controlling-tag-browser-in-power-chart-component/106846/4 "2025-06-02T20:47:01Z")

</div>

> [@michaeelphillips](#):
>
> You can use the `system.tag.getConfiguration()` function

You can read/write tag props, including writing new custom tag props, with `system.tag.readBlocking` and `system.tag.writeBlocking/Async`, which is less destructive than using `system.tag.getConfiguration()`.

By destructive, I mean using `getConfiguration` (and corresponding `system.tag.configure` to write changes) with tags within a UDT instance will override _all_ of the props set on them within the UDT definition thus essentially disconnecting their configuration from the definition. Unless you ensure to remove all of the keys except for `name` and `tagType` from the objects you get from `getConfiguration`.

I would highly recommend for this instance to use tag.read/write functions instead.

---

_[View the full topic](https://forum.inductiveautomation.com/t/need-help-controlling-tag-browser-in-power-chart-component/106846)._