This feature lets you design your reports from the ground up with the data sources you choose and the fields you want.

In the Name column you name your Custom Report, in the table name, you choose which table should be the data source. The group Id is in order to group Reports together, which will be described later.
The template name column acts the same way as the template column on the report override form.
On the fields tab there is a grid to setup the fields that should be on the report.
The Name column is for the XML output. You can define the name here. If left blank, it just uses the field or method name.
The reference table name is defaulted to the table set for the report on the overview tab. But you can pick a related table as well here, as long as a relation exists between the two tables in the dynamics data model.
In the above example the salesLine table is the main table for the report, but one of the lines use the inventtable, which is possible because such a relation exists naturally in the data model.
Reference field name is the field to take the data to the output from.
If the needed data is provided with a display method, the method name column can reference that instead.
On the Parameter tab you can set up parameters the user should be prompted for, when executing the report.

The Name is the parameter name, and how it will figure in the XML output to Interform.
The datatype is the basic datatype the parameter has.
In extended data type you can reference existing Extended data types, and if there are relations on the data type, the parameter dialog will provide a lookup option for the parameter.
You can set the default value of the parameter, as well as the labe, as it should look to the user in the label.
On the Attach to form you can add your report to any form in the entire system.
In the above example, the report has been attached to two different forms, you need to choose which data source on the form to use for the report, it of course has to be a compatible data source, to the table you added as the main table for the report itself. In this case it is the SalesTable, which is the same used on the report.
On control name you choose which button group on the chosen form to attach the report to, as a new menu item on the form, and the label column defines what the report menu item is caleld to the user on the attached form.
In this case we will look at the sales table list page, and see the report is now there:

And if we click it, it opens a dialog:
And as seen the parameter is present, and can look up in related data. Clicking ok, executes the report generation, and it is presented to the user:
Back on the
custom reports screen the next tab is the printers tab:
In this, you simply set up which printers should be available for the specific report.
On the output tab, you can see an example XML output of the current setup of your report:
What is
important to notice here is that under the salesTable, there are lines, even
though the report has only been set up for one data source. That brings us to
the final setup part of the custom reports.
You can
embed reports within each other in the embedded reports button in the top of
the form.
In this case, the Sales Header report is active, and when we click the Embedded reports button you can choose which reports should be embedded in the dataset as well.
In this case, the salesLine report has been set to be an embedded report for the salesTable report. The table picked in the table name, is the table that holds the relation between the two tables set for each report, thereby tying them together.
The Run report button does the same, as when you ran the report on an attached form, this just provides the user the possibility to test the report genration, without having to attach the report to a form until the output is ready.