Reporting Service: Render order of operations.

Just curious, but I am looking for some sort of definitive outline on
the steps reporting services goes through to render a report.
Example:
Header/Footer first.
Second starting from the top of the body of the report render the
first object.
If that object's a grid process the grid's header/footer first, then
go to each successive group until the details.
If a new page is pulled up, this happens here.
And so on..
It would help immensely creating reports, and also I have something I
can show to management who have a beef with a report and cannot grasp
why reporting service processes certain things in "illogical order".
Regards,
- jOn Nov 5, 3:38 pm, modi321 <modi...@.gmail.com> wrote:
> Just curious, but I am looking for some sort of definitive outline on
> the steps reporting services goes through to render a report.
> Example:
> Header/Footer first.
> Second starting from the top of the body of the report render the
> first object.
> If that object's a grid process the grid's header/footer first, then
> go to each successive group until the details.
> If a new page is pulled up, this happens here.
> And so on..
> It would help immensely creating reports, and also I have something I
> can show to management who have a beef with a report and cannot grasp
> why reporting service processes certain things in "illogical order".
> Regards,
> - j
Was this unclear or is there no visual work flow of how MS reporting
services renders a report?|||>From my experience, processing renders as
1. Table Header
2. Table Footer
(3. Group 1 Header)
(4. Group 1 Footer)
(5. Group 2 Header)
(6. Group 2 Footer)
...
x. Details
Order of execution appears to be top left-to-right, to bottom. Custom
Functions populated conditionally in the Details rows that store
values into (Static) global variables will render as 0 in the headers
and footers, because the data items are populated last.
Microsoft is extremely non-committal when it comes to order of
rendering.
-- Scott