Upgraded from 5.5.2 to 5.5.3 and noticed a fix to using New-UDAutocompleteOption but now without is broken. Anyone else able to confirm before I submit an issue?
My existing code worked after the upgrade but later is no longer working, which I find odd. I confirmed the same behavior in my dev environment. It worked right after the upgrade but then today it’s not working. I upgraded prod last night and this morning autocomplete worked for me. A user reported it not working and I confirmed it’s no longer working.
New-UDApp -Content {
#Works in v5.5.3 but not in 5.5.2
New-UDAutocomplete -Options @(
New-UDAutocompleteOption -Name 'Adam D' -Value '1'
New-UDAutocompleteOption -Name 'Sarah F' -Value '2'
New-UDAutocompleteOption -Name 'Tom S' -Value '3'
)
#Works in v5.5.2 but not in 5.5.3
New-UDAutocomplete -Options @('Test', 'Test2', 'Test3', 'Test4')
}
I’m sorry but thats just getting a bad product. It’s just getting bad and bader
Some Commands getting bug-fixed, and then reinvented with bugs (AutocompleteOptions)
Other commands getting a -dynamic Parameter (New-UDCardExpand) but fuck’up the way it worked without dynamic
By installing a new update, it removes always some dll’s which are needed to start up the whole thing - but crashing everything.
Never went in those Problems before V5, but only see bugfixes in all V5 + versions. I’ve put countless hours in my Dashboards, and it’s just demotivating, seeing everything crushed by single update’s
I’ve had similar thoughts. Back in v4, PSU was missing some features but was fairly stable. Now, each update breaks more than it fixes—often the same things that were previously fixed, or things that shouldn’t break at all because they haven’t been changed recently. With every update, I hope it will finally be ready, but after a while I start seeing a lot of issues again, and the cycle repeats every time.