In SSDT 2014 there is some lines in ultiple groups that show group bound:
but in SSDT 2016 there is not such this lines. How I can add them?
Thanks
This solution is going to seem counter-intuitive but based on what I'm seeing I believe it will work. The lines you're seeing there that are missing in SSRS 2016 are called the Major Tick Mark lines. In SSRS 2014, the default LineStyle appears to be "Default". When I opened Report Builder for SSRS 2016, the default value was "None". My guess is there is a mapping that if it's default in 2014 (i.e., "Default") that this will map to the default in 2016 (i.e., "None").
To fix this, open your report in SSDT 2014 or SSDT 2016 and change the MajorTickMarks LineStyle to "Solid". As the MajorTickMarks LineStyle of Solid exists in both SSRS 2014 and SSRS 2016, it should carry over from one server to another.
If that doesn't work, I would recommend downloading the SSRS 2016 Report Builder and using that to set the LineStyle to "Solid" and the re-loading the report on the 2016 server.
Below are screenshots of the default LineStyle values for the MajorTickMarks when you create a new report in Report Builder 3.0 for 2012/2014 versus Report Builder for 2016.
Related
I have a dataset that fetches data from SSAS cube using MDX query, I executed and confirmed that the MDX query retrieves measure values in SSMS Query Designer. However, when I drag the fields onto a Table in SSRS report, only the dimension values appear but not the measure (it shows up empty).
I believe this is an issue specific to Visual Studio 2017, the SSRS report displays the measure values fine when run in Visual Studio 2015.
I have only started encountering this issue in the last two days. Before that the report was displaying values correctly in Visual Studio 2017.
Please provide steps to fix this issue.
Rebuild rdl file in VS 2017 - the issue is probably because of different default xml schema versions.
I have an 2016 SSRS report that hides and shows rows based on toggles. The report was recently updated to 2016 from 2005 and the toggles broke on the 2016 server. However, when using Visual Studio 2017 preview mode, the report works as expected. Thus making it hard to determine where the error is. Any ideas? The schema in the XML is set to 2016.
All of the reports I have on our SSRS server work great through the SSRS ReportViewer web control but I have 2 reports that will not render. I fill out the parameters and the page refreshes with nothing. No loading gif, no toolbar, just the parameter controls.
I have tried using the ReportViewer on Chrome, Firefox and IE. All reports but these two certain reports work great.
I've tried the methods listed in:
SSRS 2008 R2 - SSRS 2012 - ReportViewer: Reports are blank in Safari and Chrome
Only 2 reports out of >10 fail to render on SSRS 2008R2 SP2
Does anyone know why certain reports may not display while others will?
Update: I have found that if I pass in a test parameter, the report will render with 0 results. However if I pass in a valid value, I get nothing.
Turns out to have been a couple of things.
First was something to do with the query. One of the parameters accepted values with commas in it and when changing the values to not contain commas, the report worked fine. This might have been attributed to how the values were being passed to the parameters.
The DIV containing the report needed overflow: auto; added to it's styles.
I assume you are on SSRS 2008 r2. While I'm not familiar with using the web version of ReportViewer (I always preview my reports in Visual Studio), I have found that if my Data Source loses its connection string this can happen.
Do you have visual studio with SSRS? If so can you open your report there and preview it?
I have two reports in a report project that have somehow been updated to use the 2010 report defintion;
<Report xmlns="http://schemas.microsoft.com/sqlserver/reporting/2010/01/reportdefinition" ...>
However, all other reports in the project, including new reports added to the project use the 2008 definition;
<Report xmlns="http://schemas.microsoft.com/sqlserver/reporting/2008/01/reportdefinition" ...>
How can i force this update across the other reports in the project?
=EDIT=
The Visual Studio 2012 compatibility chart specific to SQL Server Report Project says;
If you add a feature that’s specific to Visual Studio 2012, the report
schema is upgraded automatically and you can no longer open the
project in Visual Studio 2010 SP1.
Now i just need to figure out what a 2012 feature is...
One option is to add a Map (2012 feature) to the report, save it, then delete the Map, and save again. Note that adding the Map and deleting before saving will not enforce the upgrade.
In the report properties find InitialPageName an give it a value. InitialPageName is a 2010 feature, as well as the PageName property that can be set on various report elements, such as Tablix and Graph.
We have a set of reports that were created using BIDS 2005 and we are trying to deploy these onto a 2008 R2 server. The problem we are coming across is that on first view of one of our reports SSRS 2008 R2 is looking to see if it can upgrade the report and all the subreports, this is causing the main report to be upgraded to 2008 but the subreport contains a third party Custom Report Item which will not allow the subreport to be upgraded. We would prefer it if the 2008 R2 did not try to upgrade any of the reports at all.
As you can see from this article: http://technet.microsoft.com/en-us/library/ms143674(v=sql.105).aspx
(Section : Upgrading a Report with Subreports)
Microsoft states that :
The main report can be upgraded but one or more subreports cannot be upgraded. The main report is processed by the SQL Server 2008 Reporting Services report processor, but the rendered report shows the message "Error: Subreport could not be processed" in the location where the subreport that could not be upgraded would appear.
This is clearly useless as we need to be able to see the subreport!
So my question is:
Can we force SSRS to always use the 2005 RDL files without automatically upgrading?
I think the easiest answer will be to edit the parent report in BIDS 2005 and add a CustomReportItem, maybe even with visibility set to false. This should force SSRS 2008R2 to flag the report as needing backwards compatibility.
Alternatively, this flag is stored somewhere in the database, but I'm not sure where. I don't have access to any 2005 reports running with that processing engine, so I can't go hunting.