Report of Reports

Are there any example of SSRS reports using an rdl file as the source for the report. I.e. a Report of Reports?

Hi Freddie,

could you please elaborate a bit more?

thanks, 99

|||

One way of doing this in RS 2005 is to render a report with the xml data rendering extension as xml document. This is then used as input for the xml data extension. However, getting the query setup correctly and working is a bit tricky. A specific sample and explanation for this approach will be available in an upcoming MSDN article about the RS 2005 Xml data extension later this summer.

-- Robert

|||

Thanks Robert,

I did find an article "Integrate XML into Your Reporting Environment" by Bill Wolff at http://www.ftponline.com/special/sqlserver/bwolff/

I will be looking for the upcoming MSDN Article.

To elaborate more on my question...I would like to document my reporting service reports using reporting services. For example which property has custom code (e.g. IIF).

Report of Reports

Are there any example of SSRS reports using an rdl file as the source for the report. I.e. a Report of Reports?

Hi Freddie,

could you please elaborate a bit more?

thanks, 99

|||

One way of doing this in RS 2005 is to render a report with the xml data rendering extension as xml document. This is then used as input for the xml data extension. However, getting the query setup correctly and working is a bit tricky. A specific sample and explanation for this approach will be available in an upcoming MSDN article about the RS 2005 Xml data extension later this summer.

-- Robert

|||

Thanks Robert,

I did find an article "Integrate XML into Your Reporting Environment" by Bill Wolff at http://www.ftponline.com/special/sqlserver/bwolff/

I will be looking for the upcoming MSDN Article.

To elaborate more on my question...I would like to document my reporting service reports using reporting services. For example which property has custom code (e.g. IIF).

Report Manager Print does not respect page orientation or margins.

I have been experiencing a problem when viewing reports in IE (versions 6 and 7) in that the page orientation and margins set in the RDL are not passed to the print layout. I am using the one-time download print program for RS, not IE's print dialog.

As an example, I have a Landscape report with .25 margins all around. When I go to print, it is defaulted to Portrait with 1 inch margins all around.

Any help would be greatly appreciated.

-Nick

Started thread prematurely, answer in another thread. Apparently, linked reports do not retain the layout of the base report.

Report layout:- Inconsistencies between page height and HTML Rendered

I'm having problems with what is displayed in the browser being different to what is defined in the RDL and what is exported to PDF.
I have set height to 21cm and width to 29.7 with 0cm margins. There is one table in the report.
When I export the report to PDF its fine, all pages are 21x29.7cm, landscape.
However, when I view the report in the report manager (in a browser) the pages are much longer than they should be... nearly twice as long (as if to make the report portrait again?)
Has anybody had this problem with lanscape reports? Any ideas on how to resolve this?
I've made lots of different landscape reports and get the problem every time. I find it hard to believe that no one else is having this issue...
ThanksI'm having this problem, too, but since the reports export to PDF no problem, i've considered it a low priority. I'm not even convinced it's a bug, as such, due to the nature of the web and the fact that web-delivered information generally runs on pages a great deal longer than standard portrait-sized pages. That is, I've chosen to consider the page-length property to be a PDF-specific property, and not even applicable to ASP-delivered reports. It doesn't bother me to have users browsing the reports online in this format as long as they can ultimately export them to PDF if they wish.

What does bother me is the seeming randomness of the length of the ASP-delivered report pages. Some of the pages seem double-lengthed, others triple or more. What gives?

|||I know what you, however, its my users that are complaining about it!
If there was some way of being able to "lock" the table headings it wouldnt be a problem - is there any way this can be done? It is one of the most requested features of my users.
Any help is much apprerciated.|||

In SQL Server 2005, you can 'lock' the headers for a table or a matrix.

If you right click the border of the table in the Layout pane of report designer, on the General tab in the Table Properties dialog, there is a check box called "Header should remain visible while scrolling". If you check that, in HTML the table header will always be shown.

-Lukasz

This posting is provided "AS IS" with no warranties, and confers no rights.

|||I had the same problem and solved it, so thought i would share this with anyone who comes across it. I don't know why it exactly occurs but if you change the Interactive page size to be a bit larger then the html is rendered as the pdf and the pdf is unaltered. Interactive page is is reached by clicking on the yellow right hand side of the report off the actual report and then in the properties pane.|||

my report is displayed as one long page when viewed in the browser, while it is displaying correctly in several pages when exported to PDF. Can you please helpe me!!

Regards

Dwarka (hdwarka@.yahoo.com)

Report layout:- Inconsistencies between page height and HTML Rendered

I'm having problems with what is displayed in the browser being different to what is defined in the RDL and what is exported to PDF.
I have set height to 21cm and width to 29.7 with 0cm margins. There is one table in the report.
When I export the report to PDF its fine, all pages are 21x29.7cm, landscape.
However, when I view the report in the report manager (in a browser) the pages are much longer than they should be... nearly twice as long (as if to make the report portrait again?)
Has anybody had this problem with lanscape reports? Any ideas on how to resolve this?
I've made lots of different landscape reports and get the problem every time. I find it hard to believe that no one else is having this issue...
Thanks
I'm having this problem, too, but since the reports export to PDF no problem, i've considered it a low priority. I'm not even convinced it's a bug, as such, due to the nature of the web and the fact that web-delivered information generally runs on pages a great deal longer than standard portrait-sized pages. That is, I've chosen to consider the page-length property to be a PDF-specific property, and not even applicable to ASP-delivered reports. It doesn't bother me to have users browsing the reports online in this format as long as they can ultimately export them to PDF if they wish.

What does bother me is the seeming randomness of the length of the ASP-delivered report pages. Some of the pages seem double-lengthed, others triple or more. What gives?|||I know what you, however, its my users that are complaining about it!
If there was some way of being able to "lock" the table headings it wouldnt be a problem - is there any way this can be done? It is one of the most requested features of my users.
Any help is much apprerciated.
|||

In SQL Server 2005, you can 'lock' the headers for a table or a matrix.

If you right click the border of the table in the Layout pane of report designer, on the General tab in the Table Properties dialog, there is a check box called "Header should remain visible while scrolling". If you check that, in HTML the table header will always be shown.

-Lukasz

This posting is provided "AS IS" with no warranties, and confers no rights.

|||I had the same problem and solved it, so thought i would share this with anyone who comes across it. I don't know why it exactly occurs but if you change the Interactive page size to be a bit larger then the html is rendered as the pdf and the pdf is unaltered. Interactive page is is reached by clicking on the yellow right hand side of the report off the actual report and then in the properties pane.|||

my report is displayed as one long page when viewed in the browser, while it is displaying correctly in several pages when exported to PDF. Can you please helpe me!!

Regards

Dwarka (hdwarka@.yahoo.com)

Report layout:- Inconsistencies between page height and HTML Rendered

I'm having problems with what is displayed in the browser being different to what is defined in the RDL and what is exported to PDF.
I have set height to 21cm and width to 29.7 with 0cm margins. There is one table in the report.
When I export the report to PDF its fine, all pages are 21x29.7cm, landscape.
However, when I view the report in the report manager (in a browser) the pages are much longer than they should be... nearly twice as long (as if to make the report portrait again?)
Has anybody had this problem with lanscape reports? Any ideas on how to resolve this?
I've made lots of different landscape reports and get the problem every time. I find it hard to believe that no one else is having this issue...
Thanks
I'm having this problem, too, but since the reports export to PDF no problem, i've considered it a low priority. I'm not even convinced it's a bug, as such, due to the nature of the web and the fact that web-delivered information generally runs on pages a great deal longer than standard portrait-sized pages. That is, I've chosen to consider the page-length property to be a PDF-specific property, and not even applicable to ASP-delivered reports. It doesn't bother me to have users browsing the reports online in this format as long as they can ultimately export them to PDF if they wish.

What does bother me is the seeming randomness of the length of the ASP-delivered report pages. Some of the pages seem double-lengthed, others triple or more. What gives?|||I know what you, however, its my users that are complaining about it!
If there was some way of being able to "lock" the table headings it wouldnt be a problem - is there any way this can be done? It is one of the most requested features of my users.
Any help is much apprerciated.
|||

In SQL Server 2005, you can 'lock' the headers for a table or a matrix.

If you right click the border of the table in the Layout pane of report designer, on the General tab in the Table Properties dialog, there is a check box called "Header should remain visible while scrolling". If you check that, in HTML the table header will always be shown.

-Lukasz

This posting is provided "AS IS" with no warranties, and confers no rights.

|||I had the same problem and solved it, so thought i would share this with anyone who comes across it. I don't know why it exactly occurs but if you change the Interactive page size to be a bit larger then the html is rendered as the pdf and the pdf is unaltered. Interactive page is is reached by clicking on the yellow right hand side of the report off the actual report and then in the properties pane.|||

my report is displayed as one long page when viewed in the browser, while it is displaying correctly in several pages when exported to PDF. Can you please helpe me!!

Regards

Dwarka (hdwarka@.yahoo.com)

Report layout:- Inconsistencies between page height and HTML Rendered

I'm having problems with what is displayed in the browser being different to what is defined in the RDL and what is exported to PDF.
I have set height to 21cm and width to 29.7 with 0cm margins. There is one table in the report.
When I export the report to PDF its fine, all pages are 21x29.7cm, landscape.
However, when I view the report in the report manager (in a browser) the pages are much longer than they should be... nearly twice as long (as if to make the report portrait again?)
Has anybody had this problem with lanscape reports? Any ideas on how to resolve this?
I've made lots of different landscape reports and get the problem every time. I find it hard to believe that no one else is having this issue...
ThanksI'm having this problem, too, but since the reports export to PDF no problem, i've considered it a low priority. I'm not even convinced it's a bug, as such, due to the nature of the web and the fact that web-delivered information generally runs on pages a great deal longer than standard portrait-sized pages. That is, I've chosen to consider the page-length property to be a PDF-specific property, and not even applicable to ASP-delivered reports. It doesn't bother me to have users browsing the reports online in this format as long as they can ultimately export them to PDF if they wish.

What does bother me is the seeming randomness of the length of the ASP-delivered report pages. Some of the pages seem double-lengthed, others triple or more. What gives?

|||I know what you, however, its my users that are complaining about it!
If there was some way of being able to "lock" the table headings it wouldnt be a problem - is there any way this can be done? It is one of the most requested features of my users.
Any help is much apprerciated.|||

In SQL Server 2005, you can 'lock' the headers for a table or a matrix.

If you right click the border of the table in the Layout pane of report designer, on the General tab in the Table Properties dialog, there is a check box called "Header should remain visible while scrolling". If you check that, in HTML the table header will always be shown.

-Lukasz

This posting is provided "AS IS" with no warranties, and confers no rights.

|||I had the same problem and solved it, so thought i would share this with anyone who comes across it. I don't know why it exactly occurs but if you change the Interactive page size to be a bit larger then the html is rendered as the pdf and the pdf is unaltered. Interactive page is is reached by clicking on the yellow right hand side of the report off the actual report and then in the properties pane.|||

my report is displayed as one long page when viewed in the browser, while it is displaying correctly in several pages when exported to PDF. Can you please helpe me!!

Regards

Dwarka (hdwarka@.yahoo.com)

Report in CRM ?

Hi All,
I created a report for Microsoft CRM 3.0... Do I have to "deploy" it
to the CRM server in order to use it in CRM or only to "build" the RDL
and add it in CRM ?
Any tips on this will be very helpfull
ThanksRDL is all XML, I dont really think "building" does much
"Frank" <flefe2000@.gmail.com> wrote in message
news:1170335048.873329.127820@.s48g2000cws.googlegroups.com...
> Hi All,
> I created a report for Microsoft CRM 3.0... Do I have to "deploy" it
> to the CRM server in order to use it in CRM or only to "build" the RDL
> and add it in CRM ?
> Any tips on this will be very helpfull
> Thanks
>

Report FullPath Property

I have a report (A.rdl) with a FullPath property set to my C:\Temp folder.
The rest of my reports have a FullPath property of C:\Documents and
Settings\......... I want to permanently change the FullPath property of
report A.rdl to be the same as that of the other reports C:\Documents and
Settings\.........
With report A.rdl open in design view, I used the "Save A.rdl AS..." and
saved the report to the desired folder location. The new path displayed as
desired, I deleted the A.rdl files that remained in the C:\Temp folder, and
closed down Reporting Services. When relaunching RS, the A.rdl report file
was being requested from the old C:\Temp folder area. I restored the
deleted files from the recycle bin to correct the problem. I really need to
discover how to permanently locate this A.rdl report to a new location and
have Reporting Services look to the new location for the report file, as it
does with the other *.rdl files I have. I do not see in the report code
where a path is specified when the report opens and cannot directly edit the
FullPath Property from the property window.
Any ideas are welcome.I believe the key to this problem was using the "Save As feature..." then
rebuilding the entire solution, not just the report, top tier level of
project.
"box2003" <spambox03@.yahoo.com> wrote in message
news:O7NSH3D6EHA.796@.TK2MSFTNGP09.phx.gbl...
>I have a report (A.rdl) with a FullPath property set to my C:\Temp folder.
>The rest of my reports have a FullPath property of C:\Documents and
>Settings\......... I want to permanently change the FullPath property
>of report A.rdl to be the same as that of the other reports C:\Documents
>and Settings\.........
> With report A.rdl open in design view, I used the "Save A.rdl AS..." and
> saved the report to the desired folder location. The new path displayed
> as desired, I deleted the A.rdl files that remained in the C:\Temp folder,
> and closed down Reporting Services. When relaunching RS, the A.rdl report
> file was being requested from the old C:\Temp folder area. I restored the
> deleted files from the recycle bin to correct the problem. I really need
> to discover how to permanently locate this A.rdl report to a new location
> and have Reporting Services look to the new location for the report file,
> as it does with the other *.rdl files I have. I do not see in the report
> code where a path is specified when the report opens and cannot directly
> edit the FullPath Property from the property window.
> Any ideas are welcome.
>

Report Formatting Differently on different servers with same RDL

This is a good one:

Same RDL, 2 different servers. I run the report on my computer and export to PDF, it prints properly. When the customer runs the report on their server (SSRS 2K5 SP1, same as mine), they get it displayed differently. The columns on the report extend to the next page and the lines are thicker.

Is this a formatting issue on the customer's PC? It uses standard fonts (Tahoma, Sans-serif).

Any ideas?

maybe you are using a matrix on the report and the customer has different data (more data) that makes the matrix extend?

lines are thicker? I can't think of anything there unless it is the fonts, but you look ok with that.

|||

No, it is not a matrix report. It is a standard layout table that is 10 inches wide, it's set for landscape with .5in margins.

|||I did some more research and started a new report from scratch and the same issue occurs.