Hi
I am new and am trying to find the way to increase width of the parameter value in report. Report is designed on two parameter and based on first parameter value of another parameter is populated. This report is working fine in designer view and in normal .aspx web ReportViewer but width is not coming properly for parameters. So I used HTML5 report viewer but it seems initial report is rendering properly with First parameter values data populated from datasource. But it seems it does not allow to change the parameter value and also it is not fetching other parameter report value and it seems selection is getting reset. They are a multivalue parameters.
Do you know how can we resolve this issue as it seems ReportViewer in aspx is working fine but it does not work same in HTML5 report viewer?
Regards
Vraj
I am new and am trying to find the way to increase width of the parameter value in report. Report is designed on two parameter and based on first parameter value of another parameter is populated. This report is working fine in designer view and in normal .aspx web ReportViewer but width is not coming properly for parameters. So I used HTML5 report viewer but it seems initial report is rendering properly with First parameter values data populated from datasource. But it seems it does not allow to change the parameter value and also it is not fetching other parameter report value and it seems selection is getting reset. They are a multivalue parameters.
Do you know how can we resolve this issue as it seems ReportViewer in aspx is working fine but it does not work same in HTML5 report viewer?
Regards
Vraj
3 Answers, 1 is accepted
0
Hello Vraj,
We will need additional information on your report parameters configuration in order to advise further.
It would be best if you open a support ticket where you can zip and attach a runnable sample project with dummy data exhibiting the described issue.
You may also find useful the following help articles elaborating on report parameters configuration:
Regards,
Nasko
Telerik
We will need additional information on your report parameters configuration in order to advise further.
It would be best if you open a support ticket where you can zip and attach a runnable sample project with dummy data exhibiting the described issue.
You may also find useful the following help articles elaborating on report parameters configuration:
- How to: Cascading Parameters with applied filtering on Report level
- How to: Cascading Parameters with applied filtering on data source level
Regards,
Nasko
Telerik
Check out the Telerik Platform - the only platform that combines a rich set of UI tools with powerful cloud services to develop web, hybrid and native mobile apps.
0
Astin
Top achievements
Rank 1
Rank 1
answered on 10 Jun 2014, 01:47 PM
Thanks Nasko for your update but I found issue resolution replacing new latest Newtonsoft.Json.dll version. As I mentioned in my post that report is working fine in.aspx and when trying to manipulate parameter area, I needed to use HTML5 report viewer and that is where parameter was not allowing to choose to Preview report.
But I now have got another issue where this HTML5 report viewer is not working on IIS server whereas it is working on my local environment. I have created a ticket for the same and am trying to find the solution. Let me know if you have some idea on the same. I also have attached file here if you can help in this post.
Regards
Vrajesh
But I now have got another issue where this HTML5 report viewer is not working on IIS server whereas it is working on my local environment. I have created a ticket for the same and am trying to find the solution. Let me know if you have some idea on the same. I also have attached file here if you can help in this post.
Regards
Vrajesh
0
Hello Astin,
Please test to adapt the relative paths to the viewer's HTML, CSS and JS files and the service address based on your project structure. For more details check the following MSDN article: ASP.NET Web Project Paths.
You can also use Fiddler to detect which requests failed and the reason why. To verify if the REST Service has been implemented successfully you can make a request for the available document formats using the following URL:
http://localhost:[portnumber]/api/reports/formats
If the request is successful you should receive the document formats encoded in JSON. For more information see: Get Available Document Formats.
Regards,
Nasko
Telerik
Please test to adapt the relative paths to the viewer's HTML, CSS and JS files and the service address based on your project structure. For more details check the following MSDN article: ASP.NET Web Project Paths.
You can also use Fiddler to detect which requests failed and the reason why. To verify if the REST Service has been implemented successfully you can make a request for the available document formats using the following URL:
http://localhost:[portnumber]/api/reports/formats
If the request is successful you should receive the document formats encoded in JSON. For more information see: Get Available Document Formats.
Regards,
Nasko
Telerik
Check out the Telerik Platform - the only platform that combines a rich set of UI tools with powerful cloud services to develop web, hybrid and native mobile apps.