# Passed parameters not pulling current tag status popup when set bi-directional

**URL:** <https://forum.inductiveautomation.com/t/passed-parameters-not-pulling-current-tag-status-popup-when-set-bi-directional/110466>\
**Category:** Ignition\
**Tags:** perspective\
**Created:** [September 8, 2025, 9:12pm UTC](https://forum.inductiveautomation.com/t/passed-parameters-not-pulling-current-tag-status-popup-when-set-bi-directional/110466 "2025-09-08T21:12:21Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![GaryL](https://avatars.discourse-cdn.com/v4/letter/g/bbe5ce/32.png) [@GaryL](https://forum.inductiveautomation.com/u/GaryL)\
**Post date:** [September 8, 2025, 9:12pm UTC](https://forum.inductiveautomation.com/t/passed-parameters-not-pulling-current-tag-status-popup-when-set-bi-directional/110466/1 "2025-09-08T21:12:21Z")

</div>

I have a popup with a radio button im attempting to bi-directionally pull and push the current setting of the radio button for a clockwise and counter clockwise running of a motor writing to a single BOOL tag (1 = CW 0 = CCW). The radio buttons properly write to the tag and push the value however upon closing the popup the current value of the tag is not reflected by the radio button selection, the bi-directional binding seems to not be pulling the tag state upon opening the popup.

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/7/3/73646f631e445971012aad6861137d19b4c8a5ba.png)

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/1/0/10b1314a3839a7764070c8b7e55c6c4e6a542e07.jpeg)

Thanks for the help.

---

<div class="post-metadata">

**Author:** ![GaryL](https://avatars.discourse-cdn.com/v4/letter/g/bbe5ce/32.png) [@GaryL](https://forum.inductiveautomation.com/u/GaryL)\
**Post date:** [September 8, 2025, 9:42pm UTC](https://forum.inductiveautomation.com/t/passed-parameters-not-pulling-current-tag-status-popup-when-set-bi-directional/110466/2 "2025-09-08T21:42:20Z")

</div>

To elaborate on this, i have kind of a work around for this issue, if i bind the Index of the radio button with the tag value and an expression if statement it properly works, however every time that i re-open the popup it writes the value again which seems sloppy.

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/d/f/dfe566d5e1c52d58f544e2b299d094c3b5ebcb12.jpeg)

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/1/d/1d67cc44c5e3b1e559ad01a787eff41df87751be.jpeg)

But then this gives me this error:

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/3/3/331f9afe538ef572e02c3d2d8a383f58e32af27b.png)

---

<div class="post-metadata">

**Author:** ![Transistor](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/transistor/32/3380_2.png) [@Transistor](https://forum.inductiveautomation.com/u/Transistor)\
**Post date:** [September 8, 2025, 10:52pm UTC](https://forum.inductiveautomation.com/t/passed-parameters-not-pulling-current-tag-status-popup-when-set-bi-directional/110466/3 "2025-09-08T22:52:36Z")

</div>

Try this instead. (I haven't!)

- Remove the `index` binding.
- On `radios.0.selected` create an expression binding:  
`!{[edge]Ignition Tags/Pump1/PumpRun Direction}`
- On `radios.1.selected` create an expression binding:  
`{[edge]Ignition Tags/Pump1/PumpRun Direction}`

They shouldn't be bidirectional.

I think the 'Nested paths not allowed' means that you're setting the index property which is triggering a change in the `radios.x.selected` property which is updating the index which is ...

---

<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:** [September 9, 2025, 2:45am UTC](https://forum.inductiveautomation.com/t/passed-parameters-not-pulling-current-tag-status-popup-when-set-bi-directional/110466/4 "2025-09-09T02:45:52Z")

</div>

I'm pretty sure this is due to your radio buttons using 0/1 instead of false/true, but Im not at a laptop to test
