显示标签为“variety”的博文。显示所有博文
显示标签为“variety”的博文。显示所有博文

2012年3月20日星期二

Any way to make a "Page Footer Only For The First Page"

I am unclear if SSRS can handle this. We are using SSRS 2005 for a variety of things for a billing system; one of them being actual bill generation. The bills are generally one page long, but in rare exceptions can be multiplie pages. They end up being printed onto perforated paper at around the 8 inch mark, and we basically want to put a page footer there that is the "bill stub"... a section that summarizes the bill that they rip off and return with payment.

So, I guess the general problem is that I have a want to put a section of content at a specific place at the bottom of one and only one page (the first page would be preferrable, but the last page is also acceptable), in the middle of a report that has a table of bill line items of an indeterminate height.

I went down paths of looking at PageFooter, since it is generally the idea I am after, but I can't find a way to only show it on one page... on a 4 page bill, it always wants to print on page 2 AND 3 no matter what I do.

Thanks for any help that you can provide.

Michael

The only option supported is to print the footer on first or last page of the report (PrintOnFirstPage and PrintOnLastPage property respectively of the page footer band). Please note that currently RS (2000 and 2005) doesn't allow you to reclaim the space occupied in subsequent pages if the header/footer is not printed.|||

Just pinging this thread to see if anyone has a good workaround for this type of issue. I'm trying to use SSRS 2005 for creating invoices (currently using Crystal Reports). I have specific text (also includes data from the dataset) that has to be on a specific section of the LAST page of the invoice (can be 1 or multiple pages). This is done in Crystal by creating a second PAGE FOOTER that's suppressed on every page except the last one. This issues (along with not being to keep table groups together) are causing so much difficulty in creating reports. It's hard to believe this product is missing so many basic functions. Typical MSFT in throwing something out there that gets you 80-90% of what you need. Do they even try real world situations like the basic necessity of having an invoice, bill, etc.

|||

I don't think there is any way to suppress the whole Page Footer section. What you can try doing is giving a conditional visibility expression for the textbox that you have in your Page Footer.

For example if you want the text to shown only on the 1st page then the expression =IIf(Globals!PageNumber=1,false,true)

and if you want it only on the last page then =IIf(Globals!PageNumber=Globals!TotalPages,false,true) can be used.

Hope it helps,

Aayush

|||

I've already gone the expression route. I have a rectangle with a bunch of text boxes in it. I hide the rectangle on everypage but the last (IIf(Globals!PageNumber=Globals!TotalPages,false,true) ).

That works when displaying in the browser. However, when printing or exporting to pdf the "white space" where the rectangle is shows up on every page. I need it suppressed. This is an invoice so not being able to print it or export it to pdf to be emailed is pointless.

|||

Hi,

I tried to copy and paste the condition for only displaying on last page IIf(Globals!PageNumber=Globals!TotalPages,false,true) but it doesn't seem to be working and I am getting an error ") is missing" and it highlights "Globals" (first one).

Am I doing something wrong? Please advice. Thanks for your help

Nabil

|||Looks correct to me. Sounds silly but I hope your expression starts with the '=' symbol, that is, =IIf(Globals!PageNumber=Globals!TotalPages,false,true)

Any way to make a "Page Footer Only For The First Page"

I am unclear if SSRS can handle this. We are using SSRS 2005 for a variety of things for a billing system; one of them being actual bill generation. The bills are generally one page long, but in rare exceptions can be multiplie pages. They end up being printed onto perforated paper at around the 8 inch mark, and we basically want to put a page footer there that is the "bill stub"... a section that summarizes the bill that they rip off and return with payment.

So, I guess the general problem is that I have a want to put a section of content at a specific place at the bottom of one and only one page (the first page would be preferrable, but the last page is also acceptable), in the middle of a report that has a table of bill line items of an indeterminate height.

I went down paths of looking at PageFooter, since it is generally the idea I am after, but I can't find a way to only show it on one page... on a 4 page bill, it always wants to print on page 2 AND 3 no matter what I do.

Thanks for any help that you can provide.

Michael

The only option supported is to print the footer on first or last page of the report (PrintOnFirstPage and PrintOnLastPage property respectively of the page footer band). Please note that currently RS (2000 and 2005) doesn't allow you to reclaim the space occupied in subsequent pages if the header/footer is not printed.|||

Just pinging this thread to see if anyone has a good workaround for this type of issue. I'm trying to use SSRS 2005 for creating invoices (currently using Crystal Reports). I have specific text (also includes data from the dataset) that has to be on a specific section of the LAST page of the invoice (can be 1 or multiple pages). This is done in Crystal by creating a second PAGE FOOTER that's suppressed on every page except the last one. This issues (along with not being to keep table groups together) are causing so much difficulty in creating reports. It's hard to believe this product is missing so many basic functions. Typical MSFT in throwing something out there that gets you 80-90% of what you need. Do they even try real world situations like the basic necessity of having an invoice, bill, etc.

|||

I don't think there is any way to suppress the whole Page Footer section. What you can try doing is giving a conditional visibility expression for the textbox that you have in your Page Footer.

For example if you want the text to shown only on the 1st page then the expression =IIf(Globals!PageNumber=1,false,true)

and if you want it only on the last page then =IIf(Globals!PageNumber=Globals!TotalPages,false,true) can be used.

Hope it helps,

Aayush

|||

I've already gone the expression route. I have a rectangle with a bunch of text boxes in it. I hide the rectangle on everypage but the last (IIf(Globals!PageNumber=Globals!TotalPages,false,true) ).

That works when displaying in the browser. However, when printing or exporting to pdf the "white space" where the rectangle is shows up on every page. I need it suppressed. This is an invoice so not being able to print it or export it to pdf to be emailed is pointless.

|||

Hi,

I tried to copy and paste the condition for only displaying on last page IIf(Globals!PageNumber=Globals!TotalPages,false,true) but it doesn't seem to be working and I am getting an error ") is missing" and it highlights "Globals" (first one).

Am I doing something wrong? Please advice. Thanks for your help

Nabil

|||Looks correct to me. Sounds silly but I hope your expression starts with the '=' symbol, that is, =IIf(Globals!PageNumber=Globals!TotalPages,false,true)

2012年3月6日星期二

Any Problems with Large Packages?

I've been suffering with a variety of symptoms lately, and I don't know why:

    Can only debug once in BIDS. After that, it can never attach to DtsDebugHost.exe. DtsDebugHost.exe never receives any CPU time, and never grows past its initial memory allocation.

    Save takes a long time with 100% CPU usage. This can be as simple as openning a SQL Server Destination component to correct the metadata due to an added column in the underlying table, then saving. It takes several minutes at 100% CPU.

    I've had several Visual Studio crashes today (DW has reported these)

I've read here about people with 10MB or 17MB packages, so I feel badly complaining about my 3.2MB package! However, something is going on, and I'd like to know what it is, so I can debug again.

Thanks for any help.

Rebooting can sometimes work wonders Smile

What SP level are you running? I highly recommend SP2.

As a "good" practice, I try to keep packages small, for a variety of reasons. Smaller packages are easier to debug, seem to be more stable in BIDS, and are easier to manage in a team environment with multiple developers. My packages normally are under 1mb, and most often are 300-700kb.

|||

I'm running SP2.

Once I get it out to QA, I may look into breaking it up into smaller packages. I'm sure the size is due to the 17 outputs from the XML Source all being processed in the same data flow task. At the cost of reading the XML more than once, and of creating subset schemas (so I don't get hundreds of column not used warnings), I can break some pieces off and execute them in parallel.There are performance reasons as well, as there are buffers made wide by large string and NTEXT fields.

In the meantime, I'm wondering about how to avoid that reboot issue...

|||

A couple of other suggestion:

Try setting Work Offline (under the SSIS menu) to true before saving, and see if that makes a difference (it shouldn't, but I've seen stranger things).

How complex are the transformations in the data flow? You might want to use one package to read the file once, and save all the outputs to RAW files. Then have other packages that pick up the RAW files to do the rest of the processing. RAW files are extremely fast, so they don't introduce as much overhead as you might expect. On the other hand, if the transformations are simple, you won't get a lot of benefit from that approach.

|||

Another wonderful behavior is that data viewers aren't working reliably. I've just given up on one pair: one each on the default output and on the error output of a derived column transformation. The final step in that execution path writes to a SQL Server Destination, and indeed, the rows get there. But they don't stop at either data viewer, and there's no path to the destination that does not go through the derived column transformation.