# \[Bug-13032\]Using self.refreshBinding in a bound (binded?) props.x or custom.x Change Script

**URL:** <https://forum.inductiveautomation.com/t/bug-13032-using-self-refreshbinding-in-a-bound-binded-props-x-or-custom-x-change-script/23119>\
**Category:** Ignition Early Access\
**Created:** [March 7, 2019, 2:31pm UTC](https://forum.inductiveautomation.com/t/bug-13032-using-self-refreshbinding-in-a-bound-binded-props-x-or-custom-x-change-script/23119 "2019-03-07T14:31:49Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![joe.friedrich](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/joe.friedrich/32/7505_2.png) [@joe.friedrich](https://forum.inductiveautomation.com/u/joe.friedrich)\
**Post date:** [March 7, 2019, 2:31pm UTC](https://forum.inductiveautomation.com/t/bug-13032-using-self-refreshbinding-in-a-bound-binded-props-x-or-custom-x-change-script/23119/1 "2019-03-07T14:31:49Z")

</div>

I bound a custom value to a tag.  
Then, I wanted a completely different binding (in props) to run when this value changed.  
However, the JSON broke after saving the Change Script.

Here is the offending JSON:

> ,  
> "onChange": {  
> "script": "\tprint "Joe\u0027s change script! Edit JSON HERE!!"\n\tself.refreshBinding(\u0027props.views\u0027)",  
> "enabled": null  
> }

Tried setting :null to :true, but it didn't fix it.  
Tried using a different component (label.props.text) and using getSibling to access the 'props.view' that needed changed.  
Seemed to work fine when it was just a print statement, but I did not test this thoroughly.

Version: **8.0.0-beta0 (b2019030402)**  
(Can't upgrade until Friday. Sorry if this has been fixed in the last few days.)

---

<div class="post-metadata">

**Author:** ![cmallonee](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/cmallonee/32/6416_2.png) [@cmallonee](https://forum.inductiveautomation.com/u/cmallonee)\
**Post date:** [March 7, 2019, 4:01pm UTC](https://forum.inductiveautomation.com/t/bug-13032-using-self-refreshbinding-in-a-bound-binded-props-x-or-custom-x-change-script/23119/2 "2019-03-07T16:01:04Z")

</div>

Is that the entirety of the .json file? If not, could you please post or send the full file?

---

<div class="post-metadata">

**Author:** ![cmallonee](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/cmallonee/32/6416_2.png) [@cmallonee](https://forum.inductiveautomation.com/u/cmallonee)\
**Post date:** [March 7, 2019, 4:35pm UTC](https://forum.inductiveautomation.com/t/bug-13032-using-self-refreshbinding-in-a-bound-binded-props-x-or-custom-x-change-script/23119/3 "2019-03-07T16:35:45Z")

</div>

We had a team member replicate this, so we’re opening an internal ticket. Early indication is that this is a result of the refreshBinding call within a change script, so until we can investigate and deploy a fix, please avoid refreshBinding calls in Change Scripts.

---

<div class="post-metadata">

**Author:** ![awalker](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/awalker/32/6874_2.png) [@awalker](https://forum.inductiveautomation.com/u/awalker)\
**Post date:** [March 21, 2019, 4:13pm UTC](https://forum.inductiveautomation.com/t/bug-13032-using-self-refreshbinding-in-a-bound-binded-props-x-or-custom-x-change-script/23119/4 "2019-03-21T16:13:09Z")

</div>

This issue was fixed in the build that was uploaded today (3/20).  
Please let us know if you continue to see this behavior after upgrading.