New update broke some app variables

[Shawn Smalley]

I just updated to 6.3.20240724.0, and now my app will constantly keep reloading a couple of widgets. It eventually gave me an error and when i checked the log i noticed that some of the vv_invirtual() commands in my sql statements were returning blank instead of the value it should be, or even the default value built in to the command. Here is the error, along with the actual sql statement in NAB:
sql error.pngcall stack.png
Statement.png

This is happening with at least 3 different sql statements just on the front page of my app, and it was all working fine before

[sean.lanktree]

When your statement runs....what values do you have set for "wrkc" and "clknum"? Also, how are they set? Set App Variables, an expression, or by the back end via SetAppVar?

[sean.lanktree]

This issue was resolved over the phone. With the new build, a form helper change event is now fired if the value of a field is changed via an app variable linkage. In this case, the form helper program was changing the app variable that was linked to the field for every call thus causing an endless loop of calls. We will be considering a change in the form helper UI to designate which field(s) should be considered for the "change" call to the form helper.