Showing posts with label header. Show all posts
Showing posts with label header. Show all posts

Monday, March 26, 2012

ReportViewer -- how to translate header values

Hi Everyone,

Can anyone tell me how to use my resx files to translate the header and footer values in a ReportViewer Report (rdlc file)? I'm missing something here!

Thanks,

jekerry

Hi, jekerry:

Do you need to localize the Reports in the Reporting service. If so, i just recommend you to use this following tech to achieve this:

As localization is not a built-in feature for Reporting Services, people have tried a a variety of techniques for localizing reports. One technique is to use the LocID propertie to create a version of the RDL in each language. Another approach is to have a single report and create a custom assembly to load the strings for each label. Here is an relatively easy technique for providing localized reports using hidden parameters.

First, you will need to create a table to hold the translations. The following T-SQL will create the table and add a few labels for translating the Product Line Sales sample that is included with the product.

http://blogs.msdn.com/bwelcker/archive/2007/07/11/laser-guided-missiles-report-localization-through-parameters.aspx

http://blogs.msdn.com/bimusings/archive/2007/01/11/happiness-is-automatic-sql-reporting-services-localization.aspx


If i misunderstand you about your question, please feel free to correct me and i will try to help you with more information.

I hope the above information will be helpful. If you have any issues or concerns, please let me know. It's my pleasure to be of assistance

This response contains a reference to a third party World Wide Web site. Microsoft is providing this information as a convenience to you. Microsoft does not control these sites and has not tested any software or information found on these sites; therefore, Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. There are inherent dangers in the use of any software found on the Internet, and Microsoft cautions you to make sure that you completely understand the risk before retrieving any software from the Internet.

|||

Thank you so much! How depressing!!! Why would they add a new control without localization support?? I am very depressed. That is a very ugly work around. Maybe I will look into Crystal Reports.

thanks,

jekerry

|||

Woo hoo! I found a way to use my resx files!!!!!!!!!!!!!!!!!! I can now change the column headers automatically to any language. Very cool. Just add a second datatable, fill it with the header values, and reference them.

One problem solved!

jekerry

Friday, March 23, 2012

ReportServer Service Is Filling Up Log Files

I saw this header from back in April, but it has since been expired from
Microsoft's news server. Anywho, for some reason, my trace log file for the
ReportingServices Service is filling up at about 1 Mb per minute. I have dropped
the trace level down to 2 for now, but this does not fix the core issue. It
seems that the "Execution Log Entry Expiration" task, or whatever it is, is
running and will not stop, thus generating tons of trace log entries. Can
somebody please help with this?
Here is the warning message:
ReportingServicesService!runningjobs!22c8!6/22/2005-09:15:09:: w WARN: Previous
request for Execution Log Entry Expirationstill executing, skipping...
Here is the info message:
ReportingServicesService!dbcleanup!1a4c!6/22/2005-10:06:03:: i INFO: Expiring
old execution log entries
ReportingServicesService!dbcleanup!1a4c!6/22/2005-10:06:03:: i INFO: Expiration
of old execution log entries is complete. Removed 0 entries.
ReportingServicesService!dbcleanup!1a4c!6/22/2005-10:06:03:: i INFO: Cleaned 0
broken snapshots, 0 chunks
ReportingServicesService!runningjobs!1a4c!6/22/2005-10:06:03:: i INFO: Execution
Log Entry Expiration timer enabled: Cycle: 57236 seconds
Also, is there any way to change the location of the trace log files?This is fixed in SP2. There's also a hotfix available if you need to stay on
SP1 for some reason. What I used to do is just have a scheduled task that
ran a vbscript to delete the older log files if the size of the log folder >
300 MB
--
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Darrell" <Darrell.Wright.nospam@.okc.gov> wrote in message
news:u7aJg5zdFHA.688@.TK2MSFTNGP14.phx.gbl...
>I saw this header from back in April, but it has since been expired from
>Microsoft's news server. Anywho, for some reason, my trace log file for the
>ReportingServices Service is filling up at about 1 Mb per minute. I have
>dropped the trace level down to 2 for now, but this does not fix the core
>issue. It seems that the "Execution Log Entry Expiration" task, or whatever
>it is, is running and will not stop, thus generating tons of trace log
>entries. Can somebody please help with this?
> Here is the warning message:
> ReportingServicesService!runningjobs!22c8!6/22/2005-09:15:09:: w WARN:
> Previous request for Execution Log Entry Expirationstill executing,
> skipping...
> Here is the info message:
> ReportingServicesService!dbcleanup!1a4c!6/22/2005-10:06:03:: i INFO:
> Expiring old execution log entries
> ReportingServicesService!dbcleanup!1a4c!6/22/2005-10:06:03:: i INFO:
> Expiration of old execution log entries is complete. Removed 0 entries.
> ReportingServicesService!dbcleanup!1a4c!6/22/2005-10:06:03:: i INFO:
> Cleaned 0 broken snapshots, 0 chunks
> ReportingServicesService!runningjobs!1a4c!6/22/2005-10:06:03:: i INFO:
> Execution Log Entry Expiration timer enabled: Cycle: 57236 seconds
> Also, is there any way to change the location of the trace log files?

Friday, March 9, 2012

ReportOnNewPage not working as expected.

I have a simple reporting services 2005 report with just a body section which
contains a table control with the following rows
table header (RepeatOnNewPage = false)
group header (RepeatOnNewPage = true)
detail
group footer (RepeatOnNewPage = false)
table footer (RepeatOnNewPage = false)
The header & footer sections just have some text in them to describe what
they are i.e. table header has text "Table Header", group header has "Group
Header" etc.
The detail section shows 3 fields quote number, line & notes.
When I preview the report (from Visual Studio in Print Layout mode or from
report managed & export the report to pdf) and there is so much data in the
notes field for a specific line that is causes a page break within the detail
section, no group header is shown on the next page. The group header is
correctly displayed on any subsequent pages.
It only seems to be a problem when the data within the detail section causes
a page break, if a "natural" page break occurs at the end of a detail, it
correctly shows the group header on the next page.
I really need a solution/workaround for this asap as this is a simplified
version of a customers quote report - we are upgrading their Microsoft CRM
system over the weekend from 1.2 (which used Crystal Reports) to CRM 3 (which
uses SRS) and this report is vital to their operation.
Thanks in advance for any advice
Regards
AndyThink I should have entitled the posting "RepeatOnNewPage"!!
"AndyG" wrote:
> I have a simple reporting services 2005 report with just a body section which
> contains a table control with the following rows
> table header (RepeatOnNewPage = false)
> group header (RepeatOnNewPage = true)
> detail
> group footer (RepeatOnNewPage = false)
> table footer (RepeatOnNewPage = false)
>
> The header & footer sections just have some text in them to describe what
> they are i.e. table header has text "Table Header", group header has "Group
> Header" etc.
> The detail section shows 3 fields quote number, line & notes.
> When I preview the report (from Visual Studio in Print Layout mode or from
> report managed & export the report to pdf) and there is so much data in the
> notes field for a specific line that is causes a page break within the detail
> section, no group header is shown on the next page. The group header is
> correctly displayed on any subsequent pages.
> It only seems to be a problem when the data within the detail section causes
> a page break, if a "natural" page break occurs at the end of a detail, it
> correctly shows the group header on the next page.
> I really need a solution/workaround for this asap as this is a simplified
> version of a customers quote report - we are upgrading their Microsoft CRM
> system over the weekend from 1.2 (which used Crystal Reports) to CRM 3 (which
> uses SRS) and this report is vital to their operation.
> Thanks in advance for any advice
> Regards
> Andy
>

ReportItems in Page Header while using SubReport

Hey all,

Well here's the problem I am facing at the moment. I have a report that has a couple subreports along with it. I have one main page header in the main report. I reference a ReportItem from the main report in the Page header in order to display that item in the page header. However, when a subreport takes up an entire page I lose reference to that ReportItem in order for the page header to be displayed. Does anyone have any idea on how to reference a reportitem in a subreport or how to get a workaround in order to get this pageheader to be displayed all the time. I would greatly appreciate it.

Mickas

Hi.

Same problem here ! Happy to find an entry for this problem, so I'm knowing it's not a problem only of my system :-)

Pls. Help
Malte

ReportItems in Page Header

I've added a hidden field to my report so I can show the value in the page header using ReportItems. However it only works for the first page - the value is blank on subsequent pages. Does the hidden field need to appear on all pages of the report? Would I need to make it a hidden field in a repeated list or table?Yes, the hidden field needs to be on all pages. You can either put it inside the table header and make the header repeat on every page. Or put it outside of the dataregion, and check the "repeat report item with data region on every page" box to make it repeat with the list or table.|||

Greame

One trick I learn is that instead of using the hidden field for report header. I created a parameter and then selected "Internal" to be used only with the report. You can parameter in the page header.

Hammer

|||

Hammer,

That may work if you only have one row in a dataset, but if you have more than one row, it only captures the first value in the dataset.

|||

N,

Yes, that correct, but anything in the header is mostly static and a single row works perfectly.

Ham

|||

Hello All,

How do I ENABLE the Repeat report item with data region on every page property. please help.

|||Right click on the textbox and bring up the properties dialog, under the Tooltip box, there is the "Repeat report item" checkbox. Make sure that's checked, and pick a data region in the dropdown list.|||

I still cannot get this to work. I've created the hidden field outside of the table data region and told it to repeat with the table, but it still only appears on page one. What could I be doing wrong?

Just tried putting it in table header too. This works but not if the column is hidden - I need to make it visible but set width to minimum which appears to be 0.07937cm. Is this the correct method?

|||

Same problem here. The RepeatWith even tough it is set to the Date Region, isn't repeated at all

|||Hi there !

Has anybody found an answer ? .. I have the same problem here.

In my report, i'm filling the header fields through my datafield in the reportbody. But:

I found out, that it's important, where the datasetfield is located in the body. in my case: if it's located before of the subreport, the headerfield is only filled out on the first page - if it's located after the subreport, only the last page header field will be filled.

Pls. help.

ReportItems in Page Header

I've added a hidden field to my report so I can show the value in the page header using ReportItems. However it only works for the first page - the value is blank on subsequent pages. Does the hidden field need to appear on all pages of the report? Would I need to make it a hidden field in a repeated list or table?Yes, the hidden field needs to be on all pages. You can either put it inside the table header and make the header repeat on every page. Or put it outside of the dataregion, and check the "repeat report item with data region on every page" box to make it repeat with the list or table.|||

Greame

One trick I learn is that instead of using the hidden field for report header. I created a parameter and then selected "Internal" to be used only with the report. You can parameter in the page header.

Hammer

|||

Hammer,

That may work if you only have one row in a dataset, but if you have more than one row, it only captures the first value in the dataset.

|||

N,

Yes, that correct, but anything in the header is mostly static and a single row works perfectly.

Ham

|||

Hello All,

How do I ENABLE the Repeat report item with data region on every page property. please help.

|||Right click on the textbox and bring up the properties dialog, under the Tooltip box, there is the "Repeat report item" checkbox. Make sure that's checked, and pick a data region in the dropdown list.|||

I still cannot get this to work. I've created the hidden field outside of the table data region and told it to repeat with the table, but it still only appears on page one. What could I be doing wrong?

Just tried putting it in table header too. This works but not if the column is hidden - I need to make it visible but set width to minimum which appears to be 0.07937cm. Is this the correct method?

|||

Same problem here. The RepeatWith even tough it is set to the Date Region, isn't repeated at all

ReportItems in Header/Footer

Hi there,
probably the most common problem with srs: how to insert data fields in page
header or footer?
The described workaround to reference ReportItems in the body does not work
for me, don´t know why.
Here is what I did:
I have a footer that must display fields from a query.
I placed a textbox named textbox1 in the body with a value of
=First(Fields!Field123.Value
I added a textbox in the footer with a value of =ReportItems!textbox1
When I render the report the textbox in the body contains the data as
expected, but the textbox in the footer is just empty. No Errors, no
warnings!
I use SQL2000 SP4 with Reporting Services SP2.
Any suggestions are highly appreciated :)
greetinx,
Joerg KrummTry:
=ReportItems!textbox1.value
"Jörg Krumm" <jeykey-news@.justmail.de> wrote in message
news:e5MI%23WiCHHA.4016@.TK2MSFTNGP02.phx.gbl...
> Hi there,
> probably the most common problem with srs: how to insert data fields in
> page header or footer?
> The described workaround to reference ReportItems in the body does not
> work for me, don´t know why.
> Here is what I did:
> I have a footer that must display fields from a query.
> I placed a textbox named textbox1 in the body with a value of
> =First(Fields!Field123.Value
> I added a textbox in the footer with a value of =ReportItems!textbox1
> When I render the report the textbox in the body contains the data as
> expected, but the textbox in the footer is just empty. No Errors, no
> warnings!
> I use SQL2000 SP4 with Reporting Services SP2.
> Any suggestions are highly appreciated :)
> greetinx,
> Joerg Krumm
>|||Hi Chris,
thanks for your hint. I do have a value of =ReportItems!textbox1.value . I
just made a mistake in the posting :)
Joerg
"Chris Conner" <Chris.Conner@.NOSPAMPolarisLibrary.com> schrieb im
Newsbeitrag news:%23fEyGglCHHA.3476@.TK2MSFTNGP04.phx.gbl...
> Try:
> =ReportItems!textbox1.value
>
> "Jörg Krumm" <jeykey-news@.justmail.de> wrote in message
> news:e5MI%23WiCHHA.4016@.TK2MSFTNGP02.phx.gbl...
>> Hi there,
>> probably the most common problem with srs: how to insert data fields in
>> page header or footer?
>> The described workaround to reference ReportItems in the body does not
>> work for me, don´t know why.
>> Here is what I did:
>> I have a footer that must display fields from a query.
>> I placed a textbox named textbox1 in the body with a value of
>> =First(Fields!Field123.Value
>> I added a textbox in the footer with a value of =ReportItems!textbox1
>> When I render the report the textbox in the body contains the data as
>> expected, but the textbox in the footer is just empty. No Errors, no
>> warnings!
>> I use SQL2000 SP4 with Reporting Services SP2.
>> Any suggestions are highly appreciated :)
>> greetinx,
>> Joerg Krumm
>|||You could create a report parameter, probably internal, and have its value be
the data field. Then you can put that parameter in the header.
Carmine
"Jörg Krumm" wrote:
> Hi Chris,
> thanks for your hint. I do have a value of =ReportItems!textbox1.value . I
> just made a mistake in the posting :)
> Joerg
> "Chris Conner" <Chris.Conner@.NOSPAMPolarisLibrary.com> schrieb im
> Newsbeitrag news:%23fEyGglCHHA.3476@.TK2MSFTNGP04.phx.gbl...
> > Try:
> > =ReportItems!textbox1.value
> >
> >
> > "Jörg Krumm" <jeykey-news@.justmail.de> wrote in message
> > news:e5MI%23WiCHHA.4016@.TK2MSFTNGP02.phx.gbl...
> >> Hi there,
> >>
> >> probably the most common problem with srs: how to insert data fields in
> >> page header or footer?
> >>
> >> The described workaround to reference ReportItems in the body does not
> >> work for me, don´t know why.
> >>
> >> Here is what I did:
> >>
> >> I have a footer that must display fields from a query.
> >> I placed a textbox named textbox1 in the body with a value of
> >> =First(Fields!Field123.Value
> >> I added a textbox in the footer with a value of =ReportItems!textbox1
> >>
> >> When I render the report the textbox in the body contains the data as
> >> expected, but the textbox in the footer is just empty. No Errors, no
> >> warnings!
> >>
> >> I use SQL2000 SP4 with Reporting Services SP2.
> >>
> >> Any suggestions are highly appreciated :)
> >>
> >> greetinx,
> >>
> >> Joerg Krumm
> >>
> >
> >
>
>

ReportItems in header page?

Will be enable this functionality for SSRS2008 ?

Certain report items such as textbox and image were always allowed in the report header. There are some limitations, though. For example, data regions and formulas that reference dataset fields are not allowed. This will be the same in SQL Server 2008 Reporting Services as it was in previous versions.

Best regards,
Chris

ReportItems does not repeat

Here is the scanerio. A hidden textbox in the body of the report is being refered in the report header using ReportItems. But the it does not repeat on all pages. It just showed up on the very first page.

Any Ideas?

Never mind. I found a work around!|||

The hidden textbox must appear on every page too.

Try to put it into a table header that appears on every page, for instance.

Was this your workaround?

ReportItems data value displays in first page header only

I am using ReportItems in the header of a report to reference the data field
for the id of the report (based on a request in our application that
represents the value of the call_id field). This value only displays on the
first page of the report - no subsequent pages. Often the data in other
fields can be quite large (20 to 100 pages when rendered in PDF).
It is because the header is "looking" for that field value on every page -
and it only appears towards the top of the report. I verified this by moving
the data field to the bottom of the report - and then the value only appears
on the last page of the report.
I want this data to appear in the header of every page.
I have tried the following in the header:
=First(ReportItems!callid.value)
=ReportItems!callid.value
Any ideas?
Thanks for your help.
CoryMove the item into the body of the report and it should work...using First()
--
Wayne Snyder MCDBA, SQL Server MVP
Mariner, Charlotte, NC
(Please respond only to the newsgroup.)
I support the Professional Association for SQL Server ( PASS) and it's
community of SQL Professionals.
"Cory" <Cory@.discussions.microsoft.com> wrote in message
news:BD7AD9E4-F18D-4136-AFBC-CBB37FD221CF@.microsoft.com...
>I am using ReportItems in the header of a report to reference the data
>field
> for the id of the report (based on a request in our application that
> represents the value of the call_id field). This value only displays on
> the
> first page of the report - no subsequent pages. Often the data in other
> fields can be quite large (20 to 100 pages when rendered in PDF).
> It is because the header is "looking" for that field value on every page -
> and it only appears towards the top of the report. I verified this by
> moving
> the data field to the bottom of the report - and then the value only
> appears
> on the last page of the report.
> I want this data to appear in the header of every page.
> I have tried the following in the header:
> =First(ReportItems!callid.value)
> =ReportItems!callid.value
> Any ideas?
> Thanks for your help.
> Cory
>|||Wayne, just sent you an email. Not sure how often you check your email.
Check it out when you have a chance.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Wayne Snyder" <wayne.nospam.snyder@.mariner-usa.com> wrote in message
news:e5GNpSvjFHA.3144@.TK2MSFTNGP12.phx.gbl...
> Move the item into the body of the report and it should work...using
> First()
> --
> Wayne Snyder MCDBA, SQL Server MVP
> Mariner, Charlotte, NC
> (Please respond only to the newsgroup.)
> I support the Professional Association for SQL Server ( PASS) and it's
> community of SQL Professionals.
> "Cory" <Cory@.discussions.microsoft.com> wrote in message
> news:BD7AD9E4-F18D-4136-AFBC-CBB37FD221CF@.microsoft.com...
>>I am using ReportItems in the header of a report to reference the data
>>field
>> for the id of the report (based on a request in our application that
>> represents the value of the call_id field). This value only displays on
>> the
>> first page of the report - no subsequent pages. Often the data in other
>> fields can be quite large (20 to 100 pages when rendered in PDF).
>> It is because the header is "looking" for that field value on every
>> page -
>> and it only appears towards the top of the report. I verified this by
>> moving
>> the data field to the bottom of the report - and then the value only
>> appears
>> on the last page of the report.
>> I want this data to appear in the header of every page.
>> I have tried the following in the header:
>> =First(ReportItems!callid.value)
>> =ReportItems!callid.value
>> Any ideas?
>> Thanks for your help.
>> Cory
>|||Hi Wayne,
That is what I have - The item that is being referenced is in the body of
the report - and uses first to retrieve the data from the database... and the
reportitems reference in the header I've tried both first and no prefix...
But the reportitems reference in the header only appears on the same page
that the item being referenced appears.
So, if I have the body item on the 5th page then the header displays the
value on the 5th page. If on the 20th page then it will appear there and so
on.
Thanks again for your help.
--Cory
"Wayne Snyder" wrote:
> Move the item into the body of the report and it should work...using First()
> --
> Wayne Snyder MCDBA, SQL Server MVP
> Mariner, Charlotte, NC
> (Please respond only to the newsgroup.)
> I support the Professional Association for SQL Server ( PASS) and it's
> community of SQL Professionals.
> "Cory" <Cory@.discussions.microsoft.com> wrote in message
> news:BD7AD9E4-F18D-4136-AFBC-CBB37FD221CF@.microsoft.com...
> >I am using ReportItems in the header of a report to reference the data
> >field
> > for the id of the report (based on a request in our application that
> > represents the value of the call_id field). This value only displays on
> > the
> > first page of the report - no subsequent pages. Often the data in other
> > fields can be quite large (20 to 100 pages when rendered in PDF).
> >
> > It is because the header is "looking" for that field value on every page -
> > and it only appears towards the top of the report. I verified this by
> > moving
> > the data field to the bottom of the report - and then the value only
> > appears
> > on the last page of the report.
> >
> > I want this data to appear in the header of every page.
> >
> > I have tried the following in the header:
> > =First(ReportItems!callid.value)
> > =ReportItems!callid.value
> >
> > Any ideas?
> >
> > Thanks for your help.
> >
> > Cory
> >
>
>|||Hi Cory,
I have the same problem, can you please help me if you got the solution.
Thanks in advance.
"Cory" wrote:
> I am using ReportItems in the header of a report to reference the data field
> for the id of the report (based on a request in our application that
> represents the value of the call_id field). This value only displays on the
> first page of the report - no subsequent pages. Often the data in other
> fields can be quite large (20 to 100 pages when rendered in PDF).
> It is because the header is "looking" for that field value on every page -
> and it only appears towards the top of the report. I verified this by moving
> the data field to the bottom of the report - and then the value only appears
> on the last page of the report.
> I want this data to appear in the header of every page.
> I have tried the following in the header:
> =First(ReportItems!callid.value)
> =ReportItems!callid.value
> Any ideas?
> Thanks for your help.
> Cory
>|||Hi. No unfortunately nobody did respond with a really helpful suggestion.
However, I did find something elsewhere where someone suggested grabbing the
value and then setting it as a report parameter which supposedly can be
displayed on every page.
I haven't yet had time to test it though... as I've been pulled in a
different direction.
If you should happen to find something - or if someone else has a good
suggestion I'd love to hear it!
Thanks.
--Cory
"Anitha Naidu" wrote:
> Hi Cory,
> I have the same problem, can you please help me if you got the solution.
> Thanks in advance.
>
>
> "Cory" wrote:
> > I am using ReportItems in the header of a report to reference the data field
> > for the id of the report (based on a request in our application that
> > represents the value of the call_id field). This value only displays on the
> > first page of the report - no subsequent pages. Often the data in other
> > fields can be quite large (20 to 100 pages when rendered in PDF).
> >
> > It is because the header is "looking" for that field value on every page -
> > and it only appears towards the top of the report. I verified this by moving
> > the data field to the bottom of the report - and then the value only appears
> > on the last page of the report.
> >
> > I want this data to appear in the header of every page.
> >
> > I have tried the following in the header:
> > =First(ReportItems!callid.value)
> > =ReportItems!callid.value
> >
> > Any ideas?
> >
> > Thanks for your help.
> >
> > Cory
> >

Wednesday, March 7, 2012

ReportItem values are not printing in header

I am using the following inorder to get dataset fields into my header:
=First(ReportItems("EmpName").Value)
The data is returned when I run the report and I can see the values when a
client runs it to their screen. But when I go to print or print-preview the
data in the header is not there (all the data in the report is ok).
--
Systems AnalystTry =ReportItems!EmpName.Value
"schmidtkaren" wrote:
> I am using the following inorder to get dataset fields into my header:
> =First(ReportItems("EmpName").Value)
> The data is returned when I run the report and I can see the values when a
> client runs it to their screen. But when I go to print or print-preview the
> data in the header is not there (all the data in the report is ok).
> --
> Systems Analyst

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