# Searching for a resolved tagpath **URL:** \ **Category:** General Discussion\ **Tags:** ignition81\ **Created:** [October 21, 2023, 3:02pm UTC](https://forum.inductiveautomation.com/t/searching-for-a-resolved-tagpath/80803 "2023-10-21T15:02:59Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![Narzan\_Daghouz](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/narzan_daghouz/32/53684_2.png) [@Narzan\_Daghouz](https://forum.inductiveautomation.com/u/Narzan_Daghouz)\ **Post date:** [October 21, 2023, 3:02pm UTC](https://forum.inductiveautomation.com/t/searching-for-a-resolved-tagpath/80803/1 "2023-10-21T15:02:59Z")
Hi all; I noticed when using the search function there is a minor issue when trying to search for the resolved dynamic OpcItemPath, essentially throwing us off when trying to troubleshoot and find whether certain PLC addresses were used or not. This essentially causes multiple tags of the same address to be added especially on larger projects we work on. Here is an example: - UDT Dynamic OPC Item Path: `ns=1;s=[RF5]N19:{ndx+1}` - Resolved path (OpcItemPath) shows `ns=1;s=[RF5]N19:21` on the tag browser - **Searching for** `N19:21` **does not show me whether this address is being used or not.** I also tried the following to see if it's related to how the UDT is setup: - Changing the binding to `ns=1;s=[RF5]N19:{ndx}` to see if it's related to the math operation but still didn't work. - Changing the datatype of `ndx` parameter from Integer to String, still no go Ignition Version: **8.1.31** this however happened even with older versions of Ignition ( **8.1.17** ). Thank you ---
**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:** [October 21, 2023, 3:17pm UTC](https://forum.inductiveautomation.com/t/searching-for-a-resolved-tagpath/80803/2 "2023-10-21T15:17:15Z")
The search function simply does not look at the results of bindings. Sorry. There were announcements at ICC of new tag cross referencing functionality coming in Ignition v8.3 You simply cannot search for this kind of information in the meantime. ---
**Author:** ![Narzan\_Daghouz](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/narzan_daghouz/32/53684_2.png) [@Narzan\_Daghouz](https://forum.inductiveautomation.com/u/Narzan_Daghouz)\ **Post date:** [October 21, 2023, 3:22pm UTC](https://forum.inductiveautomation.com/t/searching-for-a-resolved-tagpath/80803/3 "2023-10-21T15:22:01Z")
Thanks Phil; Yes I do remember that announcement, it got a huge round of applause! It was a pleasure meeting you in person and everyone else at ICC this year! 🕶 ---
**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:** [October 21, 2023, 3:59pm UTC](https://forum.inductiveautomation.com/t/searching-for-a-resolved-tagpath/80803/4 "2023-10-21T15:59:34Z")
Actually, I just realized you are searching for an OPC Item Path result. I think you are still going to be toast in v8.3. /: ---
**Author:** ![Narzan\_Daghouz](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/narzan_daghouz/32/53684_2.png) [@Narzan\_Daghouz](https://forum.inductiveautomation.com/u/Narzan_Daghouz)\ **Post date:** [October 21, 2023, 4:12pm UTC](https://forum.inductiveautomation.com/t/searching-for-a-resolved-tagpath/80803/5 "2023-10-21T16:12:08Z")
Is there a technical reason why this can't be possible?.. If not then I will submit a feature request. ---
**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:** [October 21, 2023, 4:19pm UTC](https://forum.inductiveautomation.com/t/searching-for-a-resolved-tagpath/80803/6 "2023-10-21T16:19:22Z")
Well, the designer's search function searches **configuration** , not **live** values. I imagine you could create your own search function by using `system.tag.readBlocking()` on all of your OPC Item Paths and examining those values. ---
**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:** [October 21, 2023, 5:14pm UTC](https://forum.inductiveautomation.com/t/searching-for-a-resolved-tagpath/80803/7 "2023-10-21T17:14:19Z")
> [@pturmel](#): > > tag cross referencing functionality coming in Ignition v8.3 Minor point: tag reference tracking is landing in 8.1, not just 8.3. ---
**Author:** ![nminchin](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/nminchin/32/6911_2.png) [@nminchin](https://forum.inductiveautomation.com/u/nminchin)\ **Post date:** [October 23, 2023, 3:01am UTC](https://forum.inductiveautomation.com/t/searching-for-a-resolved-tagpath/80803/8 "2023-10-23T03:01:20Z")
The tag report tool should be able to find these though ---
**Author:** ![MMaynard](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/mmaynard/32/3366_2.png) [@MMaynard](https://forum.inductiveautomation.com/u/MMaynard)\ **Post date:** [October 23, 2023, 12:02pm UTC](https://forum.inductiveautomation.com/t/searching-for-a-resolved-tagpath/80803/9 "2023-10-23T12:02:17Z")
8.1.25 tag report tool finds these just fine? Make sure you search on Property OPC Item Path and then use the like operator with wild cards around the search string. So your example search would be for Property 1, OPC Item Path, Like, `*N19:21*`