# Tag History Indirect Binding

**URL:** <https://forum.inductiveautomation.com/t/tag-history-indirect-binding/96810>\
**Category:** Ignition\
**Tags:** vision\
**Created:** [October 4, 2024, 7:38am UTC](https://forum.inductiveautomation.com/t/tag-history-indirect-binding/96810 "2024-10-04T07:38:33Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![PFollansbee](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pfollansbee/32/46440_2.png) [@PFollansbee](https://forum.inductiveautomation.com/u/PFollansbee)\
**Post date:** [October 4, 2024, 7:38am UTC](https://forum.inductiveautomation.com/t/tag-history-indirect-binding/96810/1 "2024-10-04T07:38:33Z")

</div>

Not really needing help, but looking for validation on something.  
When binding tag history to a dataset, I dragged some tags over from the historical tags. As such, the tag paths were structured as:

[DB\_Connection/GatewayName:Tag\_Provider]Tag\_Folder\_Path/Tag

I needed to set this up for indirection. Since most of my indirects use a Tag\_Folder\_Path variable of the form [Tag\_Provider]Tag\_Folder\_Path, I just plugged this as a placeholder with intent to reformat to the full path later. However, this resulted in valid data. {1}/Tag fully worked as a historical tag binding using my tag path as defined.

Is is fair to assume that if I direct to a realtime tag, it will automatically pull the appropriate provider?  
Will this tag reference be happy in the long term?  
Forgive my paranoia.

Thanks all!

---

<div class="post-metadata">

**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 4, 2024, 12:31pm UTC](https://forum.inductiveautomation.com/t/tag-history-indirect-binding/96810/2 "2024-10-04T12:31:54Z")

</div>

> [@PFollansbee](#):
>
> will automatically pull the appropriate provider?

Yes, for local tag providers. There are optional overrides in remote tag providers that might affect this.

---

<div class="post-metadata">

**Author:** ![PFollansbee](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pfollansbee/32/46440_2.png) [@PFollansbee](https://forum.inductiveautomation.com/u/PFollansbee)\
**Post date:** [October 5, 2024, 2:27pm UTC](https://forum.inductiveautomation.com/t/tag-history-indirect-binding/96810/3 "2024-10-05T14:27:37Z")

</div>

Hopefully not too much to ask, but how do you know this? Where can i look to track this type of thing down? I would like to understand this at a deeper level to be able to answer questions like this for myself.

Thanks!

---

<div class="post-metadata">

**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 5, 2024, 2:54pm UTC](https://forum.inductiveautomation.com/t/tag-history-indirect-binding/96810/4 "2024-10-05T14:54:40Z")

</div>

> [@PFollansbee](#):
>
> how do you know this?

Experience. History paths are poorly documented.

Some related topics:

> [@Is the extended tag path format for history queries documented?](https://forum.inductiveautomation.com/t/is-the-extended-tag-path-format-for-history-queries-documented/96730):
>
> I was doing some hackish things with a history DB, and landed in a situation where I could no longer see the history for one specific tag using system.tag.queryTagHistory. Just to make sure I wasn't fumbling a parameter, I tried a history binding in Perspective for the same tag and it worked. Then I noticed that the designer UI had built the tag path in a form I've never seen documented. I tried that path with queryTagHistory and it got data. I was using a more simple: my\_hist = system.tag.qu…

> [@Historian Tag Path Syntax Format](https://forum.inductiveautomation.com/t/historian-tag-path-syntax-format/94617):
>
> I am laying out some foundational work. I came across two valid syntax of Historian Tag Path: short version: DB\_GW\_A01/gw\_maker:default]wm01 long version: histprov:DB\_GW\_A01:/drv:gw\_maker:default:/tag:wm01 From your experience. Which one is more acceptable?

> [@Remote Tag Provider History Queries](https://forum.inductiveautomation.com/t/remote-tag-provider-history-queries/93632):
>
> I'm working on a couple tasks related to historians and history queries, and have encountered some behaviors of remote tag providers (RTPs) that have me stymied: There's no public way to retrieve the gateway name that a RTP is pointing at, nor any public way to retrieve the far end's real tag provider name. (Reflection has exposed com.inductiveautomation.ignition.gateway.tags.distributed.client.RemoteTagProvider and com.inductiveautomation.metro.api.ServerId to me, and a number of private fie…
