# 7.9.4 issue : Alarm displayPath with UDT String parameter **URL:** \ **Category:** Ignition\ **Tags:** ignition79\ **Created:** [August 24, 2017, 10:17am UTC](https://forum.inductiveautomation.com/t/7-9-4-issue-alarm-displaypath-with-udt-string-parameter/15154 "2017-08-24T10:17:01Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![mazeyrat](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/mazeyrat/32/10955_2.png) [@mazeyrat](https://forum.inductiveautomation.com/u/mazeyrat)\ **Post date:** [August 24, 2017, 10:17am UTC](https://forum.inductiveautomation.com/t/7-9-4-issue-alarm-displaypath-with-udt-string-parameter/15154/1 "2017-08-24T10:17:01Z")
Since we’ve upgraded our application from 7.9.3 to 7.9.4, alarm display path displayed in alarm status are not OK. We use alam display path calculated with expression: ```auto concat("{codeGTC}"," | ","{codeGMAO}"," | ","{designationInstanceEqt}") ``` codeGTC and codeGMAO and designationInstanceEqt are UDT String parameter Upgrade at 2017/08/24. Old alarm in 7.9.3 are OK, new one in 7.9.4 are NOK ![](https://us1.discourse-cdn.com/inductiveautomation/original/2X/2/264492230a137b98f99528ac2ae1c46748a00c4e.png) Perhaps it is related to : Ignition 7.9.4 Changelog mention : ```auto Fixed - UDT parameter references in alarms are incorrectly replaced in memory when instances are created, potentially leading to incorrect instance creation (issue introduced in 7.9.4 beta) ``` ---
**Author:** ![James.Lorenz](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/james.lorenz/32/3290_2.png) [@James.Lorenz](https://forum.inductiveautomation.com/u/James.Lorenz)\ **Post date:** [August 24, 2017, 5:09pm UTC](https://forum.inductiveautomation.com/t/7-9-4-issue-alarm-displaypath-with-udt-string-parameter/15154/2 "2017-08-24T17:09:25Z")
Are those variables being accessed via Associated Data properties, or are they direct references to the UDT parameters? Would it be possible for you to send us a tag export of the UDT in question? ---
**Author:** ![Colby.Clegg](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/colby.clegg/32/3282_2.png) [@Colby.Clegg](https://forum.inductiveautomation.com/u/Colby.Clegg)\ **Post date:** [August 24, 2017, 6:23pm UTC](https://forum.inductiveautomation.com/t/7-9-4-issue-alarm-displaypath-with-udt-string-parameter/15154/3 "2017-08-24T18:23:47Z")
We’re looking into it. Looks like something is somehow changing parameter names to include “{ }” around them on the UDT definitions, but it’s not very reproducible. I’m sure we’ll track it down shortly… ---
**Author:** ![mazeyrat](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/mazeyrat/32/10955_2.png) [@mazeyrat](https://forum.inductiveautomation.com/u/mazeyrat)\ **Post date:** [August 24, 2017, 8:17pm UTC](https://forum.inductiveautomation.com/t/7-9-4-issue-alarm-displaypath-with-udt-string-parameter/15154/4 "2017-08-24T20:17:38Z")
Yes sure. I will post tomorrow UDT and tags xml export. @James.Lorenz, @Colby.Clegg ---
**Author:** ![mazeyrat](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/mazeyrat/32/10955_2.png) [@mazeyrat](https://forum.inductiveautomation.com/u/mazeyrat)\ **Post date:** [August 25, 2017, 6:16am UTC](https://forum.inductiveautomation.com/t/7-9-4-issue-alarm-displaypath-with-udt-string-parameter/15154/5 "2017-08-25T06:16:24Z")
Example of udt and instance to try to reproduce this issue [tags.xml](https://us1.discourse-cdn.com/inductiveautomation/original/2X/d/da19f46b23fdc2d30a42db9b3a7a3a8277a02f94.xml) (1.2 KB) [udt\_.xml](https://us1.discourse-cdn.com/inductiveautomation/original/2X/3/3bc73d5487c79cfe1c0c9d2387347c4dce60eb3d.xml) (24.6 KB) ---
**Author:** ![Plantformance](https://avatars.discourse-cdn.com/v4/letter/p/b77776/32.png) [@Plantformance](https://forum.inductiveautomation.com/u/Plantformance)\ **Post date:** [August 29, 2017, 6:14am UTC](https://forum.inductiveautomation.com/t/7-9-4-issue-alarm-displaypath-with-udt-string-parameter/15154/6 "2017-08-29T06:14:04Z")
Hey, I found yesterday also some issues with parameters in UDT. To reproduce :: - Create a UDT - Create a parameter long - Create a first param string1 with value - Create a second param string2 with value - Create a tag expression in UDT = to param long - Create a tag expression in UDT = to param string1 - Create a tag expression in UDT = to param string2 3rd tag expression (and also 2nd some time) will fail to calculate. ---
**Author:** ![James.Lorenz](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/james.lorenz/32/3290_2.png) [@James.Lorenz](https://forum.inductiveautomation.com/u/James.Lorenz)\ **Post date:** [August 29, 2017, 7:20pm UTC](https://forum.inductiveautomation.com/t/7-9-4-issue-alarm-displaypath-with-udt-string-parameter/15154/7 "2017-08-29T19:20:14Z")
Which version of Ignition were you using? Also, for the string parameter references in the expression, are you using quotes? i.e. “{param}” ---
**Author:** ![Plantformance](https://avatars.discourse-cdn.com/v4/letter/p/b77776/32.png) [@Plantformance](https://forum.inductiveautomation.com/u/Plantformance)\ **Post date:** [August 30, 2017, 5:57am UTC](https://forum.inductiveautomation.com/t/7-9-4-issue-alarm-displaypath-with-udt-string-parameter/15154/8 "2017-08-30T05:57:00Z")
7.9.3 (b2017060210) And I tried everything 🙂 {mystring} ‘mystring’ “mystring” there is a tricky bug there first one is working in some cases, but never the second ---
**Author:** ![Kevin.Collins](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.collins/32/13497_2.png) [@Kevin.Collins](https://forum.inductiveautomation.com/u/Kevin.Collins)\ **Post date:** [August 30, 2017, 1:16pm UTC](https://forum.inductiveautomation.com/t/7-9-4-issue-alarm-displaypath-with-udt-string-parameter/15154/9 "2017-08-30T13:16:30Z")
One thing to be careful of when editing UDT’s in the Designer is _NULL_ values… I think some of this issue might have been addressed in 7.9.4, but I’d still look out for it. For example, if you create a new data type, and add a tag to it and change [from Integer] to Boolean and save, you’ll have instances of that type (along with the type itself) have _NULL_ values for that tag. This is especially tricky for Boolean data types since they don’t show _NULL_ in the designer, only a check box. You have to “wiggle” the value (change to true, apply, change back to false, apply, for example) to ensure that instances start with a correct value. This might be something to look at when you’re having things fail to resolve (which can happen due to null-coalescing) properly. Here is an image showing the data type export and what to look out for: ![](https://us1.discourse-cdn.com/inductiveautomation/original/2X/2/2d2d9835b8ffaa3565f10a97a5c0750a26b1ebc6.png) Again, this might not be your issue, but I’ve struggled in debug on a few things until I discovered this behavior. ---
**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\ **Post date:** [August 30, 2017, 8:55pm UTC](https://forum.inductiveautomation.com/t/7-9-4-issue-alarm-displaypath-with-udt-string-parameter/15154/10 "2017-08-30T20:55:27Z")
An updated version 7.9.4 is now out, which solves the issue raised by Lionel in the original post.