List query templates define the lists that are to be included in a report. You can create a list query template on a list by list basis, for a number of list types, for all lists or for all libraries. A report can have any number of list query templates.
To add a list query template:
Context Settings enable you to define a list to use to test your CAML and to build the column mappings. It is important that you select a context first as selecting a new one resets the page.
This SharePoint dialog shows 15 items at a time. There is a link in the top-right of the dialog to see the next 15 items. This also applies when selecting the list context.
This is the option you will most likely need to use.
You can only have one instance of each list type per report.
If you have specified a context, the List Type number will be displayed.
This option can be useful if you want to query all the lists in the scope when you know that they all share common columns that you can query against; however it does return all lists, including Tabs, List of Lists etc.
This option can be useful if you want to query all the libraries in the scope when you know that they all share common columns that you can query against; however it does return all libraries, including BrightWork pages.
The purpose of the column mappings page is to map columns in the report to columns in the List Query Template. To be able to map a column in a List Query Template you must first add the column to the report.
If you have specified a context, you will be able to select a column from the List menu on the left.
If a column in the list and in the Columns section have the same internal name they will be automatically mapped.
This feature enables you to use columns from the Project Statement list in and on the report. Columns you add from the Project Statement will be available for selection in the Reporter Settings page.
The scenarios where you would need to do this include:
Mapping two columns with a different name to the same column
If you have two columns in two different lists that perform the same function, but have different internal names, you can map them to a single column.
For example, the Assigned To column is called AssignedTo in most lists; however, in the Project Deliverable Library, the Assigned To column has an internal name of AssignedToUser.
Mapping two columns with the same name to different columns
If you had two columns in two separate lists that had the same name, but actually performed different functions, you could distinguish between them by mapping one of them to a different name - otherwise they will roll up under the same column in the report.
Mapping a column with a number as a leading character to one that is acceptable to the DataTable
Report column names cannot have a number as a leading character. If a column has a number as a leading character you will have to map it to a column that does not have a number as a leading character (e.g. from 07_Feb_Sales to Feb_Sales_07).