[Solved] Report Header contents not showing on all pages when it contains a list

[JGirl]

Hi.

Due to the problems with attempting to format date parameters for display in a report header, I have created a query (that only ever returns one row) that has the to and the from dates as data items.Ã,  ie. data item "ToDate" = cast(?parm_ToDate?,date), and the data item "FromDate" = cast(?parm_FromDate?,date).

In the header of my report, i have a 2 x 2 table, with the first column containing the filter description (eg. "First Payment Date to Include = "), and the second column in the table containing a list in each cell with one column and headers etc hidden, so that the 'FoDate" is displayed in one list, and the "FromDate" is displayed in the next list.

This works and displays fine when the report is a one page report.Ã,  However, as soon as the report is multiple pages, only the first page's header contains the actual date values.

How can i force these values to display on every page whilst maintaining the type of display I have now (ie. I dont want suggestions that recommend I use "ParamDisplayValue" instead of using the lists.....)

I've attached an XML report spec that uses the 'GO Sales and Retailers' package to demonstrate the problem.

J

[BIsrik]

i have not seen what u have done...but going with ur requirement i m doing the same by associating the page to that query. On doing so i am able to drag the data item to the header section. It does get repeated for every page...

Srik

[JoeBass]

Hi JGirl, have you tried a list header?Ã,  Ã, 

[bdybldr]

JGirl,
The easiest fix for this is to select the list column of your table and select the ancestor on the properties bar.  Then select the list.

Go to the Pagination property and check the box beside "Repeat on every page".

This should solve the problem.

[mikegreen]

How can i force these values to display on every page whilst maintaining the type of display I have now (ie. I dont want suggestions that recommend I use "ParamDisplayValue" instead of using the lists.....)

Curious..... Why can't you use this type of solution?  We use it for some of our reports with success... ?

Cheers,

Mike

[bdybldr]

You can't easily apply formats to the ParamDisplayValue.

[JGirl]

bdybldr, i'll have to try your suggestion out when I get back to work....but it sounds promising!

I need to use the list to display the parameter values because the parameters are being passed in a drill through.  Basically i prompt for a date on the first level report, and drill though to a second report by clicking on the area name.  In my child report, while I want to obviously filter by the area name, I also want to pass the date values that were selected.  The date parameters are passed to the child report, but in the child report if I attempt to use paramdisplay value in the header, it (annoyingly) display the value as a datetime (even though i've selected a date prompt), which I don't want.....which is why my list data item for the header is cast(parametername,date).

J

[JGirl]

perfect - exactly what I was looking for.

applause for bdybldr   :)

Thankyou!

[JoeBass]

I don't have a pagination property available for tables.  I do for lists but, your example report had a table in the header?  Can you clarify for me how you got this to work?  Thanks.  We use mr2. 

[bdybldr]

You're right, Joe.  The report did contain a table but the table contains a list.  The pagination property was set for the list within the table.  You can make the list look like a ParamDisplayValue by hiding the boorders and column titles, ect.  You can't even tell the difference when the report is rendered.

[JoeBass]

Ahh, thanks bdy

[bdybldr]

Thanks JGirl...much appreciated!!