# Address Description In Perspective

**URL:** <https://forum.inductiveautomation.com/t/address-description-in-perspective/95647>\
**Category:** General Discussion\
**Tags:** perspective\
**Created:** [September 6, 2024, 6:17pm UTC](https://forum.inductiveautomation.com/t/address-description-in-perspective/95647 "2024-09-06T18:17:03Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Shaun\_Thobe](https://avatars.discourse-cdn.com/v4/letter/s/e19b73/32.png) [@Shaun\_Thobe](https://forum.inductiveautomation.com/u/Shaun_Thobe)\
**Post date:** [September 6, 2024, 6:17pm UTC](https://forum.inductiveautomation.com/t/address-description-in-perspective/95647/1 "2024-09-06T18:17:03Z")

</div>

I have a Mitsubishi PLC where I have defined many addresses in the device setup as shown below.

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/a/0/a06994055dbaeb515333a8f007be3d5b34647b24.png)

I have defined a "description" for all of the address I have added. However, when I go into perspective and pull the tags up I can see the browse path and address through tag items but I cannot see the description.

Is there a way to see the address description in Perspective so I can use it in bindings for other objects?

---

<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:** [September 6, 2024, 7:11pm UTC](https://forum.inductiveautomation.com/t/address-description-in-perspective/95647/2 "2024-09-06T19:11:12Z")

</div>

Sadly these Description fields on drivers that have a tag configuration page like this are a wasted effort.

They get exposed over OPC UA in the Description attribute, but there's nothing in Ignition that actually uses or reads that Description attribute when the tags are created.

Your effort would be better spent defining the Documentation tag property after the tags have been created _in Ignition_, which you would then be able to read in other parts of Ignition.

---

<div class="post-metadata">

**Author:** ![Shaun\_Thobe](https://avatars.discourse-cdn.com/v4/letter/s/e19b73/32.png) [@Shaun\_Thobe](https://forum.inductiveautomation.com/u/Shaun_Thobe)\
**Post date:** [September 6, 2024, 7:38pm UTC](https://forum.inductiveautomation.com/t/address-description-in-perspective/95647/3 "2024-09-06T19:38:30Z")

</div>

Ok. That is basically what I am seeing. The description field in the address definition is just super easy to fill out as I can build it from a CSV. With needing to do the Documentation tag I will need to fill each one in individually which will not be an easy or fast task.

---

<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:** [September 6, 2024, 7:46pm UTC](https://forum.inductiveautomation.com/t/address-description-in-perspective/95647/4 "2024-09-06T19:46:36Z")

</div>

You could automate adding it to the tags using `system.tag.configure`; not quite as easy as this page though.

> **[system.tag.configure | Ignition User Manual](https://docs.inductiveautomation.com/docs/8.1/appendix/scripting-functions/system-tag/system-tag-configure)**
>
> Creates tags from a given list of Python dictionaries or from a JSON source string.