Perspective Power Chart tag browser question

Ignition
1

is there any way to modify the tag browser of the chart?
I would like to show the description of the tags instead of the names.

Thank you

2 Likes
2

This is especially important for tag history coming from mqtt providers, as these can’t always be named nicely for an operator

1 Like
3

Please vote here:
https://ideas.inductiveautomation.com/ignition-features-and-ideas/p/history-tag-alias-field

1 Like
4

in vision I have been able to do it by creating my own tag browser.

5

Yep, I made my own trend viewer for Vision with descriptive names and tag filtering, very easy to find and select the tags you want.

2 Likes
6

yes, so in perspective for now nothing can be done? give up?

7

Hello,

Is there any plans to allow filtering, wildcards on this power chart tag browser control? It is quite cumbersome to click through layers and layers of folders and tags. As the number of tags increasing so does the scrolling. We are running perspective 8.1.14 BTW.

Thanks,

Frank

1 Like
8

Not exactly. The only solution I found is through the translation manager…
Yes, it WILL translate the tags names in the tag browser.

If you have too many tags to translate manually, but already have display names configured on your tags, use a script to generate the translations for you.

9

Hello,

I am not sure I follow your post. I do not need to translate anything with the tags in the browser I simply want a filter/search option with wildcards to show that tags I want and then I can click and add them to chart.

Thanks,

Frank

10

Yes, I was answering to @lachguerabdallah 's question, regarding how to change the display names of the tags. While this can’t be done directly, the internal name can be translated into something more user friendly through the translation manager.

11

Any updates? The translations currently only work in the tags browser, but it would be helpful to see the 'translation' in Legends and on the chart as well.

12

you can use scripting to create your own browser tag, you have to hide the browser tag button from power chart.

13

Hi, the browser is ok.. the problem is to rebuild the PowerChart! :sweat_smile:

14

What was the rough outline of how you built out a tag "picker" component?
Would you run a system.tag.browse to build up a list of tags with history enabled on them, and populate a list of tags, tagpaths, descriptions etc.. and show it in a table or something?
Then allow user to filter, select and add these to the trend?

15

I have opted for running a Named Query with a filter parameter against the DB.

SELECT tagPath
FROM sqlth_te
WHERE tagPath LIKE :filter AND retired is null

This allowed for my "browse" time to go from seconds to single digit ms (Roughly 6K historical tags).

Just my two cents.

If you care about the properties of particular tags (other than History Enabled), then perhaps system.tag.browseHistoricalTags() would be a better option? In my application I just want to know if its a historical tag.

2 Likes
16

Fair enough, my primary goal with this custom tag picker is to show the "Description" of the tag, which we store as a UDT parameter. So the browse tag function would enable us to do that.

But yes it would certainly be more efficient to just query the sqlth_te table!

Could potentially do a sneaky hybrid approach where you maintain a separate SQL table which runs the browse tag function daily or something and stores results to a SQL table which can be queried by the tag picker...

Not sure I particularly like that as it isn't very realtime. But something like this wouldn't need to be that quickly updated

1 Like
17

I think I queried from the sqlth_te table as well and would recommend against tag.browse. If you need descriptions from tags, then read those periodically from the tag values and update into a separate table that stores description against sqlth_te tagpaths and then join them up, or in that case, you might even just be able to use your new table. But either way, use a sql table rather than a tag.browse for speed as well as filterability. On second thoughts, perhaps I did it this way instead, it's been a while since I looked at it

Edit: I just read your post and see you came to that solution already haha.
Tag changes in the commissioned system will most likely be sparse, or occur during scheduled work, so having the sql table updated periodically shouldn't be an issue.

3 Likes
18

@richardNZ15 What property do you want to show? .Tooltip or .Documentation?
Can you indicate how you want your navigation tree to be displayed based on the tag structure?

19

Hi, doesn't matter too much. I can always bind the custom {Description} parameter to either of those properties.
I just want the ability to either replace the tag name with this description property, or show it side by side.
Simply hovering over the tag wouldn't work for users, as they'd need to see what exactly they're looking for in the tree.

For example, if tags look something like:

MZ50123

That doesn't necessarily mean much to most operators unless they know the plant inside out. So it would be hugely useful to see the description instead, which might be something like:

Drier 1 feedline auxiliary pump 2

eg:

image
image844×359 10.8 KB

The fact that there is no in-built Tag Browser tree component for historical tags like there was in Vision is already pretty dissapointing..

3 Likes
20

You can use the Tree component to compose your tree.

To compose the tree, I use the tag.browse function

results = system.tag.browse("[default]", {"tagType":"AtomicTag","valueSource":"opc", "recursive":True})

for result in results.getResults():
	    if "history" in result["attributes"]:
              your code...

Once you have your tree, you can add a button to add pens to the power chart component, adding values ​​to the axes and pens properties

image