Are you talking about this video? https://www.youtube.com/watch?v=olq0OgW3dsM

That is the basics, but he doesn't explain it very well, for instance in my site I tag every point and history with Metadata with the following Metadata tags:

Campus
Building
Utility
System
Room

than when you create the history groupings, the order in which you add the metadata will be the order in which the tree "unfolds", i.e. logically you would list Campus as the first, so when you clicked the history group name you would see all the campus names as folders, then you click a specific campus name the next folder presented would be a list of all the items with a metadata tag taken from the next tag in the history groupings list, say that was "Building", which would present every building name as a separate folder, etc on down the list.

Keep in mind all histories would need to have multiple tags. In the even a history only has 3 of the 5 tags I listed above it will show up in the 3rd subfolder.

I hope I explained it well enough, once you play with it a few minutes it will make a whole lot more sense.

In your specific case try the following:
make sure each history for every AHU and Each VAV has 2 metadata tags: First one maybe name it "System" and second one maybe name it "SystemName"

so for each history in AHU-1, you would set the metadata tag "System" to equal "AHU's" and "SystemName" to equal "AHU-1". Do the same for all of the AHU's and VAV's you are interested in, than create a history grouping where the first tag is "System" and the second tag is "SystemName". That should get you what you want.

 

Ya that video did not work for me. I've never used 'tags' and I accomplished it a few years ago but I don't remember how.

 

First step is to add the metadata using the metadata browser. This is shown in the video starting at minute 2.

2nd step would be to add the history grouping to the history service and configure it. That is around minute 1, not sure why they laid it out in that way.

I suppose step zero would be to ensure there is histories on the point of interest.

Keep in mind I mix up the terms "tags" and "metadata", which I really shouldn't do. the word Tag implies a haystack tag, Metadata is not the same. History groupings only work with Metadata (as far as I know). You must have each history point you are interested in with at minimum of 1 (but in your case 2) pieces of Metadata. Each metadata is a Key:Value pair. An example of your keys would be "System:AHU's" and "SystemName:AHU-1".

 

If you are doing this on a running jace, beware the metadata browser is going to be painfully slow. If i go this route I do it on a station running on my laptop. Or you can use the program service.
Here are some screenshots that might be helpful.

 

If you are doing this on a running jace, beware the metadata browser is going to be painfully slow. If i go this route I do it on a station running on my laptop. Or you can use the program service.
Here are some screenshots that might be helpful.

View attachment 847781 View attachment 847783 View attachment 847785

This is great thanks!

 

Metadata browser sucks on the jace and overall. I use the batch editor to add histories, metadata, and groups. I made a doc for some guys on the process. I will send it to you.

 

Could you please also send this to me?/ Thanks, ben

 

I have done History Grouping plenty of times - never used the Metadata browser. I add bajaString slots on the HistoryConfig of each history extension with Program Services. Floor, AreaServed, etc. Then enter those slot names into the history grouper. works great.

 

Exactly how I do it also. The doc I sent him describes this.

 

I can't seem to find it. Can you resend it?

 

All I want to do is have a folder by AHU and folders by VAV. I created the groupings but can't figure out how to get something on every extension. I manually added a slot named VAVs but that didn't work. It has to be step by step. I don't know how to use Program service or Metadata etc.
https://hvac-talk.com/vbb/attachment.php?attachmentid=853919&d=1689815004

 

The sorting works by the values in the slots. So having a vav slot is good, but you need a value in there.
I tend to put a slot for BuildingName, Floor, UnitName, etc.
Everyone has these slots on their history extensions. So items with
BuildingName=building 1
Are grouped in a folder named building 1
Floor=Floor2
Are subfoldered under building 1 in another folder called Floor2
UnitName will be the name of the unit holding the extensions. A little tedious to set these.
UnitName=VAV3
Another subfolder that is named VAV3 holds the few extensions in their.

 

Yeah, I used to hate doing groupings when I was nervous about using the program service and completely mucking things up. Legitimate hours doing trends on new construction, all whittled down to maybe 1 or 2 hours total. Learning BFormat code and how to navigate modules with the Bql Query took awhile.


InControl, you can try and close the history folder carrot, right click, then "Refresh Tree Node".

 

I added the room number but nothing changed. Looking for step-by-step for someone who knows nothing.

https://hvac-talk.com/vbb/attachment.php?attachmentid=854043&d=1689944553

 

You receive the doc I sent you? That is step by step with program services.

 

I just like RC unless I have gobs of histories per device. Then I will use program service to put the unit or room number on each of the 5 or 10 trends on that device.
It is not fun, but if I put my head down, it goes quick.

 

I dislike the semi-literate "AHU'S" and "VAV'S" when it should be "AHUs" or simply "AHU", etc. There's no possessive case.

 

Agreed. That's what I used. Sorry you couldn't get into the police academy.

 

Sorry. I tried to delete my stupid remark but am not given that opportunity here.

 

LOL Same here. Make your words sweet in case you have to eat them.

 

Hi Right, just wondering if you could send me this doc also. I am also having issues using the program service for this. I sent you an email yesterday. Thanks

 

I would love to get a copy of this document if possible too please!

 

I like that adding a StringWritable to the history config immediately organizes the history without the metadata browser, but how do you create subfolders? For example, I have a history config with a string called "building" and another called "system". How do I organize the histories so it looks like "Building History Group Name" > "Building String Value" > "System String Value"?

Also, is there a way to hide the "{ok} @def" from the folder name created by the StringWritable?

 

In the format of the text. Change it from %.% to %out.value% this will get rid of your @def your seeing.

 

Sorry for the late reply - I just updated my profile. Thanks again for your help.

 

Just went through the document. Thanks again for your help, RC. I got tripped up with adding the strings. For people reading too quick in the future, it's a new slot in the History Config of type "baja string", not a StringWritable point.

Also worth noting that each new field added to a history group is another nested folder, not another word that could be used to add a history to that group.

 

Glad to help.

 

I know I asked for this guide as well, but looked through my email and can't find it, I hope it didn't get caught in spam filters, could I ask once more for it please?

 

I would just expand a little on what Numba is saying. I do like to help with some things considered. One, the document I made was for internal co-workers, it has specific job information on it. Not huge but something to consider when deploying it to the masses. Also, this took me like 20 minutes to create I wouldn't say it's some high level Niagara thinking. Most with a little effort I feel could expand or improve it. I was using the Metadata browser for years, and sat down one day to see if I could improve my work flow. This is where the doc originated from. With tagging now prevalent this maybe consider old process. Works for me because I'm old LOL. The last thing is probably my biggest consideration for sending things out to others. If your a new guest with very little posts, and haven't made any attempt to contribute to our little niche world on here. And you can't seem to add an email to your profile I won't spend two seconds making an attempt to help. With Mr. Mayor it was easy to see even given his low post count. He's engaged, has tridium skills, and has offered help to others. This does gain mileage on here. So new guests, engage, be part of the group it will gain you knowledge and collaboration.

 

Calling for help on this, spent too many hours on this yesterday. I know perfectly well how to do this where the histories are in a JACE, but when you import the histories in a JACE on a supervisor, the histories do not have a "historyconfig" object on the supervisor so you can't use program service to do mass edits on the supervisor. They do have a "NiagaraHistoryImport" object (found under Niagara driver) but the metadata is not attached to those objects. I am stuck doing it in Metabrowser on the supervisor and if you try to edit more than a handful it is painfully slow. Anybody know the secret sauce where the Meta tags are stored on imported histories?

 

I may not be understanding what you are trying to do, but if you are needing to edit\add metadata for histories created in a jace just use the program service in the jace and then just archive the history imports in the supervisor and it should update the metadata for the history imports in the supervisor.

 

I could be wrong, but I don't think the Metadata is imported from the JACE to the supervisor. Perhaps I need to create a quick history and test that theory, would be easier in the JACE to do this!

 

BTW it sucks we still need to use "Metadata" for histories and can't use tags!

 

Ok, I have been proved wrong! Excellent! I will do what I need to do in the JACE!

 

Ya It's been a while but they did come into the server.