ReportItem dont function in divided Pages

Hello
On my header I need the Employee-Name (ReportItem!EmployeeFullName.Value),
so i put in a ReportItem that refer to a Field
(Fields!EmployeeFullName.Value) in the body.
It functions as long as the page wont be divided.
When the report is too long and it will be divided, the header will be
printed an other time but the refered field
(ReportItem!EmployeeFullName.Value) is empty.
Do you have an other way to read Data in the header?
thx a lot
Ciao MicheleNote to my first post:
The refered field filled in the first page and beginning from the second
page it is empty.
ciao Michele
"Michele" wrote:
> Hello
> On my header I need the Employee-Name (ReportItem!EmployeeFullName.Value),
> so i put in a ReportItem that refer to a Field
> (Fields!EmployeeFullName.Value) in the body.
> It functions as long as the page wont be divided.
> When the report is too long and it will be divided, the header will be
> printed an other time but the refered field
> (ReportItem!EmployeeFullName.Value) is empty.
> Do you have an other way to read Data in the header?
> thx a lot
> Ciao Michele|||Where are you placing the referred field? For example, if you reference a
field in the header, and that field does not appear on a page, the header
will not display any data. If you are using a table, place the field in the
table header, and repeat the header on each page. As long as you can get the
field in the body which contains the Employee Name to be on each page, your
header should work. Hope this helps.
David
"Michele" wrote:
> Note to my first post:
> The refered field filled in the first page and beginning from the second
> page it is empty.
> ciao Michele
> "Michele" wrote:
> > Hello
> >
> > On my header I need the Employee-Name (ReportItem!EmployeeFullName.Value),
> > so i put in a ReportItem that refer to a Field
> > (Fields!EmployeeFullName.Value) in the body.
> > It functions as long as the page wont be divided.
> > When the report is too long and it will be divided, the header will be
> > printed an other time but the refered field
> > (ReportItem!EmployeeFullName.Value) is empty.
> >
> > Do you have an other way to read Data in the header?
> >
> > thx a lot
> > Ciao Michele|||This is a limitation of Reporting Services that I've heard *they* will fix
one day. Here is a suggested workaround that I use successfully:
Make an arbitrary group on your table, one that never breaks, or use the
header that breaks on your employee, if that's how you've set up your
report. In any case you need a Group Header row on your table that you can
"hide" by setting the Visibility | Hidden property to "True". This is the
best place to put the field you need to refer to in the Header--this fakes
out Reporting Services so it knows exactly which field value is needed
regardless of the report division.
On that hidden Header row place the field you need to refer to. It's
Visibility | Hidden property should be "False".
THEN you can refer to the textbox that contains the VALUE of the field you
need in your header. Like this:
Group Header Row: groupheaderEN.Value is filled with
=Fields!employeeName.Value
Page Header: pageheaderEN.Value is filled with
=ReportItems!groupheaderEN.Value
After playing with this and being sure your data appears as you wish, then
you can squeeze the unneeded Group Header field down to nothing so it won't
take up space when it prints.
--
Message posted via http://www.sqlmonster.com|||Hei, thx a lot!
I will try both variants and will you let know if it functions ;)
ciao Michele
"Sandra Lewis via SQLMonster.com" wrote:
> This is a limitation of Reporting Services that I've heard *they* will fix
> one day. Here is a suggested workaround that I use successfully:
> Make an arbitrary group on your table, one that never breaks, or use the
> header that breaks on your employee, if that's how you've set up your
> report. In any case you need a Group Header row on your table that you can
> "hide" by setting the Visibility | Hidden property to "True". This is the
> best place to put the field you need to refer to in the Header--this fakes
> out Reporting Services so it knows exactly which field value is needed
> regardless of the report division.
> On that hidden Header row place the field you need to refer to. It's
> Visibility | Hidden property should be "False".
> THEN you can refer to the textbox that contains the VALUE of the field you
> need in your header. Like this:
> Group Header Row: groupheaderEN.Value is filled with
> =Fields!employeeName.Value
> Page Header: pageheaderEN.Value is filled with
> =ReportItems!groupheaderEN.Value
> After playing with this and being sure your data appears as you wish, then
> you can squeeze the unneeded Group Header field down to nothing so it won't
> take up space when it prints.
> --
> Message posted via http://www.sqlmonster.com
>|||Another question: how do you make a group on the table, one that never breaks?
thx, michele
"Sandra Lewis via SQLMonster.com" wrote:
> This is a limitation of Reporting Services that I've heard *they* will fix
> one day. Here is a suggested workaround that I use successfully:
> Make an arbitrary group on your table, one that never breaks, or use the
> header that breaks on your employee, if that's how you've set up your
> report. In any case you need a Group Header row on your table that you can
> "hide" by setting the Visibility | Hidden property to "True". This is the
> best place to put the field you need to refer to in the Header--this fakes
> out Reporting Services so it knows exactly which field value is needed
> regardless of the report division.
> On that hidden Header row place the field you need to refer to. It's
> Visibility | Hidden property should be "False".
> THEN you can refer to the textbox that contains the VALUE of the field you
> need in your header. Like this:
> Group Header Row: groupheaderEN.Value is filled with
> =Fields!employeeName.Value
> Page Header: pageheaderEN.Value is filled with
> =ReportItems!groupheaderEN.Value
> After playing with this and being sure your data appears as you wish, then
> you can squeeze the unneeded Group Header field down to nothing so it won't
> take up space when it prints.
> --
> Message posted via http://www.sqlmonster.com
>|||The field with the data is a hidden filed on the body.
The refence-field is a field in the header.
So if the report has a lot of data it breaks automatically in 2 pages.
On the second page the header will be printed again, BUT the hidden field
(on the body) hasnt any data, cause the pagebreake happens after the print of
this hidden field.
"David Siebert" wrote:
> Where are you placing the referred field? For example, if you reference a
> field in the header, and that field does not appear on a page, the header
> will not display any data. If you are using a table, place the field in the
> table header, and repeat the header on each page. As long as you can get the
> field in the body which contains the Employee Name to be on each page, your
> header should work. Hope this helps.
> David
> "Michele" wrote:
> > Note to my first post:
> > The refered field filled in the first page and beginning from the second
> > page it is empty.
> >
> > ciao Michele
> >
> > "Michele" wrote:
> >
> > > Hello
> > >
> > > On my header I need the Employee-Name (ReportItem!EmployeeFullName.Value),
> > > so i put in a ReportItem that refer to a Field
> > > (Fields!EmployeeFullName.Value) in the body.
> > > It functions as long as the page wont be divided.
> > > When the report is too long and it will be divided, the header will be
> > > printed an other time but the refered field
> > > (ReportItem!EmployeeFullName.Value) is empty.
> > >
> > > Do you have an other way to read Data in the header?
> > >
> > > thx a lot
> > > Ciao Michele|||Here you have a sample of how the report is structured and what happens after
a pagebreak.
thx a lot, Michele
____________________________________________________
|___________________________________________________| Header; Titel
____________________________________________________
|___________ReferItem!EmployeeName.Value___(functions)__| Header; Nam
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
____________________________________________________
|_________(hidden) Fields!EmployeeName.Value___________| Body; Table 1
____________________________________________________
|___________________________________________________| Body; Table 2
____________________________________________________
|___________________________________________________| Body; Table 3
@.@.@.@.@.@.@.@.@.@.@.@.@.@.@.@.@.@.@.@.@.@.@.@.@.@.@.@.@.@.@.@.@.@.@.@.@.@.@.
automatic pagebreake because there are a lot of data
____________________________________________________
|___________________________________________________| Header; Titel
___________________________________________________
|_____ReferItem!EmployeeName.Value__(doesnt function)___| Header; Nam
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
____________________________________________________
|___________________________________________________| Body; Table
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
____________________________________________________
|___________________________________________________| Footer