9 Answers, 1 is accepted
0
Hi Josh,
The Excel Rendering Extension renders the whole report in a single Excel worksheet and the idea of paging is not applicable here. When you do a PrintPreview, it is the Excel application that splits the worksheet across pages. So the only way to have "Page n of m" at the bottom of each page is to add this field to the Excel Page Footer by hand. It is our fault that the "Design Considerations for Excel Rendering" section does not mention that, for which we would like to apologize.
Sincerely yours,
Ross
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
The Excel Rendering Extension renders the whole report in a single Excel worksheet and the idea of paging is not applicable here. When you do a PrintPreview, it is the Excel application that splits the worksheet across pages. So the only way to have "Page n of m" at the bottom of each page is to add this field to the Excel Page Footer by hand. It is our fault that the "Design Considerations for Excel Rendering" section does not mention that, for which we would like to apologize.
Sincerely yours,
Ross
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
0
Sean
Top achievements
Rank 1
Rank 1
answered on 10 Oct 2008, 02:58 PM
Ross,
Telerik should consider providing this functionality since Excel files exported from Microsoft Reporting Services render page numbers correctly in the Excel footer.
It seems like a competitive disadvantage for Telerik not to do the same.
Thanks.
Sean Bernard
Telerik should consider providing this functionality since Excel files exported from Microsoft Reporting Services render page numbers correctly in the Excel footer.
It seems like a competitive disadvantage for Telerik not to do the same.
Thanks.
Sean Bernard
0
Hi Sean,
We have this logged in our features list and would research the possibility to add it in a subsequent release of the Reporting product.
Please excuse us for the temporary inconvenience.
Regards,
Steve
the Telerik team
Check out Telerik Trainer, the state of the art learning tool for Telerik products.
We have this logged in our features list and would research the possibility to add it in a subsequent release of the Reporting product.
Please excuse us for the temporary inconvenience.
Regards,
Steve
the Telerik team
Check out Telerik Trainer, the state of the art learning tool for Telerik products.
0
Stephen McDaniel
Top achievements
Rank 1
Rank 1
answered on 03 Dec 2010, 12:15 AM
I'm wondering if there has been any update on this issue. It appears that the same behavior of always printing "Page 1 of 1" on every page still exists in the latest version.
Thanks,
-Stephen
Thanks,
-Stephen
0
Hi Stephen,
We have not been able to work on this feature yet and cannot provide a time frame for its implementation, but added your vote for it.
Best wishes,
Steve
the Telerik team
We have not been able to work on this feature yet and cannot provide a time frame for its implementation, but added your vote for it.
Best wishes,
Steve
the Telerik team
0
Chris
Top achievements
Rank 1
Rank 1
answered on 20 Sep 2011, 08:14 PM
It would be nice to see this put up there on the priority list.
We have developed several reporting tools for customers with 1.5 years of product development, and now that we are at the end of development to find that page numbers cannot be added to excel is making meeting customer automation requirements exceedingly challenging.
Regards,
Chris
We have developed several reporting tools for customers with 1.5 years of product development, and now that we are at the end of development to find that page numbers cannot be added to excel is making meeting customer automation requirements exceedingly challenging.
Regards,
Chris
0
Hossam
Top achievements
Rank 1
Rank 1
answered on 30 Oct 2012, 08:16 AM
Excel allows variables like &[Page] to define page numbers.
I guess this is then parssed by the Excel Preview/Print module to hold the right page number.
would there be a way where we insert these "variables" the report, and Excel would do the numbering for us?
I guess this is then parssed by the Excel Preview/Print module to hold the right page number.
would there be a way where we insert these "variables" the report, and Excel would do the numbering for us?
0
Hello,
As the PageNumber and the PageCount global objects can be used in complex expressions it is not quite clear how to determine whether the expression should be evaluated or converted. Currently this feature implementation is postponed until we have a more vivid idea how to proceed.
We are sorry for the inconvenience.
Kind regards,
Chavdar
the Telerik team
As the PageNumber and the PageCount global objects can be used in complex expressions it is not quite clear how to determine whether the expression should be evaluated or converted. Currently this feature implementation is postponed until we have a more vivid idea how to proceed.
We are sorry for the inconvenience.
Kind regards,
Chavdar
the Telerik team
HAPPY WITH TELERIK REPORTING? Do you feel that it is fantastic? Or easy to use? Or better than Crystal Reports? Tell the world, and help fellow developers! Write a short review about Telerik Reporting and Telerik Report Designer in Visual Studio Gallery today!
0
derek
Top achievements
Rank 1
Rank 1
answered on 09 Jan 2013, 08:06 PM
In my case, the value of 1 is put into the Excel footer (using File - Print - Page Setup - Header/Footer tab - Custom Footer).
The part that "=Now()" evaluated to is in the Left section [which is what I prefer, being the date the report was pulled].
But the Right section has a hard-coded 1 which is what the "=PageNumber()" evaluated to, which is bad because the 1 prints on every page. What I would prefer is that the "=PageNumber()" be translated to "&[Page]", which is what Excel uses to evaluate the page number.
I assume this also means the "Page N of M" would also need to be looked at. Those two special cases should solve the majority of the complaints on this subject.
In my opinion, only the full text match would need to "special". If PageNumber were used in an expression it's just going to process as 1 (which is what it does now anyhow). Although that does open the window for inconsistency complaints, so you're damned if you do damned if you don't, but I know that I would vote for these two full-text cases being handled special, so the end users out there get what they expect. The developers like myself will just need to know that PageNumber in an expression isn't going to translate to excel. Right now it doesn't, and the page numbering doesn't work in excel, so I'd definitely argue that it's a step in the right direction.
The part that "=Now()" evaluated to is in the Left section [which is what I prefer, being the date the report was pulled].
But the Right section has a hard-coded 1 which is what the "=PageNumber()" evaluated to, which is bad because the 1 prints on every page. What I would prefer is that the "=PageNumber()" be translated to "&[Page]", which is what Excel uses to evaluate the page number.
I assume this also means the "Page N of M" would also need to be looked at. Those two special cases should solve the majority of the complaints on this subject.
In my opinion, only the full text match would need to "special". If PageNumber were used in an expression it's just going to process as 1 (which is what it does now anyhow). Although that does open the window for inconsistency complaints, so you're damned if you do damned if you don't, but I know that I would vote for these two full-text cases being handled special, so the end users out there get what they expect. The developers like myself will just need to know that PageNumber in an expression isn't going to translate to excel. Right now it doesn't, and the page numbering doesn't work in excel, so I'd definitely argue that it's a step in the right direction.