This may be a newbie question, and I have done quite a lot of searching for an answer but have had no luck.
I am using SSRS on SQL Server 2008 R2 (Standard edition) to generate XML reports. I have developed my report in Report builder 3 and uploaded the report to the Report server.
So far so good
Now I want to have a subscription that generates the reports in XML format and deposits it into a folder
No problem with this straight forward enough
How do I install an XML transform or specify the actual XML schema for the rendered document as I don't want to manually handle the generated report.
In the Report Builder software there appears to be a report property where I can specify as path which would have to be to a file on my local desktop but nothing on how to supply a similar file to the reporting server to use.
How do I do this?
And I thank all of you kindly stackoverflow souls in advance for your collective wisdom.
The answer to this is Read the Manual !
However finding information through the myriad of MS pages is an excercise in Google-foo
and old fashioned primary school collage.
You upload XSL through the Report Manager UI using IE and make sure that you have a server side path specified in the DataTransform field in Report Properties in ReportBuilder 3 for your RDL file
The essential confusion that I suffered from was that I thought the XSL transform would be incorporated into the RDL file for publication to the report server. It isn't
SO
For the DataTransform property:
1 A local absolute file path with a drive letter will not work
2 Use a path that makes sense on the report server
3 Either a relative path to the XSL file from the location of the RDL file
OR an absolute path from the Report Server should be used
Angus
Related
Our reporting services migrated from SSRS 2005 to SSRS 2016. In one specific report, a particular field of looks different on the pdf export. The font that's specified in the report rdl file for that specific field was internally designed a long time ago. We thought the problem had to do with it not being installed in the new server and we proceeded to installing it. After the installation, the result looked different (meaning that the recently installed font was being used) but still very different from the pdf export on the original server. Keep in mind that the rdl files for the report are exactly the same.
My questions is: is it possible to configure some kind of font mapping at server level, so it will replace one font for other, when exporting to pdf?
Any other ideas that explain why the same rdl file looks different in the two SSRS servers when exported to PDF?
Thanks in advance!
How can I find out where a Sharepoint Report is getting its data from?
Is it possible/easy?
I have a live report similar to one I am about to produce (it will use the same data source) but I do not know where this is coming from!
Thanks in advance!
The easiest is to just copy and rename the file, upload it and edit it in Report Builder on SharePoint. This way you will maintain the exact data source without needing to edit XML.
If you want to download it, go here Microsoft SQL Server 2008 R2 Report Builder 3.0
However, if you favour a text editor you can open the .rdl file to edit it.
Look in the XML for something like:
<DataSources>
..data source details here.
Where the data comes from
</DataSources>
<DataSets>
.. actual returned date definitions here, like columns.
What the data is
</DataSets>
I am using visual studio 2008 and reporting service 2008.
I created a .rdl reports. Now I want to convert .rdl to .rdlc. How can I do it?
Good question. According to spec whey should be more or less the same, but in reality they differ wildly depending on version. For instance if I open an RDLC file I created in Visual Studio 2010 in Report Builder 3.0 it works. But if I make a change in my RDL(C) file and try to open it in VS2010 I first get asked if I want to convert it to RDLC 2008 format (yes) and then I get the error message "The report definition has an invalid target namespace 'http://schemas.microsoft.com/sqlserver/reporting/2010/01/reportdefinition' which cannot be upgraded."
There is nothing to convert. All you have to do is to rename the file to .rdlc. This converts it from a server report to a client report. The underlying schema is the same, whether it's an .rdl or .rdlc file.
Take a look at FAQ #8 here: http://www.gotreportviewer.com/
I found working with MS support that converting an RDL to RDLC merely by changing the extensions results in a ReportViewer Control HTTPHandler error which is shown with a style of "dsiplay:none". It accuses the developer of not including the HTTPHandler in the web.config, when it is actually in the web.config. Using an rdlc created by VS in that project, then the reportviewer opens just fine and properly displays. MS support and I are still researching what other changes need to be made, but as of now, I can let people know not to drink the MSDN Kool-Aid.
I also tried changing the schemas namespace in the XML file and I got the same report definition cited above.
I've managed to obtain the report definition schema for SQL Server 2005, but cannot find the xmlns:rd="http://schemas.microsoft.com/SQLServer/reporting/reportdesigner" schema anywhere.
Is it part of the 2005 install buried somewhere? The reason I ask is because I've recently started writing RDL files for SQL Reporting Services. I'd like to be able to validate both schemas and get autocompletion working (I'm using Eclipse mostly). Any Ideas on how I can get ahold of this xsd?
That's just an XML namespace - there's no physical representation of that, really. The rd namespace is part of the report definition stuff - should be in your XSD already.
i have read this article about custom report items(CRI)
http://msdn.microsoft.com/en-us/magazine/cc188686.aspx
The only problem is that CRI are only usable in reporting service and not in local reports. My question is it possible some how to use CRI in local reports( RDLC ). Also i am interested in which version of reporting service is this possible, if possible
Best Regards,
Iordan
Custom report items are not supported in .rdlc files. (http://msdn.microsoft.com/en-us/library/ms251712(v=vs.90).aspx) This is likely the approach taken by Microsoft because the ReportViewer used with these files is a free control, while more complex features like third-party controls are supported only on a full SQL Server report server.
One thing in particular I have done in the past to get around this is generate custom charts/controls/images etc. As images and then send them into the report as an image. Not an ideal solution but it works.