Customizing the Master Report
The definition generated by Studio's Master Report Layout wizard includes a number of elements that you can customize.
For example, in the header you can specify your own logo image and title. You can copy and paste Menu Branch and Menu Leaf elements as often as needed to complete your menu. And you can place your own message in the footer.
Of course, you're not limited to working with just the elements and
styling that the wizard generates - you can tailor the definition to meet
Using Tokens in a Master Report
Due to the way that the Logi Server Engine combines a Master Report definition and the other report definition, you can include certain tokens in the Master Report representing data from the other report.
For example, if the other report is called with a URL that includes Request variables, then you can access those values using @Request tokens in the Master Report definition. As such, there's no way to, nor need to, use elements to "pass" parameters to the Master Report.
Similarly, if the other report uses Local Data to retrieve data, then you can use @Local tokens to access those values in the Master Report definition.
Tokens with universal scope, like @Session, @Function, @Constant, and
others, can also be used in the Master Report definition and will be
Styling a Master Report
If you want to use a theme with your application we generally recommend that you apply it in your application's _Settings definition or in the other reports, not in a Master Report. If a Master Report and the other report definition are assigned different standard themes, the other report's theme will be used.
You can include a style sheet in a Master Report to style it, but
be aware that the styling is not restricted to the Master Report. Due to
the way the definitions are combined at runtime, unless overridden by a
class in a theme assigned to the other report, classes in the Master
Report could affect content in the other report.
You may use User Input elements in a Master Report and their values will be passed as Request variables, as usual, when the combined reports are submitted.
Master Reports are executed every time another report that references them is loaded or re-loaded so, for best performance, you probably do not want to place long-running queries in them.