This is more a FYI thank a bug I guess, as I'm used to MS RS which doesn't appear to do this but Telerik Reporting does.
I print a Print date on the top of reports using =Now()
In MS RS this stays consistent throughout the report.
In Telerik Reports 1.0 it appears as if the value is evaluated per page as I just had a long running report where the time field incremented on each page.
I guess the simple way round it is store a variable in code behind and use this if it is a concern.
I print a Print date on the top of reports using =Now()
In MS RS this stays consistent throughout the report.
In Telerik Reports 1.0 it appears as if the value is evaluated per page as I just had a long running report where the time field incremented on each page.
I guess the simple way round it is store a variable in code behind and use this if it is a concern.
1 Answer, 1 is accepted
0
Hi Jafin,
All items that resides in the page section (Page Header/Footer Sections) are bound when the report is paged and the current page is about to render. We definitely agree with you that this causes the problem with the Now() function that takes the current time and the report paging takes too long to render. We logged the issue and it should be fixed for the next version of the Telerik Reporting.
Thank you for the feedback! Your points have been updated.
Greetings,
Svetoslav
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
All items that resides in the page section (Page Header/Footer Sections) are bound when the report is paged and the current page is about to render. We definitely agree with you that this causes the problem with the Now() function that takes the current time and the report paging takes too long to render. We logged the issue and it should be fixed for the next version of the Telerik Reporting.
Thank you for the feedback! Your points have been updated.
Greetings,
Svetoslav
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center