Query |
Response |
I looked into this a bit more, and came to the conclusion that the Report Designer is happier with a 2010 schema instead of a 2016 schema...
I think this will actually work OK for us, since we probably don't need the most recent 2016 functionality in these particular RDL's.
So instead of: <Report xmlns="http://schemas.microsoft.com/sqlserver/reporting/2016/01/reportdefinition" ...
... we are going with:
<Report xmlns="http://schemas.microsoft.com/sqlserver/reporting/2010/01/reportdefinition" ...
|
Since SQL2010 schema version don’t have parameter layout features in MS SSRS server, so it is working properly in Report Designer.
Currently we have below Parameter layout available in 2016 schema not loading in Report Designer issue which we will fix and fix changes will be available in next weekly nuget release which will rollout on February 12, 2019. |
Our RDL is 2016 Schema, so it includes a ParametersLayout section. If we use the Designer to add in a new Parameter using the Report Designer, and then save the report, it doesn't look like the Designer is adding to the ParametersLayout section.
So, when we try to save the modified RDL back to SSRS, it is complaining with "The parameter panel layout for this report contains more parameters than total cells available
|
We were able to reproduce the mentioned parameter layout not updated properly issue in web report designer and we have confirmed that the issue is a defect and logged a defect report on this. You can keep track of this bug from the feedback portal below.
The fix for this issue will be estimated to be available in next weekly nuget release which will rollout on February 12, 2019.
If you have any more specification/precise replication procedure or a scenario to be tested you can add it as a comment in the portal.
|