Hi Tom @TomD,
Yes, I’ve tried restarting Wappler multiple times (it actually crashes every time windows goes into sleep mode, and therefore have restarted it more times than I care to count), to no avail.
I never used the betas, I moved to 4 and then 4.0.1. This worked fine under the last 3.9.9 stable version and the undefined var can be corrected on code view (by replacing the word undefined by a value of choice), and the fact it happens on my two machines makes me think it’s a bug.
Thanks for the follow-up, it was an interesting thought.
I’ve had enough of these scenarios in the past that I just hand type or copy/paste those kinds of statements now… it feels so much more liberating and productive!
Bumping this as I have the same problem. I can add the Set Value action and enter a value via the Properties, but after saving the Properties shows as blank and the value remains undefined.
Restarting Wappler makes no difference.