Did $EventData in UDSelect change in 2026.3.0.0?
After updating to 2026.3.0.0 a screen didn't work for me anymore.
After debugging I found that the $EventData variable in the -onchange of the UDSelect now returns "string" instead of string.
So it includes double quotes in the variable itself.
So if I use my UDSelect to select for instance value abcdef then "abcdef" gets returned instead of abcdef in the $EventData
So char 34 in front and in the back.
Is this by design?
I fixed my screen by inserting a .Trim('"') later in the code where I needed that variable.
All Comments (2)
Hello @denistiri
Thank you for reporting this.
I reviewed the published changes for PowerShell Universal 2026.3.0.0, and I do not see a documented change indicating that the value returned by $EventData for New-UDSelect -OnChange should now include double quotes.
Since you observed this behavior immediately after upgrading, I would like to validate it as a possible behavioral change before confirming whether it is expected.
We will attempt to reproduce this internally using 2026.3.0.0 and compare the $EventData value returned by the same New-UDSelect configuration against the previous behavior.
Could you please confirm the exact PowerShell Universal version you upgraded from, where the same code was working without requiring .Trim('"')?
References:
https://forum.devolutions.net/topics/56197/devolutions-powershell-universal-version-2026300-september-15-2026
Best regards,
Ruben Tapia
Hi, I've come across the same issue (among lots of others, will be posting bug reports in a minute). The documentation hasn't changed but the output of $EventData seems to be raw JSON data instead of unserialized objects.