# Tag Property Nested Parameter Binding

**URL:** <https://forum.inductiveautomation.com/t/tag-property-nested-parameter-binding/112918>\
**Category:** Ignition\
**Tags:** ignition81\
**Created:** [December 19, 2025, 4:39pm UTC](https://forum.inductiveautomation.com/t/tag-property-nested-parameter-binding/112918 "2025-12-19T16:39:34Z")\
**Posts on this page:** 1\
**Showing post:** 12

<div class="post-metadata">

**Author:** ![nminchin](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/nminchin/32/6911_2.png) [@nminchin](https://forum.inductiveautomation.com/u/nminchin)\
**Post date:** [December 19, 2025, 11:14pm UTC](https://forum.inductiveautomation.com/t/tag-property-nested-parameter-binding/112918/12 "2025-12-19T23:14:45Z")

</div>

I’d forgotten about that one. I think it’s only an issue if you put names inside the braces e.g. `“{0}”.format(…)` compared to `"{}”.format(…)`

I got Claude to find relevant posts for an example:

> [@Python String Formatting in Tag Change Script](https://forum.inductiveautomation.com/t/python-string-formatting-in-tag-change-script/70855):
>
> It seems like pythonic string formatting is broken within tag-change event scripts. For example, writing value = currentValue.value ack\_value = "{0}\_ACK".format(str(value)) # unnecessary str() call, but used for comparison only does not work, but value = currentValue.value ack\_value = str(value) + "\_ACK" does. We get no errors on the gateway and cannot run any code above or below the str().format() call until it is removed. Is the Jython environment within the tag-change script a diff…

---

_[View the full topic](https://forum.inductiveautomation.com/t/tag-property-nested-parameter-binding/112918)._