Report design step by step

[rabijlsma]

Part I: structure the data
Before you are going to really build the report in the report designer you have to structure your data first in the following steps:

- Draw the structure of the report on a piece of paper
- Determine the data needed for the report
- Write data in correct structure to Scenario Navigator to an output table, or
- Create a query with the correct structure and data in Scenario Navigator

Part II: create the report
- Make a first preview with only one dummy label in one of the report bands. It's important to select multiple scenarios in this preview, because all of your next previews during the design of the report will then show multiple scenarios. Set also the correct paper size and margins in the first preview.
- Design the top margin (e.g. project title, report title) and the bottom margin (e.g. logo, page numbers) of your report first.
- Design the reportheader
- Put data in detail band

When you want to group the data:
- Use groupheaders to define the groups
- Put data in group footer band to get non individual values from your data, like an average over the different scenarios

- Finalize your report (e.g. font style, colors, etc.) by adjust and preview

I hope these steps will give you some structure.

[nbaum]

Why it s required to have only one table for a report?
I want to create my documentation for a whole scenario of a simulation project with a report. But with the restriction of only one table it is not possible.
In that report I want to see all relevant data tables and I want to include all relevant result tables and charts and so on.
The result should be a report per scenario which I want to provide to the participants of the project.

How I can do this?
Or is it possible to create a report which consists of other reports?

[jdewindt]

The reason for the restriction has to do with the design of tables in Scenario Navigator.
A table may contain linked values, calculated fields and formatted data besides plain static data (text, numbers, etc).
Each table used by the report must be first processed to reflect these settings. As this is a complex operation and in order to maintain a reasonable performance, we decided to limit a report data source to only 1 table.

However, there are some workarounds to overcome this limitation and to use more than 1 table in a report. I’ll create an example project and post the results in this topic as soon as possible.

[jdewindt]

However, there are some workarounds to overcome this limitation and to use more than 1 table in a report. I’ll create an example project and post the results in this topic as soon as possible.

My apologies for the delay in the follow-up. I created a new topic in the "Reports" forum which addresses this issue.
However, if this is not a valid option for you, you can submit a functionality request and we will review it.