# Expression into Indirect Tag Binding **URL:** \ **Category:** Ignition\ **Created:** [January 25, 2021, 5:24pm UTC](https://forum.inductiveautomation.com/t/expression-into-indirect-tag-binding/42584 "2021-01-25T17:24:17Z")\ **Posts on this page:** 1\ **Showing post:** 7
**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:** [January 26, 2021, 9:22pm UTC](https://forum.inductiveautomation.com/t/expression-into-indirect-tag-binding/42584/7 "2021-01-26T21:22:38Z")
> [@jlandwerlen](#): > > There is nothing wrong with using tag(). Ah, but there is. It simply runs slower, because expressions built around it have to completely execute, even if only one little piece changes, and even if a given change wouldn't yield a change in the output. Totally aside from the (fixed?) bugs in its implementation in v8.0. > [@Nesting Not Allowed while using Properties in a Template to turn on a Light](http://forum.inductiveautomation.com/t/nesting-not-allowed-while-using-properties-in-a-template-to-turn-on-a-light/33609/16): > > Yes, there is. If the items that comprise your tagpath are updated, even if yielding the same result path, the entire expression containing the tag() function will have to execute. With indirect binding, this doesn’t happen. The strings themselves have to be reconstructed every time, even if not changing, slowing down the final expression execution. There are a few cases with computed gateway tags where the tag() expression is the only good way to do indirection, and the dynamic stuff above… Gateway expression tags are the _ **only** _ place the tag() expression function makes sense. --- _[View the full topic](https://forum.inductiveautomation.com/t/expression-into-indirect-tag-binding/42584)._