I developed reports in SSRS 2012. Users view reports using IE11 (version 11.0.9600.18537). I set the report columns visible(Column headers) while scrolling. It works fine in the reportviewer but when I deploy it to the report manager header(report column headers) does not scroll anymore. On the IE 11 I tried to change the document mode to 10 and it works fine. But upon refresh it goes away. Now fixing the browser is hard as we may have to make a policy change across the company which is no go.
Please suggest a SSRS server side fix.
Already tried the server side fix. But failed to work.
https://www.mssqltips.com/sqlservertip/3666/sql-server-reporting-services-ssrs-is-not-compatible-with-internet-explorer-11/
As a matter of fact I don't even have the suggested meta tag in the "reportviewer.aspx" but I tried to add it anyway with no success of working.
I expect column headers to be visible while scrolling on IE11 on SSRS 2012 report manager. Since we own SSRS 2012 report manager and I have admin access I can try to make changes in that server.
Found the fix, under "ReportManager\Pages\Report.aspx" there is the tag which I modified from content="IE=Edge" to content="IE=5"
to
Related
When I launch Domino Designer, I don't see any databases listed. When I open DD for a specific database, I get the same thing. My Notes client still works fine.
Is my DD behavior due to me no longer hitting a live Domino server? (My user license is good until 2024).
UPDATE: I noticed the errors below under Problems:
Menu "Window --> Show Eclipse Views --> Applications" will show you selected databases in "Applications" tab in Domino Designer.
Using the repair/modify options did not work. The solution was to completely uninstall Notes/Domino Designer/Admin and reinstall.
SQL Server 2016, SSRS: I have an expandable group that works correctly in Report Builder or Visual Studio SSDT, but does not display when run on the server.
My charter was to create a report that didn't rely on pop-ups or new windows to display detail data. I've managed to embed that detail data below each order. A single dataset feeds the entire report. The user views a list of orders and can click an expand control on a given order to see the detail.
There are three groups in the report: District, Date and Order. Each group is expandable. At the bottom most 'Order" level several rows are displayed, including three that have tablixes embedded in them.
Problem: The order number and expand control [+] work fine in development but are not visible when running on the server.
This image shows the report in Development mode in VS 2017. Note the sections starting with 'Order Type' and 'Low Flow Test are Tablixes, each with a single header and a single row of data:
This second image shows the report in preview mode in VS 2017. It's displaying correctly with a single order expanded:
This third image shows the same report running on the server. Note the 'OrderNum' group cannot be expanded - the Order number field isn't even visible:
Both Visual Studio and Report Builder render this report as desired. When running in a browser this fails on IE, Chrome and Edge.
Either this is a bug or there's something I don't know about how this all works.
I had this issue and got it resolved. It was because of the over-flow: hidden that was put on these tablix headers. Under alignment my vertical alignment was set to 'bottom'. After setting it to 'Default' it was fixed. I guess having alignment as bottom made the browser think it was over-flow text.
I have several reports created with multi value parameters. They are deployed to the report manager and run fine from chrome. When ran from Internet Explorer 11, when a parameter is chosen, I cannot click on the down arrows or scroll bar of the multi valued param. When I do it closed the param and would not scroll. I can use the scroll wheel but clicking does not work. This only happens in IE 11 which happens to be what 90 percent of our users use. Any ideas on a fix? This is SQL Server 2016.
I am using Crystal report in VB.NET web application.
IDE: VS 2010 Ultimate
Crystal Report installed: V13.0.16
I am able to view my crystal report with data, but when i click the refresh button or next page button or export option in CR menu.
the whole filter condition is reset and all the data related to the report is displayed/exported.
when i re enter URL which has filter condition then it loads the data with filters.
Request.QueryString() is used to get the filter details
and report details.
I need help at the earliest. Kindly help me.
I have fixed the issue which is posted above.
The application was developed using Crystal report version 13.0.0.99 (approximately 6 years before). I tried to upgrade it with latest version but it didn't help me on time. When i use the version which is used during development solved the error. The export or next page or refresh post back didn't reset the report content.
I am not sure how to fix it with most recent version of crystal report. This Discussion sounds like a solution with latest version but i don't have additional time to use it. I hope this could help some one in need.
I have an SSRS report which drills through to sub reports via actions. The report functions correctly in the VS environment, and correct once deployed to the server and viewed through a browser.
The report however is also viewed inside our in-house app via a Microsoft.Reporting.WinForms.ReportViewer - and while it renders on screen correctly, clicking the element that would normally take me to a sub-report no longer functions.
I have had a look around and there seemed to be an issue around VS2010 SP1 where this stopped working, however I'm currently stuck with VS2008. This seems to be the majority of results I'm getting.
Anyone have any ideas?
Many thanks.
OK have found issue.
The text box in question had three place holders. A reference No, A date and an age. I wanted to trigger the sub report if someone clicked on the reference no. While this worked fine in VS and IE, it failed to work in the Microsoft Report Viewer control.
I have now set the action against the containing text box, rather than against a single placeholder/expression within that box. While this has solved the immediate issue that I have, it would not work if you wanted multiple actions from different placeholders in a single text box.
But for now, I'm all good, and all solved.