edit variables uses previous value

A fix for this issue has been implemented in version 2026.3.5.0
Implemented

edit variables uses previous value

avatar

add 3 variables

put values in all 3

try to edit another one, it will not pull the value that is in the database/variables.ps1

it pulls the value from the last edit of a different variable

All Comments (2)

avatar

Hi Matthew,

Thank you for the clear steps. I reproduced this on PowerShell Universal 2026.3.3. Once you open a variable's properties (by clicking its name, or through ... > Edit Properties), every other variable you open afterwards shows the value that was last in that Value box (the first variable's value, or the last value typed there) instead of its own, until the page is reloaded. The name and the other fields are the right ones; only the value is wrong.

Please be careful with Save in that state: it writes whatever the Value box shows. In my test, opening a second variable and clicking Save without changing anything overwrote it with the first variable's value, in variables.ps1 as well.

Until this is fixed:

1. Reload the page (F5) before you open each variable. In my test, the first variable opened after a reload showed its own value.

2. For text (String) variables stored in the database, use the pencil button in the row (Set Variable Value) instead; it opens a dialog with only a Value box. It showed each variable's own value in my test.

3. If a variable was saved from that dialog recently, check its value in the Value column of the Variables page.

These steps are for 2026.3.x. If you are on an earlier version, tell me which one and I will check it there. I will report this to our development team.

Best regards,

Michel

Michel Audi

avatar

Hello,

Thank you for your patience while our team looked into the issue you reported.

I'm happy to let you know that the latest version of PowerShell Universal (2026.3.5) includes a fix for this problem. You can download it from our website here:
https://devolutions.net/download-center/#psu

Once you have installed the update, could you please test it in your environment and confirm that everything now works as expected? If the issue persists or if you notice anything unusual related to the same original problem, just reply to this message with a few details, and we will be glad to look into it further.

Thank you for your collaboration.

Best regards,

Érica Poirier

A fix for this issue has been implemented in version 2026.3.5.0