New-UDTabs -RenderOnActive – deprecation warning still present in 2026.1.7

Hi wolfbergmann,

Thank you for reporting this.

I reviewed the current status and I agree that this is confusing. The GitHub issue you referenced indicates that -Dynamic on New-UDTab should be enough, but the current Tabs documentation still shows New-UDTab -Dynamic together with New-UDTabs -RenderOnActive for the Dynamic Tabs scenario.

Because of that, I do not want to give you an incorrect migration recommendation until we confirm whether the warning is outdated, the documentation needs to be updated, or there is still a valid scenario where -RenderOnActive is required.

I am going to raise this internally so we can clarify the intended behavior and the recommended migration path for current PSU versions. For now, if the current implementation is working correctly aside from the warning, I would avoid changing production behavior only to suppress the message until we confirm the expected replacement pattern.

If possible, could you also share a small sanitized example of the New-UDTabs / New-UDTab block you are using? That will help us validate the exact scenario against the current behavior.

Thanks,
Ruben Tapia

Hi Ruben,

thank you for you fast response. Here is one of our simple implementations.

I hope this helps, thank you,
Wolf

New-UDLayout -columns 1 -Content {
    New-UDTabs -RenderOnActive -Id "tabs_XXX_$TabId" -ScrollButtons 'off' -Variant 'scrollable' -Tabs {
        #Code
        New-UDTab -Id 'fake_1' -Disabled -Content {
            #Code
        }
    }
}

Hi Ruben,

thank you for you fast response. Here is one of our simple implementations.

I hope this helps, thank you,
Wolf
New-UDLayout -columns 1 -Content {
New-UDTabs -RenderOnActive -Id "tabs_XXX_$TabId" -ScrollButtons 'off' -Variant 'scrollable' -Tabs {
#Code
New-UDTab -Id 'fake_1' -Disabled -Content {
#Code
}
}
}

@wolfbergmann

Hi Wolf,

Thank you for sharing the sample implementation.

This helps. One thing I noticed is that the simplified example still uses `New-UDTabs -RenderOnActive`, but the visible `New-UDTab` in the sample does not include `-Dynamic`. Since the current guidance around this behavior is tied to Dynamic Tabs, could you please also validate whether the real tabs inside your `#Code` blocks are using `New-UDTab -Dynamic`?

This week we will be running this in our lab against the current PSU behavior to compare a few scenarios:

1. `New-UDTabs -RenderOnActive` without `New-UDTab -Dynamic`
2. `New-UDTabs -RenderOnActive` with `New-UDTab -Dynamic`
3. `New-UDTab -Dynamic` without `New-UDTabs -RenderOnActive`

From your side, if possible, please test removing `-RenderOnActive` in a non-production environment and confirm whether you see any functional change, such as tabs rendering too early, slower initial page load, empty tab content, or different behavior when selecting a tab.

For now, I would not recommend changing the production implementation only to suppress the warning until we finish validating the intended behavior and migration path.

Thanks,
Ruben Tapia

Hi Wolf,

First, I apologize for the delay in getting back to you.

We completed the lab validation. The available isolated environment was running PSU 2026.1.5, while you reported 2026.1.7, so the results are preliminary rather than an exact version match.

We tested four scenarios and observed the following:

* The warning was emitted only when `New-UDTabs -RenderOnActive` was present, regardless of whether the individual tabs used `-Dynamic`.
* `New-UDTab -Dynamic` without `New-UDTabs -RenderOnActive` did not emit the warning.
* In our simple two-tab test, `-Dynamic` alone preserved the expected lazy rendering behavior.
* We did not observe any functional regression after removing `-RenderOnActive`.

These results suggest that the warning is directly tied to `-RenderOnActive` and that `New-UDTab -Dynamic` may be the intended migration path. However, we still need to confirm that no relevant behavior changed between PSU 2026.1.5 and 2026.1.7 before presenting this as the definitive recommendation.

If you had an opportunity to test without `-RenderOnActive` in your non-production environment, please let us know whether your complete implementation showed any behavioral or performance difference.

Thanks,
Ruben Tapia

Hi Ruben,
Tested on 2026.2.2 with New-UDTabs -RenderOnActive around New-UDTab -Dynamic tabs. Warning is there with -RenderOnActive and gone once I remove it. No other difference: tabs still render only on click, content loads fine, no empty tabs, no slower load.
So -Dynamic alone keeps the lazy rendering and dropping -RenderOnActive just removes the warning. Works as the migration path for us, assuming nothing changed between 2026.1.5 and 2026.2.2 on your end.
Thanks, Wolf