I have created a sub-report and embedded it in a report, the sub-report details appear when the report is run and also when the report is exported to PDF but when the report is exported to excel the sub-report details are not appearing, is possible for the information to appear?
Turns out that for sub- report details to appear in excel, the excel settings in the report designer should be 1,1. i.e the sub-report should be first item in its row.
Related
I have a matrix on my main SSRS report (Lets call it Main) which has the row groups:
Manager
Employee
Then my one Column Group has Count of Loans.
What I want to do is if a User clicks on "Click Me" underneath Excel Report, they could export an Excel file based on SSRS columns from a different SSRS report (let's call it Drill01). Basically just instead of going to the drillthrough report (Drill01), it should export that drillthrough report in an Excel format automatically.
Does anyone know how to do this or where I should search?
Easy.. have a drill down report that is formatted the way you want to see it in excel and render the report directly to excel via the drill down.. rather than just calling another report straight.. use the reportmanager link.. Use the Action - go to URL rather than go to report.. then you can specify the report link with the required parameters and the render style.. in this case Excel.
something like this: assuming you have two parameter called test and test1 (for example)
="http://yourreportserver/pages/folder.aspx/all the way to your report folder /reportname"&"&test=" & Parameters!test.value "&test2=" & Parameters!test2.value & "&rs:Command=Render&rs:Format=EXCEL"
Assuming you have the link correct.. it should just pop up asking you to save / open the sub report in Excel..
I want to create a report with dynamic number of columns.
I have used the solutions of these two following links to load and modify my rdlc report file.
http://dobrzanski.net/2009/02/06/how-to-dynamically-add-new-columns-to-report-created-with-reporting-services/
Why does C# XmlDocument.LoadXml(string) fail when an XML header is included?
but the problem is that when i use the Save method of xmlDocument to save the report anything happens.
what is my mistake???
I have a report where I have 50+ fields and I am exporting this report from crystal to excel. Once in excel the data columns are the proper width but the headings are truncated. Is there a way to get the headings to dynamically expand like the data does?
Have you tried using the grid line tools to line up all your columns and headers? Ensure snap to grid is on and that all headers/fields are the same size on screen.
Basically you want the crystal report in the designer to look similar to an excel report; with all the headers and fields in a grid like structure.
Crystal also produced a document many moons ago when they were owned by Seagate describing how to avoid formatting problems when exporting to excel. Check it out HERE
This helped me a load when I had to build stock reports and summaries for one of my customers.
Before I give a description of the problem, here is the list of technologies I am using - Excel 2010, PowerPivot Add-in, Win 7, Macros - VBA
I have created charts using multiple data sources (via PowerPivot). PowerPivot has provided Slicers and I want to print various states of the chart to separate PDFs for each value of the Slicer. I have already written the code that does the printing job. I need help with a snippet of code to loop through the list of Slicers and select them in such a way that the state of the chart changes everytime.
Through my research I found out that there is a property named SlicerItem.Selected which can be set to TRUE or FALSE to select a particular item in the Slicer. But apparently we can Set this property for OLAP pivot table/chart.
Any help is appreciated.
Thanks,
Rushabh.
If you convert your slicer to a report filter, then you can utilize Excel's builtin-feature of "show report filter pages"
Go to PowerPivot ribbon, option tab, Options. You'll see the item show report filter pages. It will create multiple worhsheets for each report filter selection.
I am working on an excel report in CrystalReports, in VS2005. I have a field in the Details section which can have up to 255 characters of text, and I want the height of the row in excel to expand so that the entire text can be seen initially when the report is generated.
I set CanGrow=True in the field's properties, and the field does seem to grow; the field is only one line (Height=159), but many of the rows display multiple, wrapped lines of text. Some rows intermittently have the bottem half of the last line of text cut off; the user has to expand the row a little bit to see it. There doesn't seem to be a particular field length that causes this - in one case, it has four lines total in the output, and in another case, it has only three.
Can anyone suggest what might be the cause of this, or how I could work around it?
Thanks in advance for any help you guys can offer.
[Edit: I am no longer working on this project, so I never found out what became of this setting. Most likely it wasn't fixed, since it's not a critical issue.]
One solution to this issue that I've come up with in the past is to have two separate reports. One for display and exporting to pdfor rtf and another report for exporting to Excel.
I know in general this is not a good approach because there is the possibility for data to be different in the export than the display report, but if careful it works well.
I have a situation where a client needs data printed in a specific format on a report, but there is way to much data to physically be able to fit on a page. We worked out a solution that I run a "display version" of the report that fits most of the data, but the rest of the data necessary for there client is added only to the "Excel version" of the report.
To do this I simply load the "display report" to the report viewer as you normally would, but when you go to export the report I load the "excel report" with the same parameters as the "display report" and call the code to export the data to Excel.
By using this method the "display report" can be formatted any way necessary without having to worry about messing up the export to excel. The excel report fields can then be made a smaller size than required by the display report because the data should export even regardless of the size of the field. Doing this allows you to fit more data on the Excel export report.
Since both reports use the same datasource you will have an issue if you make a change that you have to remember to go verify the database on each report to see the new database changes, but this method allows you to include more data and in a different format than the display version of the report.
Hope this helps.
While not a solution for Crystal (I don't know of one), as part of the reporting team at GrapeCity-Data Dynamics, we've worked with similar issues taking free-form reports to excel spreadsheets for a decade. In our Data Dynamics Reports product we came up with a completely new way of solving the problem of exporting reports to excel.
We allow you to create a template for the report output. The template is a basic excel file with place holders for the various textboxes (or other controls) and regions (tables, lists, etc.) in the report. You can open this template inside of excel and modify the properties of the cells and rows. In the scenario you describe, you can export a "template" from Data Dynamics Reports and then modify the autosize property of the row in the template containing the placeholder for the textbox you're struggling with.
When you export the report to excel next time, just specify the template to Data Dynamics Reports (which can be done programmatically and transparently to the end user) and Data Dynamics Reports will honor all settings you specified in the template.
This is hard to explain so there is a ~2 minute screencast that shows this feature at our website in the following location:
http://www.datadynamics.com/Products/DDRPT/ScreencastViewer.aspx?ID=XLS01
For more information about the product and for a free trial download visit: http://www.datadynamics.com/DataDynamicsReports
Scott Willeke
GrapeCity - Data Dynamics