# How can I browse historical providers using the Tag Browser Tree component?

**URL:** <https://forum.inductiveautomation.com/t/how-can-i-browse-historical-providers-using-the-tag-browser-tree-component/110155>\
**Category:** Ignition\
**Tags:** perspective\
**Created:** [August 25, 2025, 6:00pm UTC](https://forum.inductiveautomation.com/t/how-can-i-browse-historical-providers-using-the-tag-browser-tree-component/110155 "2025-08-25T18:00:37Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Tucker\_Gustavesen](https://avatars.discourse-cdn.com/v4/letter/t/43a26b/32.png) [@Tucker\_Gustavesen](https://forum.inductiveautomation.com/u/Tucker_Gustavesen)\
**Post date:** [August 25, 2025, 6:00pm UTC](https://forum.inductiveautomation.com/t/how-can-i-browse-historical-providers-using-the-tag-browser-tree-component/110155/1 "2025-08-25T18:00:37Z")

</div>

So I followed the responses to this post in order to get 70% of what I want.: [[POSSIBLE] How to filter history-only tags in the Tag Browse Tree - Ignition - Inductive Automation Forum](https://forum.inductiveautomation.com/t/possible-how-to-filter-history-only-tags-in-the-tag-browse-tree/61955)

The above helped me get a tag browser tree component set up to show only nodes beneath the root path that either:

1. have history enabled
2. have any children

However there are issues I still need to fix with this and I’m not sure how:

1. Users need to be able to browse across all providers, and currently my browser doesn’t show anything if I try to just leave a wildcard in the root path field; I can only get results when I specify a provider
2. This still includes parent nodes that don’t contain any historical tags (because they DO contain children)

Basically, I want to be able to set up a tag browser tree like the one that’s built into the power chart. That one by default shows all historical providers, so it only shows nodes that contain children with history.

I feel like I’m missing something obvious and that it really shouldn’t be so complicated to make this component do what another component already makes it do.