Hotfix: Unique and not-empty user variable names enforced
User variable names are now validated when creating or renaming user variables in the administration UI. Duplicate names are rejected and the grid is refreshed to restore the persisted server state.
User variable names must now be unique and not null. In addition to the existing GUI and backend validation, ReportServer now also enforces this rule on database level using a unique constraint.
Duplicate user variable names can lead to ambiguities when reports resolve user variables. During upgrade, existing duplicate, empty, or missing user variable names are adjusted automatically to allow the new constraint to be created.
Administrators should review all user variable definitions under User Root → User Variable Management.
During the upgrade, duplicate user variable names are renamed automatically. The generated names contain _DUP_. Empty user variable names are also renamed and receive a generated name containing uservariable_DUP_.
Administrators should verify that these generated names are appropriate and update affected user variables and reports if necessary. Duplicate user variables can also be deleted, but the corresponding reports must be adapted accordingly.
Example of automatically renamed user variables:
