SSRS 2019 RDL Internal/Hidden Parameter Shows as blank

Question

Details:
Server Deployment:
1. SQL Server 2019 Version 15.0.4223.1
2. SQL Server Reporting Services Version 15.0.8115.18148
3. ReportServer Database Compatibility is 2019 (150)

Visual Studios:
1. 2019 (Microsoft.ReportingServices.Designer.dll - Version Major 15).

Question:
How do I fix the blank SSRS 2019 Report Parameters when I deploy as 2016 or newer?

Issue:
If I deploy as 2008-2014 the Internal/Hidden parameters hide properly. If I deploy with 2016 or Later, the Internal/Hidden parameters hold a blank space in the deployed RDL (I assume there is an issue with the Visual Studios deployment, but could be the XML interpretation on the server).

Other Notes:
I saw that there was a fix for this for 2016.

KB4025021 - FIX: Blank spaces in the parameter area when you open SSRS report that contains Hidden or Internal parameters in SQL Server 2016

Thanks for any and all help!

Answer 1

Hi @Tony Cannon

You can upload an .rdl file created in an earlier version of Reporting Services to the new version and it is automatically upgraded on first use. The report server stores the report definition file in the original format. The report is automatically upgraded the first time it is viewed, but the stored report definition file remains unchanged.

From the official document ：https://learn.microsoft.com/en-us/sql/reporting-services/install-windows/upgrade-reports?view=sql-server-ver16

Best Regards,
Isabella

Answer 2

Hi @Tony Cannon

As you mentioned，this issue has been solved
Referenced thread：
https://support.microsoft.com/en-us/topic/kb4025021-fix-blank-spaces-in-the-parameter-area-when-you-open-ssrs-report-that-contains-hidden-or-internal-parameters-in-sql-server-2016-44311657-9977-d21f-e8b9-658ac427dd7e

To make sure ， I did a test in my VS 2019, and there is no such issue

In your situation ，you can edit the report in VS 2019 and upload it to the SSRS server ，make sure that you configure the reporting service project correctly（You can back up the old project or report to prevent project or reports from being corrupted）：

Referenced thread：
https://www.sqlservercentral.com/articles/ssrs-in-visual-studio

Best Regards,
Isabella

---

If the answer is the right solution, please click "Accept Answer" and upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 3

First, thank you for reaching out, but for me, I am having issues.

Prior to the forum post, I updated the VS 2019 and the extension to be the latest. I then restarted the laptop. I updated the SQL 2019 to the latest version available. The Databases are running in Compatibility Mode of 150. Nothing seems to help with the Issue.

I try to do everything in my power prior to requesting help from others, but I am beating my head against the wall on this one. What is odd is that the RDL deploys correctly if I deploy under a Target Server of 2008-2014 to the SSRS Server running SQL 2019 compatibility.

The issue only shows up when I change the Target Version to 2016 and Higher in Visual Studios.

What I will try next:

1. Creating a new RDL from scratch, instead of using an RDL that was created in 2017 or 2013 or 2008 that has been pushed forward through each release.
2. There is no way for us to re-create the 1200+ RDLs that our company has in place, but this will tell me if it is the Visual Studios side or the SSRS SQL Server side.

I will post back later today with my results. I have to assume that the issue is on the SSRS SQL Server side, but not sure.

Answer 4

Ok, so I created a NEW 2019 VS RDL with Internal/Visible parameters. A NEW RDL, reacts as I would have expected (see images below).

This now launches a new question of how does an RLD created in 2017 or 2013 or 2008 get converted to a 2019 RDL without re-creating 1200+ RDLs from scratch?
Tried with no success:

1. Editing an old report, saving, then deploying
2. Editing the XML through View Code and changing the top few lines to match the New 2019 RDL's XML.
3. Removing the RDL, recopying the old RDL to the 2019 folder and then Re-Importing the RDL as an existing report.

Answer 5

Update...

It definitely is an issue with the VS 2019, but still researching the why.
The following images are for the VS2019 Preview, the VS2019 Install Version and the SSRS Extension Version that I am using.