Ability to search for PI Points used by PI AF attributes

One of the core items missing from this is not only finding attributes that directly use a PI Point, but also finding any non-PI Point DRs that reference that same PI Point. In systems with 5-8 million+ attributes, building our own recursion process to find these references becomes a pain. The solution provided needs to identify every reference.

This request occurs multiple times in this enhancement request list. It has been requested in multiple tools. The total votes across each request is several thousand. Please address this.

I would kill for this feature!
As an admin and user support of 10 sites, I spend a lot of effort any time I have to look for this reference. In my case, I normally starts from a tag and I need to get the element name and database. Thx, M.

I agree -we're struggling to maintain AF without this feature

I agree being up to search for PI Points, Elements etc. in AF would save a lot of time

Not only search PI Points but the ability to search for a value of a PI AF attributes. Example if an attribute is an asset type such as a pump, a fan, an agitator, etc. It would be possible to find all the elements that would have an attribute value of "fan".

I want to search AF element or its child attribute based on PI point. If I know PI point I can search its linked element and attributes in AF. In pallette option "search by tag" this feature should be provided.

This would be very helpful. Currently, I'm doing a Tag Name child attribute so it can be found using the Attribute Search's filter. However, this is very cumbersome.

In the meantime, I would suggest making a query table in Excel that uses PI OLEDB Enterprise to get the same information. Then you only need to refresh the table to update it rather than import the information all over again.

In the meantime, I would suggest making a query table in Excel that uses PI OLEDB Enterprise to get the same information. Then you only need to refresh the table to update it rather than import the information all over again.

In the meantime, I would suggest making a query table in Excel that uses PI OLEDB Enterprise to get the same information. Then you only need to refresh the table to update it rather than import the information all over again.

Now I used PI Builder (in Excel) to download the AF structure and search where tags are used. I would like to suggest an update / addin for System Explore that would allow you find tags and where they are used in the AF structure

Customer would like the ability to search in PI System Explorer for a tag, and find all references (attributes linked to that tag) in the database.

Here is a similar use-case for those who are trying increase their AF adoption: Create a way to search for PI Points that are NOT represented anywhere in AF. Here is an example: https://pisquare.osisoft.com/thread/37080

Native way to search in Pi System Explorer if a PI Point is used and where it is used would be very useful.

This is a very needed feature to find all the assets that are using a particular tag.

Searching PI points used in PI AF elements/attributes is very needed feature.

I encountered a similar situation, except that I was trying to see which tags I still had to add to PI AF (I started with a bunch of tags and a completely empty PI AF). My solution was to use PI OLEDB Provider in Excel to get a list of all tags on the PI Data Archive. I used PI OLEDB Enterprise in Excel to get all attributes in PI AF and their associated tag, if any. With these 2 tables in Excel, you can use lookup functions to check if each value in one table is in the other.

This is sorely missed. Some of the databases are huge and it can take a long time to figure out where a tag resides in the structure. Also, in my experience when we have new employees it is one of the first features they request when they are learning AF.

I feel the pain! For those interested (and those not afraid to break the rule of not querying PIFD directly!) I came up with a SQL query you can run against PIFD. You copy your PI tag name into line 3 and it searches the SQL database for everywhere it's referenced. So far it's proven reliable. The way it's written it only searches one tag a time - I'm sure it's possible to search multiple. -- Paste your PI Point name in the 'SET' line. It has to be exact. DECLARE @PIPoint VARCHAR(MAX) SET @PIPoint = 'RAWHIDPT.Cryo Unit.NGL.C2Rec (Simulated)' -- Do not modify anything below this SELECT ep.path As 'Element Path', ep.name As Element, ta.path AS 'Attribute Path', ta.name As Attribute, adr.configstring, 'Yes' As Template, CASE WHEN ta.fkparentattributeid IS NOT NULL THEN 'Yes' ELSE 'No' END As 'Is Child Attribute' FROM AFElementAttributeDR adr INNER JOIN AFElementTemplateAttribute ta on ta.rid = adr.fkattributetemplateid INNER JOIN AFElementVersion ev on ev.rid = adr.fkelementversionid INNER Join afelementpathA0 ep on ep.elementversionid = ev.id WHERE adr.fkattributetemplateid IS NOT NULL AND ep.primarypath = 1 AND adr.configstring like '%\' + @PIPoint + '?%' UNION SELECT ep.path As 'Element Path', ep.name As Element, ea.path AS 'Attribute Path', ea.name As Attribute, adr.configstring, 'No' As Template, CASE WHEN ea.fkparentattributeid IS NOT NULL THEN 'Yes' ELSE 'No' END As 'Is Child Attribute' FROM AFElementAttributeDR adr INNER JOIN AFElementAttribute ea on ea.attributeid = adr.fkattributeid INNER JOIN AFElementVersion ev on ev.rid = adr.fkelementversionid INNER Join afelementpathA0 ep on ep.elementversionid = ev.id WHERE adr.fkattributetemplateid IS NULL AND ep.primarypath = 1 AND adr.configstring like '%\' + @PIPoint + '?%'