SSRS Report not updating in Preview in Visual Studio - reporting-services

I've never seen this problem before.
The report elements are not updating from changes made in the Design mode in Visual Studio (2015). It's not a data issue - even static text box changes are not appearing.
I had removed the Member ID column, combined the last and first names into a single Member Name column, added a couple of columns and renamed SEX to Gender. Here's the Design view.
These changes should appear when I click on Preview but Visual Studio displays the old report.
As I mentioned, I haven't seen this before and haven't found any similar issues when using Google-Fu. I have tried restarting VS but that was no help. The only thing I did to get from the first pic to the second is to press the Preview button in Visual Studio. I've been trying to make it update for over half an hour now. I've updated and created hundreds of SSRS report over the last 15 years but have never seen or heard of this issue.
Is there some new preview caching that SSRS is now doing? It seems similar to the dumb data caching issue but I don't see where the report would be cached. This is completely ridiculous - what moron would create a caching for something being developed so changes can't be viewed?
How can I see the correct preview in my SSRS report in Viusual Studio?

Related

SSRS Report - Subreport can't be found

Ok, I have an SSRS report that has 2 subreports in it. One works just fine and the other works in testing but when I publish the report to my AMS platform under their instructions, the subreport comes up saying it can't be found. I can run the report through Visual Studio and it works just fine without a problem and I have rebuilt the entire project a few times and republished but I still keep getting the same error. I know that the publishing is working because I made a change to the main report to expand the subreport area and allow me to see the full error and that published fine. Any reason this would work through Visual Studio but not when published? The report along with the 2 subreports all are in the same directory as well.
Additional note to this. I just went to the master report in Visual Studio and deleted the subreport from it. I then re-added it and gave it a different name. Rebuilt the report and re-uploaded it including the already uploaded sub report and I am getting the same error but the error is referring to the new name I gave the subreport so it picked up the name change but not the actual sub report for some reason
Sometimes SSRS website caches your old report and doesn't get overridden by your new reports. On the SSRS website, try removing all of your reports including the main report. Then re-deploy.

SSRS FetchXML Report works in Visual Studi - empty in Dynamics 365

I at my whits end.
I have spent the last couple of days building a very in depth and mildly interactive report in Visual Studio 2015 (yes, I know but SMT wont let me upgrade to later version).
The report work fine in VS2015 but when uploaded to Dynamics 365, it is empty. The very odd thing though - the 'blank' report has the right number (3) pages however they are empty other than the header and footer.
I have a few Parameters that the user can choose from and it is the first time using these (just to set viability for a few tablix).
I don't even know where to start with searching this - all the results I am getting relate to reports having extra blank pages at the end but nothing about just coming up empty but still having the right number of pages.
I'm sorry that this seem (is) a bit of a wishy washy question. I just dont even know where to start asking for help...
EDIT: The problem appears to be with EnablePreFiltering="True" If I disable this, the report will run and return many many many pages and they are all formatted correctly. I have built my report so that everything is inside a single List which I apply the current users record to. Again - the problem is here somewhere.
Edit: (Wine has just been opened and the laptop charger is out - going to be a long night)

Charts and gauges not rendering in Report Viewer

I have a number of SSRS reports that contain various charts and/or gauges. All reports had been displaying the charts and gauges correctly. Now, none of the reports display any chart or gauge; just a blank space where the chart or gauge is supposed to appear. Yet tables in the same reports continue to display correctly.
In between it all working correctly and when the gauges and charts stopped displaying, I had gone into Reporting Services Configuration Manager and into SQL Server Management Studio so I may have inadvertently changed something that has caused the problem. But what? I've spent ages trying to find a cause but no luck.
I have even created an entirely new project and created an entirely new report containing a chart and a table. Same problem - the table displays correctly but there is just a blank space where the chart is supposed to be.
Because it is affecting all reports (even ones that I haven't touched and new ones that I create), it seems as if I have unwittingly changed some setting that is now causing Report Viewer to not display gauges and charts (but continues to display tables).
As I say, it had all been working fine.
Any suggestions as to what could cause this problem across all reports or where to look for the cause of the problem?
Thanks in advance.
I re-installed SQL Server (just ran the installer in repair mode - ie, without uninstalling first) and all the gauges and charts are displaying correctly again. I have no idea what the problem was.

SSRS in Visual Studio doesn´t update directly after changes have been made

I am building a report with one "go to report" and in that new report I have one subreport. Now, when I´m sitting and working with the report and for instance changing the format for a cell the report doesn´t view the new changes directly. Sometimes it does. Sometimes I have to wait a while, sometimes I restart BIDS. Has anyone experienced this problem before?
I think the way VS maintains subreport data when designing means the definitions can get stale; does a Rebuild Solution before previewing help?
This should hopefully make sure everything is up to date and for a Report project/solution it should be quick to rebuild.

Can't see subreport in the Report Manager

I've been following this tutorial (lesson 6) in order to build and deploy a sample report with an embedded subreport which reads its parameters' values from the parent report. This subreport is embedded in one of the group rows of the report's table, and both share the same datasource. Additionally, detail rows appear collapsed until the user presses the (+) button for each group of data in the table.
The report works great when I preview it at the Business Intelligence Development Studio (by the way, SQL 2005 Express edition) but when I deploy it and try to see in the Report Manager, the subreport is not shown. And, if I press the (+) button, the following message appears:
Some parameters or credentials have not been specified
Does anybody has the slightest idea of what I am doing wrong? Why does it works perfectly in the Report Viewer embedded in Visual Studio but not in the Report Manager web app?
Thanks in advance.
Does the subreport use the same Data Source as the parent report? If not, be sure to check the data source of the subreport to make sure it is correct. Check in Report Manager, not your local copy.
I'm beginning to think this could be an issue with the browser. I'm currently using Internet Explorer 8 Beta and I'm also experiencing weird behavior from the Report Manager. I've tried with Google Chrome and Firefox 3 and, although the navigation is not as smooth as I like, the problem seems fixed.
it happens when you use IE8 as a report browser. I faced same issue and when I tested on chrome it worked fine .
This may or may not be related, but I had a similar problem some time ago (except that in my case the reports were accessed through a custom web page) and it turned out we had an older version of the report viewer control (the version that came with Sql 2005 RTM). After upgrading to the latest version the issue went away.