Showing posts with label properly. Show all posts
Showing posts with label properly. Show all posts

Friday, March 30, 2012

Report parameter metadata not updated during deployment

In 2005, I've experienced a problem when re-deploying reports to the report server. The parameter references don't get updated properly and I would either need to re-deploy several times, or delete the reports and deploy a fresh copy. The latter re-creates the report GUIDs and messes up usage statistics. I've not been able to reproduce this consistently but have aexperienced it on several projects.

Is this issue being adressed in RS 2008?

I've run into this one as well.


I think this also occurred in SSRS 2000 as well.

|||The behavior around parameter metadata has not changed in Katmai. If you have a specific scenario where things get messed up, post a bug over on the connect site and we will take a look.|||

This is raised and explained in this post http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=100960&SiteID=1

I can't envisage parameter defaults and prompts being maintaned by an administrator. Does an override mechanism exist in RS 2005? If not, then will it be added in 2008?

Report parameter metadata not updated during deployment

In 2005, I've experienced a problem when re-deploying reports to the report server. The parameter references don't get updated properly and I would either need to re-deploy several times, or delete the reports and deploy a fresh copy. The latter re-creates the report GUIDs and messes up usage statistics. I've not been able to reproduce this consistently but have aexperienced it on several projects.

Is this issue being adressed in RS 2008?

I've run into this one as well.


I think this also occurred in SSRS 2000 as well.

|||The behavior around parameter metadata has not changed in Katmai. If you have a specific scenario where things get messed up, post a bug over on the connect site and we will take a look.|||

This is raised and explained in this post http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=100960&SiteID=1

I can't envisage parameter defaults and prompts being maintaned by an administrator. Does an override mechanism exist in RS 2005? If not, then will it be added in 2008?

Monday, March 26, 2012

Report not using pagination properly

I have a portrait report that has 1 table with 1 hidden group header (for the Page Header to reference fields from) and 36 detail rows. My problem is that pagination is not working properly. Depending on the length of data in the detail rows, the report tends to push majority of data on the next page(s) which leaves a lot of blank lines or blank page at the beginning of each group of data. I want the data to complete the first page before rolling over to the next page. That's why I have 36 individual detail rows instead of all the data in 1 detail row. I've tried adjusting the page length, but it doesn't seem to work all that well. I either get all the report on one page (which is fine when viewing online, but data is cut off when printing) or inadequate pagination. I do not have any white space at the bottom of the table and the page footer. Anyone have any ideas?

Thanks,

T

Have you tried setting KeepTogether=false on your table? The behavior your describing sounds like it's set to true, which would mean that if the table can't fit completely on the current page, but will fit on the next page, it will move the table to the next page.

You shouldn't need to specify the detail rows individually if you're populating from a data source!|||Yes, KeepTogether is false and yes I am using a shared data source and data is queried using Stored Procedure.|||Well it seems the problem lies within the Group Header row. I removed that row and pagination works properly now, but I lose the ability to call fields in my page header when the report spans more than one page.|||

Ok, I found a solution for showing Field values in Page Header even when the report spans more than one page(but you don't know at what point the report spans to the next page). It's a combination of several solutions:

1) Create hidden textbox(es) with the field value you're wanting on every line where the page might span to the next page.

textbox1

textbox2

textbox3

2) Create a function in code that will reference each hidden textbox(es) by name

Shared Function Header(reportItems as ReportItems) as string
Dim final as string
If ReportItems!textbox1.value <> "" Then
final = ReportItems!textbox1.value
Else If ReportItems!textbox2.value <> "" Then
final = ReportItems!textbox2.value
Else If ReportItems!textbox3.value <> "" Then
final = ReportItems!textbox3.value
End If
Return final
End Function

3) In Page Header call function, pass (ReportItems)

=Code.Header(ReportItems)

The reason for the function is because you can't reference multiple ReportItems in Page Header textbox, so you have to determine which hidden textbox has a value on that page and return that value to the calling Header textbox. Hope this helps....

sql

Report not rendering properly when passing prms in url

This has probably been answered before, but i cannot find the
solution.. I need to pass prms to a packlist report to pull the correct
packlist once a user is finished with a shipment in our logistics
software. Whenever i pass in the prms the report comes up, but there
are no graphics. I am also using neodynamics barcoding software and
those do not appear either.
Here is the url w/prms i am using :
http://sts-sqlsrv/ReportServer?/SCOUT+Reports/LOGISTICS/rptPacklist2&rc:Command=Render&rc:Format=HTML4.0&rc:Toolbar=True&PacklistId=060421001
Any ideas?
Thanks
JayDialDid you Deploy your graphics to the server as well?
Richard.
"JayDial" <JayDial@.gmail.com> wrote in message
news:1145889309.197930.223470@.e56g2000cwe.googlegroups.com...
> This has probably been answered before, but i cannot find the
> solution.. I need to pass prms to a packlist report to pull the correct
> packlist once a user is finished with a shipment in our logistics
> software. Whenever i pass in the prms the report comes up, but there
> are no graphics. I am also using neodynamics barcoding software and
> those do not appear either.
> Here is the url w/prms i am using :
> http://sts-sqlsrv/ReportServer?/SCOUT+Reports/LOGISTICS/rptPacklist2&rc:Command=Render&rc:Format=HTML4.0&rc:Toolbar=True&PacklistId=060421001
> Any ideas?
> Thanks
> JayDial
>|||The graphics display fine if i browse to the actual report, but not if
i provide the prms in the url.|||Next question is: does the report return a result set with the parms you've
specified? I'm thinking that if no rows are returned then your graphics may
not show up either. Does this work when you preview the report using those
parms?
Richard.
"JayDial" <JayDial@.gmail.com> wrote in message
news:1145892373.787538.120860@.y43g2000cwc.googlegroups.com...
> The graphics display fine if i browse to the actual report, but not if
> i provide the prms in the url.
>|||Hrmm, that is the strangest thing. Today i was getting a couple screen
shots for you, but now the graphics are showing up. I thought maybe it
was a problem with the original url I was using, but when i copy and
paste from the original post everything is to be expected! Thanks for
your help!
-JayDial

Tuesday, February 21, 2012

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.