Bug New-UDSelectGroup

Product: PowerShell Universal
Version: 2026.1.5

I’m not sure if I’ve found a bug, but when I create a New-UDSelectGroup with the -multiple parameter, the value in the row is not displayed, even though it is selected. This is unfortunate, as we would like to use the multiple selection feature.


image

New-UDSelect -Option {
    New-UDSelectGroup -Name 'Group One' -Option {
        New-UDSelectOption -Name 'One' -Value 1
        New-UDSelectOption -Name 'Two' -Value 2
        New-UDSelectOption -Name 'Three' -Value 3
    }
    New-UDSelectGroup -Name 'Group Two' -Option {
        New-UDSelectOption -Name 'Four' -Value 4
        New-UDSelectOption -Name 'Five' -Value 5
        New-UDSelectOption -Name 'Size' -Value 6
    }
} -Multiple -FullWidth

If I remove the -multiple parameter, the value is displayed.

Dear Marco,

Thank you very much for contacting Ironman Software!

My name is Ruben Tapia, a support engineer from PSU. While we review the details provided, please remember that you can add additional information by replying to this email.

To start over kindly share with me the following information:
• When the issue started?
• PSU Version:
• Screenshot of the error, if you have any additional examples
• PSU Logs:
• Browser console errors, if available

Based on the example shared, I understand the issue occurs when New-UDSelectGroup is used together with -Multiple, where the selected value is not displayed in the row even though it appears to be selected.

I will try to reproduce this behavior on my side so I can validate whether this is a product defect and, if confirmed, proceed with a formal internal escalation.

If possible, please also confirm whether this is only a display issue, or if the selected values are also affected when captured in -OnChange.

https://docs.powershelluniversal.com/apps/components/inputs/select

Best regards,

Ruben Tapia

Hi @RubenT91 ,

thank you for your feedback.

  • We haven’t used grouping so far.
  • We are using version 2026.1.5.
  • There are no error messages; it just doesn’t display after making a selection.
  • However, when using Invoke-Psusscript, the data is processed correctly.

For now, I managed to work around this by implementing the grouping with a new-udselect -disable. It’s not the most elegant solution, but at least it works temporarily. Still, it would be great if grouping could work properly in the long term.

Dear Marco,

Thank you for the additional details.

I appreciate you confirming that you are using PSU 2026.1.5, that there are no error messages, and that the selected data is still being processed correctly through Invoke-PSUScript. Based on that, this currently looks more like a display or rendering issue in the component rather than a data processing issue.

I also understand that you have implemented a temporary workaround by using a disabled New-UDSelect to simulate the grouping behavior. While that helps in the short term, I agree that the grouped control should work properly long term.

From my side, I will run a minimal reproducible test in my lab to validate the behavior directly. I also have the suspicion that there may have been work done on New-UDSelect in versions released after the 2026.1.x line. I am going to review my notes and the recent product changes to verify whether there was an improvement related to this feature.

If I can reproduce the issue locally, I will proceed with the formal internal escalation so the team can review it further.

For reference, the current Select component documentation shows grouped select and multiple select as supported scenarios, and it also documents that in multiple mode the selected values should still be available through $EventData as an array.

https://docs.powershelluniversal.com/apps/components/inputs/select
https://docs.powershelluniversal.com/changelogs/changelog

Best regards,
Ruben Tapia