# Help with Dynamic History Tags

**URL:** <https://forum.inductiveautomation.com/t/help-with-dynamic-history-tags/102600>\
**Category:** Ignition\
**Tags:** ignition81, perspective\
**Created:** [February 19, 2025, 10:30pm UTC](https://forum.inductiveautomation.com/t/help-with-dynamic-history-tags/102600 "2025-02-19T22:30:20Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![daniel4](https://avatars.discourse-cdn.com/v4/letter/d/cdc98d/32.png) [@daniel4](https://forum.inductiveautomation.com/u/daniel4)\
**Post date:** [February 19, 2025, 10:30pm UTC](https://forum.inductiveautomation.com/t/help-with-dynamic-history-tags/102600/1 "2025-02-19T22:30:21Z")

</div>

You can see me trying to build a tag path with parameters there in the expression field since there is no option to do an indirect tag binding in the tag history tab. I have tried everything I can think of regarding syntax for this and read what I can find in the docs about history tags but nothing seams to apply to this. I just want to show different data in my chart depending what you clicked on to get the popup it's displayed in. I know the parameters work fine as I have them bound to labels for example in the popup. But I can't seam to get the history tag path to work. I feel like I'm missing something here. Any help would be great.

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/2/4/245c2a937163a8e8f86e8b61818d039edcd75e94.png)

---

<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:** [February 19, 2025, 10:42pm UTC](https://forum.inductiveautomation.com/t/help-with-dynamic-history-tags/102600/2 "2025-02-19T22:42:27Z")

</div>

There is a very specific format requirement for "Expression", which can only be satisfied with a separate custom property (out of the box). That custom property must be an **array** of **objects** with specific keys. The expression in the binding would be just a curly-brace property reference.

If you have my Integration Toolkit module, you can build the proper structure right there in the binding. Like so, fwiw:

```python
asList(
	asMap(
		'path', concat(
			"[Ignition_bdcisb31_ignition_01_edge]BLD/",
			{view.params.BuildingName},
			"/Power/",
			{view.params.PowermeterName},
			"/ACTIVE_POWER"
		),
		'alias', "POWER",
		'aggregate', 'Average'
	)
)

```

---

<div class="post-metadata">

**Author:** ![kvane](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kvane/32/22228_2.png) [@kvane](https://forum.inductiveautomation.com/u/kvane)\
**Post date:** [February 19, 2025, 10:53pm UTC](https://forum.inductiveautomation.com/t/help-with-dynamic-history-tags/102600/3 "2025-02-19T22:53:45Z")

</div>

This is the User Manual page for the Tag History Binding - Expression requirements, it is not clear in the designer how strict it is, I'd recommend watching the IU video to see a quick example:

> **[Tag History Bindings in Perspective | Ignition User Manual](https://www.docs.inductiveautomation.com/docs/8.1/ignition-modules/perspective/working-with-perspective-components/bindings-in-perspective/tag-history-bindings-in-perspective#tag-history-binding---expression)**
>
> Tag History Binding

---

<div class="post-metadata">

**Author:** ![daniel4](https://avatars.discourse-cdn.com/v4/letter/d/cdc98d/32.png) [@daniel4](https://forum.inductiveautomation.com/u/daniel4)\
**Post date:** [February 24, 2025, 9:17am UTC](https://forum.inductiveautomation.com/t/help-with-dynamic-history-tags/102600/4 "2025-02-24T09:17:34Z")

</div>

Looking at the video got me on the right track. Thank you. I had already read through the doc but hadn't noticed the video link at the top. It works great, though its needlessly complicated when they have obviously solved this in a much more user friendly manner with the indirect tag system. I don't see any reason why it could not be the same for history tags. Maybe that will be a future update. Either way I'm not going to complain to much as it works flawlessly now. Again many thanks for the help.