# Alarm Display Path and UDT parameters vs. Tag insertion

**URL:** <https://forum.inductiveautomation.com/t/alarm-display-path-and-udt-parameters-vs-tag-insertion/8789>\
**Category:** Ignition\
**Created:** [July 25, 2014, 4:16pm UTC](https://forum.inductiveautomation.com/t/alarm-display-path-and-udt-parameters-vs-tag-insertion/8789 "2014-07-25T16:16:57Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![matt.eaton](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/matt.eaton/32/72046_2.png) [@matt.eaton](https://forum.inductiveautomation.com/u/matt.eaton)\
**Post date:** [July 25, 2014, 4:16pm UTC](https://forum.inductiveautomation.com/t/alarm-display-path-and-udt-parameters-vs-tag-insertion/8789/1 "2014-07-25T16:16:57Z")

</div>

Here’s an anomaly I noticed.  
I have a UDT with a device (string) property and a metadata folder that has a description memory tag (string).  
If I insert {device} in the display path it comes in as a raw value:  
Wheeling A

If I insert {[.]metadata/description} into the display path it comes in as a string:  
“Wheeling A”

I can make a point of enclosing the {device} with quotations but it’s definitely unexpected behaviour, I would think they would both work the same way, whatever that way is.