# Tag Properties not available on OPC client browser

**URL:** <https://forum.inductiveautomation.com/t/tag-properties-not-available-on-opc-client-browser/87981>\
**Category:** Ignition\
**Created:** [March 27, 2024, 4:23pm UTC](https://forum.inductiveautomation.com/t/tag-properties-not-available-on-opc-client-browser/87981 "2024-03-27T16:23:48Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jacob\_Barlow](https://avatars.discourse-cdn.com/v4/letter/j/e99b99/32.png) [@Jacob\_Barlow](https://forum.inductiveautomation.com/u/Jacob_Barlow)\
**Post date:** [March 27, 2024, 4:23pm UTC](https://forum.inductiveautomation.com/t/tag-properties-not-available-on-opc-client-browser/87981/1 "2024-03-27T16:23:48Z")

</div>

Hey folks,

I had a question come in from a customer that I'm not sure about.

They're trying to view specific tag properties (units, description, scaling) via an OPC client connection. Is there a way to expose the entire tag configuration on the OPC server or a way to access those properties that I'm not aware of?

---

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [March 27, 2024, 4:30pm UTC](https://forum.inductiveautomation.com/t/tag-properties-not-available-on-opc-client-browser/87981/2 "2024-03-27T16:30:40Z")

</div>

No, they aren't exposed over OPC UA.

---

<div class="post-metadata">

**Author:** ![Jacob\_Barlow](https://avatars.discourse-cdn.com/v4/letter/j/e99b99/32.png) [@Jacob\_Barlow](https://forum.inductiveautomation.com/u/Jacob_Barlow)\
**Post date:** [March 27, 2024, 4:42pm UTC](https://forum.inductiveautomation.com/t/tag-properties-not-available-on-opc-client-browser/87981/3 "2024-03-27T16:42:18Z")

</div>

I didn't think so, but them asking for it kind of threw me for a loop thinking that might be an option.

Thanks Kevin

---

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [March 27, 2024, 4:43pm UTC](https://forum.inductiveautomation.com/t/tag-properties-not-available-on-opc-client-browser/87981/4 "2024-03-27T16:43:36Z")

</div>

I'm afraid that implementing something like that would just encourage people to subscribe to both every tag _and_ every tag property, and the number of monitored items would go up something like 10-20x (however many tag properties we exposed).

---

<div class="post-metadata">

**Author:** ![Jacob\_Barlow](https://avatars.discourse-cdn.com/v4/letter/j/e99b99/32.png) [@Jacob\_Barlow](https://forum.inductiveautomation.com/u/Jacob_Barlow)\
**Post date:** [March 27, 2024, 4:46pm UTC](https://forum.inductiveautomation.com/t/tag-properties-not-available-on-opc-client-browser/87981/5 "2024-03-27T16:46:32Z")

</div>

Oh, definitely. It seems the common thought process is "more data is more better", regardless of sense lmao. I'll see if there's a specific set that they want available and maybe I can just create a few reference tags for those properties. Cheers!