# Asociated data any\_properties not working properly **URL:** \ **Category:** Ignition\ **Created:** [August 10, 2023, 11:26am UTC](https://forum.inductiveautomation.com/t/asociated-data-any-properties-not-working-properly/77687 "2023-08-10T11:26:39Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![Brian\_Cockrell](https://avatars.discourse-cdn.com/v4/letter/b/6f9a4e/32.png) [@Brian\_Cockrell](https://forum.inductiveautomation.com/u/Brian_Cockrell)\ **Post date:** [August 10, 2023, 11:26am UTC](https://forum.inductiveautomation.com/t/asociated-data-any-properties-not-working-properly/77687/1 "2023-08-10T11:26:39Z")
I am using associated data called group to create an active alarm tag to show if any tags in a specific group of tags has alarm and if they are all acknowledged or not. I can get the script to work but it is only looking at the numerical value for the associated data called group. For example I have tags with a group of 40A and tags with a group of 40B If i use that in the example scripting for associated data and look for 40A it will show a tag for 40B which has an alarm active. I can search for 40\_A and get the same. Is there a problem with texts as the group versus just numbers. ![20230810_062340](https://us1.discourse-cdn.com/inductiveautomation/original/3X/a/2/a2c01d908d5dfdcdad6125061169d18637e39c64.jpeg) ![20230810_062322](https://us1.discourse-cdn.com/inductiveautomation/original/3X/a/7/a75098751a5340cfe99d78e4fe853caf8e0ab0a5.jpeg) As you can see in the pictures i am getting the same return tag that has a group of 40B when searching for any\_properties Group = 40A or 40B. Need to figure this out please or see if it is a bug Using version 8.1.23 ---
**Author:** ![lrose](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/lrose/32/62724_2.png) [@lrose](https://forum.inductiveautomation.com/u/lrose)\ **Post date:** [August 10, 2023, 11:49am UTC](https://forum.inductiveautomation.com/t/asociated-data-any-properties-not-working-properly/77687/2 "2023-08-10T11:49:03Z")
What happens if you put an ‘\_’ at the front of the actual group names? ---
**Author:** ![Brian\_Cockrell](https://avatars.discourse-cdn.com/v4/letter/b/6f9a4e/32.png) [@Brian\_Cockrell](https://forum.inductiveautomation.com/u/Brian_Cockrell)\ **Post date:** [August 10, 2023, 11:55am UTC](https://forum.inductiveautomation.com/t/asociated-data-any-properties-not-working-properly/77687/3 "2023-08-10T11:55:36Z")
That seems to fix the issue and will work but is not ideal. ---
**Author:** ![lrose](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/lrose/32/62724_2.png) [@lrose](https://forum.inductiveautomation.com/u/lrose)\ **Post date:** [August 10, 2023, 12:03pm UTC](https://forum.inductiveautomation.com/t/asociated-data-any-properties-not-working-properly/77687/4 "2023-08-10T12:03:06Z")
I believe that this has to do with the fact that identifiers in Java and Python (and many other languages) shouldn’t/can’t start with a number. ---
**Author:** ![Brian\_Cockrell](https://avatars.discourse-cdn.com/v4/letter/b/6f9a4e/32.png) [@Brian\_Cockrell](https://forum.inductiveautomation.com/u/Brian_Cockrell)\ **Post date:** [August 10, 2023, 12:04pm UTC](https://forum.inductiveautomation.com/t/asociated-data-any-properties-not-working-properly/77687/5 "2023-08-10T12:04:05Z")
Okay. Thank you. I guess I will have to live with it. ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [August 10, 2023, 12:04pm UTC](https://forum.inductiveautomation.com/t/asociated-data-any-properties-not-working-properly/77687/6 "2023-08-10T12:04:18Z")
Hmmm. Sounds like a common problem, where people name things in their architecture that will be used like identifiers, but fail to follow common rules for identifiers (start with letter or underscore, include only letters, underscores, and digits). It may "technically" be a bug, but it isn't a surprise.