I have an ssrs 2008 r2 report that has a date icon on 2 of the parameters that are dates that runs on an ssrs 2012 report server. This report is accessed by running a vb.net 2010 web form application via a report view control.
The date icon works is displayed when the ssrs 2010 report is accessed by the current version of Mozilla Firefox.
However when the report is accessed by Microsoft Edge or Chrome, the date icon is not displayed. The what is displayed in the default date/time parameter.
Thus can you tell me what I can do to make the date icon on the date parameters show when Microsoft Edge or Chrome?
Related
I am using SSRS 2019 and have an issue with date formats. I have a report that takes 2 date parameters using the report date picker, when I run the report through visual studio 2019 the report date picker dates are in the right format. When I upload it to my SSRS portal and run the same report and pick the dates it displays it MM-DD-YYYY rather than DD-MM-YYYY though it still works and generates the report. What I don't want to do is confuse users. I have checked all the region settings on my browsers as well as my server and all are set to English, I have the language in my report set to "en-UK". What I have noticed though is when I go to Manage the report through the portal and look at the changed and created dates they are also in the wrong format. This seems to be either an issue with my portal or server setting but I am not sure where else I can change this setting.
I thought I had managed to fix my issue with dates but it appears not and I may just have confused myself with too many changes.
My outstanding issue is, if I open up the report builder directly on the server the date format in the parameter box once you have clicked the calendar is as expected and works. If I run the report as normal on the reporting portal and click the date in calendar it sets it to MM-DD-YYYY. My server language setting is British English and my Browser is also set the same, what else could be changing the format?
SSRS 2008 R2 - have set up a back button in a linked report to link back to main report when clicked on. The text box nor the image shows up when user runs report from reporting services - anyone know why? Thank you
I have used Microsoft SSRS extensively with the Report Manager.
Today I have a unique requirement:
I need to deploy the header and footer of a report as Report Part. (I am completely new to report parts though)
After building the report in SSRS 2016 Report Designer, I go to the tab Reports, and choose Publish Report Parts.
In the Publish Report Parts tab, I see Select items to Publish.
In this window, I do NOT see the report header or footer. I see only the parameters used in the report.
When I use the SSRS Report Builder to Publish Report Parts, I see parameters and datasets (this time), but still not the header or footer.
Any idea on how to publish the header and footer alone as Report Part ?
We have an SSRS report (drill down report) built and it works fine through the browser. However when we open the same report through the report viewer (WPF application - report viewer hosted as windows forms host), the drill-down functionality is not visible. The report is shown without the drill down part.
Thanks
Resolved.
The issue was that the report in print layout format does not display the expanders. On changing the report layout to normal, the expanders were seen and worked as expected.
We have a website that's using Microsoft Report Viewer 9 to consume reports from Reporting Services. We noticed an issue with the controls to set parameters losing their values.
We have a date control that's used to set a Start Date parameter for the report. When we use the date picker (calendar pop-up) to set the date, all dropdown lists whose values are dependent on the date picker will lose their values. The values may be available in the dropdown, they just do not remain selected. The report data being returned is correct though.
I should not that we have not seen this issue in Microsoft Report Viewer 10 while viewing the same reports.
After contacting Microsoft support, we believe this is an issue with Report Viewer, and that it has been resolved when using Visual Studio 2010.