Difference between revisions of "Create iReport Templates with Subreports"

From IMSMA Wiki
Jump to: navigation, search
 
(72 intermediate revisions by 7 users not shown)
Line 1: Line 1:
==Advanced Reports==
+
{{TOC right}}
===Sub-Report===
+
==Creating Subreports==__NOEDITSECTION__
<p>Sub-report is reports within a report; thus, providing a way to generate a report that includes data on the target IMSMA Item as well as data on other IMSMA Items that are associated to the target IMSMA Item.  Generally a sub-report is used in a situation where you have one or more sets of data relating to a single IMSMA item. A common use case would be a Location report with multiple details bands of different IMSMA items (Land, Activity, Accident, Victim, Education, and QM).</p>
+
A subreport is a report within a report; thus, providing a way to generate a report that includes data on the target IMSMA item as well as data on other IMSMA items that are associated to the target IMSMA item.  Generally a subreport is used in a situation where you have one or more sets of data relating to a single IMSMA item. A common use case would be a Location report with multiple details bands of different IMSMA items (Land, Activity, Accident, Victim, Education, and QM).
<p>Regardless of what IMSMA data you’re including in your report and sub-reports, there are 6 basic steps to create a report with sub-reports:</p>
 
  
:Step 1 – Create the Main report
+
Regardless of what IMSMA data you’re including in your report and subreports, there are 5 basic steps to create a report with subreports:
:Step 2 – Add Sub-report to the Main report
+
:Step 1 – Create the main report
:Step 3 – Add Parameter to the Sub-report
+
:Step 2 – Add a subreport to the main report
:Step 4 – Define Report Query for the Sub-report
+
:Step 3 – Add a parameter to the subreport
:Step 5 – Add Sub-report Parameter to the Main report
+
:Step 4 – Define the report query for the subreport
:Step 6 – Repeat Step 2-5 for additional Sub-reports
+
:Step 5 – Add subreport parameter to the main report
  
[[Image:iRepStep01.png|center|500px|''Step 1 – Create the Main Report'']]
+
====Step 1 – Create the Main Report====__NOEDITSECTION__
  
====''Step 1 – Create the Main Report''====
+
Before creating the main report, you will need to determine what data should be included in your report.  For example, if you are creating a report about Land with all the Progress Report data, then the target IMSMA item for your main report should be Land and the target data for your subreport should be Activity assuming that Progress Reports are entered into the system as Activity.  Below is a list of questions and things to be considered when designing a report.
 
 
<p>Before creating the main report, you will need to determine what data to be included on your report.  For example, if you are creating a report about Land with all the Progress Report data, then the target IMSMA item for your main report should be Land and the target data for your sub-report should be Activity assuming that Progress Reports are entered into the system as Activity.  Below is a list of questions and things to be considered when designing a report.</p>
 
 
*What are all the data to be included on the report?
 
*What are all the data to be included on the report?
*What is the target IMSMA Item for the Main report?  This is the primary data of your report.
+
*What is the target IMSMA item for the main report?  This is the primary data of your report.
*What is the target IMSMA Item for the sub-reports?  This is the secondary data of your report.
+
*What is the target IMSMA item for the subreports?  This is the secondary data of your report.
*Determine the relationship between the primary data and the secondary data.  How did they get reconciled to one another?
+
*Determine the relationship between the primary data and the secondary data.  How did they get reconciled to one another? How are they linked?
  
<p>The Main report should be created with the IMSMA item determined to be the primary data of your report.  The Main report is just a basic report and can be created using the steps provided in the “Creating a Basic Report” section. Below are the instructions:</p>
+
The main report should be created with the IMSMA item determined to be the primary data of your report.  The main report is just a basic report and can be created using the steps provided in the [[Create a Basic iReport Template]] section.
<ol>
 
<ol type="a">
 
<li>Create your main report with the IMSMA item determined as the primary data of your report.  This is just a basic report.</li>
 
<li>Save your main report</li>
 
<li>Compile your main report to make sure that it’s error-free.</li>
 
</ol>
 
</ol>
 
  
[[Image:iRepStep02.png|center|500px|''Step 2 – Add Sub-report to the Main report'']]
+
====Step 2 – Add Subreport to the Main report====__NOEDITSECTION__
  
====''Step 2 – Add Sub-report to the Main report''====
+
Once the main report has been created you can add a subreport to the main report. The intent of the subreport is to bring data from a different but related datasource into the main report. For example, you could include Activity data on a report about Land.  Below are the instructions to create a subreport:
  
<p>Sub-report is reports within a report.  As mentioned earlier, a sub-report should be created with the IMSMA Item determined as the secondary data of the reportBelow is the instructions to create a sub-report:</p>
+
# On the main report, from the '''Palette''' pane, select '''Subreport''' and drag it to the desired band on the iReport template (normally this is the '''Detail''' band).
 +
#:[[Image:IReportSubReportPalette.png|center|300px|''Subreport Palette'']]<div align="center">''Subreport Palette''</div>
 +
# Release the button and the window below displays.
 +
#:[[Image:IReportSubReport1.png|center|500px|''Add Subreport to the Main report'']]
 +
# Click '''Next''' to define a new subreport unless you have an existing report that you would like to use for subreport.
 +
# Select the desired iReport Template to apply (Blank is recommended).
 +
#:[[Image:IReportSubReport2.png|center|500px|''Select the desired iReport Template'']]
 +
# Select from the '''Connection/Data Source''' listThis should be the IMSMA item determined as the secondary data of your report. For example, if you are creating a report about Land with Progress Reports, then “Hazard Reduction” should be the data source for the subreport. Click Next.
 +
#:[[Image:IReportSubReport3.png|center|500px|''Select the desired datasource'']]
 +
# Select the attributes to be included in your subreportClick '''Next'''.
 +
#:[[Image:IReportSubReport4.png|center|500px|''Select the desired fields for the subreport'']]
 +
# Select the fields to group by. This step is not required.  Click '''Next'''.
 +
#:[[Image:Subreport_Group_by.png|center|500px|''Select the fields to group by'']]
 +
# Enter a name for the subreport or use the default. Choose '''Next'''.
 +
#:[[Image:IReportSubReport5.png|center|500px|''Enter a name for the subreport'']]
 +
# Select '''Use the same connection used to fill master report'''. Click Finish. 
 +
#:[[Image:IReportSubReport6.png|center|500px|''Use same connection'']]
 +
# The subreport displays.
  
<ol type="a">
+
====Step 3 – Add Parameter to Subreport====__NOEDITSECTION__
<li>Increase the size of Detail section of the Main report to make room for your sub-report.</li>
 
:'''View''' -> '''Bands''' -> '''detail''' -> '''increase the Band Height''' -> '''Apply'''
 
<li>Click the [[Image:iRepBand.png]] button</li>
 
<li>Click the detail section of the report.  Hold down the mouse button and drag the cursor to create a rectangle to define the area of sub-report.  Release the botton and the window below displays.</li>
 
</ol>
 
  
[[Image:iRepBandScreen.png|center|500px]]
+
To connect a subreport to the main report, we next need to create a parameter for passing the identification (guid) of the primary IMSMA item between the subreport and the main report. In the '''Report Inspector''' on the subreport, [[Modify an iReport Template#Adding a Parameter to an iReport Template|add a Parameter]] to hold the guid of the IMSMA item on the main report. It is recommended to add a fairly generic parameter name such as ''ItemGUID'' so that the subreport can be more easily re-used.
  
<ol type="a" start="4">
+
# From the Report Inspector, '''right click''' on the '''Parameter''' tree and choose '''Add Parameter'''.
<li>Click '''Next''' to define a new sub-report unless you have an existing report that you would like to use for sub-report.</li>
+
#: [[Image:IReport AddParameter1.png|center|250px|''Add Parameter'']]
<li>Select from the '''Connection/Data Source''' list. This should be the IMSMA item determined as the secondary data of your report. For example, if you are creating a report about Land with Progress Reports, then “Activity” should be the data source for the sub-report. Click Next.</li>
+
# In the '''Properties''' pane, enter a parameter name (e.g. ItemGUID} and edit any other properties. Normally it is not required to edit anything other than the name, you might however want to deselect the '''Use as a prompt''' option.
<li>Select the attributes to be included in your sub-report.  Click '''Next'''.</li>
+
#: [[Image:IReport AddParameter2.png|center|250px|''Add Parameter'']]
<li>Select the layout option.  Click '''Next'''.</li>
+
# Once the parameter is added it will be available in the '''Report Inspector''' and can be referenced as ''$P{parametername}''. For example:
<li>Enter a name for the sub-report. Click Finish.  The sub-report displays.</li>
+
  $P{ItemGUID}
</ol>
 
  
[[Image:iRepStep03.png|center|500px|''Step 3 Add Parameter to Sub-report'']]
+
====Step 4 Define Report Query for Subreport====__NOEDITSECTION__
  
====Step 3 – Add Parameter to Sub-report====
+
The next step is to create a report query for the subreport you just created in Step 2 to define how the IMSMA item on the main report is related to the IMSMA item on the subreport. Typically the subreport report query will receive the guid from the main report via the parameter created in Step 3 and then use it to limit items in the subreport to those linked to the main report.  Below is the instructions on how to define the report query:
  
<p>To connect a sub-report to the Main report, we need to create a parameter for passing the identification (guid) of the primary IMSMA Item between the sub-report and the main report. Below is the instructions to create the parameter you need for the sub-report:</p>
+
# Open the [[Modify an iReport Template#Using Report Query filters|report query window]].
 
+
# From the report query window, select '''ImsmaQuery''' from the query language list.
<ol start="a">
+
# Enter a report query filter using the parameter defined above to limit the objects according to the main report object. The most common report query filter would be to filter to only linked objects. For example '''''links.toGuid="$P{ItemGUID}"'''''. In this step, the Report Query tells the subreport to return only rows that are linked to the guid of the item in the main report via the link table. Other combinations of report query filters can be used on subreports beyond the link table. These are documented in the [[#Example Subreport Relationships|Possible Subreport Relationships]] section below.
<li>At the Sub-report window, select View -> Parameters.  
+
# Click '''OK'''. The report query window closes.
:The window displays the parameters.
+
# Save the subreport.
</ol>
 
 
 
[[Image:iRep09.png|center|500px|''Figure 9. Window of fields, variables, and parameters'']]
 
<div align="center">
 
''Figure 9. Window of fields, variables, and parameters''
 
</div>
 
  
<ol type="a" start="2">
+
====Step 5 – Link the Subreport to the Main Report====__NOEDITSECTION__
<li>Click the '''New''' button.</li>
+
Now that both the main and the subreport are ready, the only thing that remains to be done is linking the two together. Below are the instructions to link the two reports:
:The Add/modify parameter window displays.
+
# Make sure you are at the main report by selecting the name of the main report from the tabs at the top of the iReport Designer canvas pane.
<li>From the Add/modify parameter window:</li>
+
# Select the subreport box within the main report.
*Enter “'''''object_guid'''''” for the '''Parameter Name''' where ''object_guid'' is the suggested parameter name in the Column D of the Table - Required Parameters for Sub-report below.
+
#: [[Image:IReportSubReportSelection.png|center|500px|''Select the Subreport on the main report'']]<div align="center">''Select the Subreport on the main report''</div>
*Click the '''OK''' button.
+
# On the '''Properties''' pane for the Subreport, select the '''Parameter''' selector.
<li>Close the window that displays the list of all parameters.</li>
+
#: [[Image:IReport_SubReportProperties.png|center|200px|''Subreport properties'']]<div align="center">''Subreport properties''</div>
</ol>
+
# '''Add''' a parameter and type '''exactly the name of the subreport parameter created in step 3''' (e.g. ''ItemGUID'')
 +
#: [[Image:IReport_SubReportParameter.png|center|200px|''Add a parameter'']]<div align="center">''Add a parameter''</div>
 +
# For the '''value expression''', select the appropriate field to include in the parameter. '''Normally this is ''$F{guid}''''' but other choices are available.
 +
#: [[Image:IReport_SubReportParameter2.png|center|200px|''Select the appropriate field'']]<div align="center">''Select the field to include in the parameter''</div>
 +
# Click '''OK''' and close Subreport Parameters window.
  
[[Image:iRepStep04.png|center|500px|''Step 4 – Define Report Query for Sub-report'']]
+
You are now ready to run your main report. Running (i.e. previewing) the main report will automatically run the subreport(s) as well, and the data from the main as well as from the subreport(s) will be included in the output.
  
====Step 4 – Define Report Query for Sub-report====
+
==Kinds of Subreports==__NOEDITSECTION__
 +
There are three main kinds of relationships in IMSMA on which subreports can be generated from IMSMA data. These are:
 +
*Location relationship
 +
*Link relationship
 +
*Geospatial relationship
 +
*Other relationship
  
<p>The next step is to create a report query for the sub-report you just created in Step 2 to define how the IMSMA item on the Main report is related to the IMSMA item on the Sub-report.  Below is the instructions on how to define the Report Query:</p>
+
===Location relationship subreports===__NOEDITSECTION__
 +
Because each of the main items in {{IMSMANG}}, Accident, Activity, Assistance, Education, Land, QM, and Victim, must be reconciled to a Location during the data entry phase, each of these objects has a relationship with Location and can thus be a subreport on a Location main report. Since all accidents, land, activities, educations, QMs, assistances, and victims are associated with a single location each record knows what location it is related to based on the '''''location guid''''' field. When creating a report where the main report is a Location and the subreport is one of the associated objects the Location's guid is passed to the subreport in a parameter and the subreport can use a special ImsmaQuery language syntax to limit the subreport data to those associated with the main report's location:
 +
location.guid = "$P{parametername}"
  
<ol start="23">
+
The location guid field in the subreport item table contains the guid of the location to which the item record is associated. The figure below shows an example of a location and the accident and land that are associated to the location. Notice that the location_guid value (1234-1234) in the accident and land are identical to the location_guid of the location.
<li>At the Sub-report window, select Data -> Report Query.</li>
 
:The Report query window displays.
 
<li>From the Report query window:</li>
 
<ol type="a" start="3">
 
<li>Select ImsmaQuery from the Query language list.</li>
 
<li>Enter object.guid = “$P{object_guid}” for the ImsmaQuery where object  is the object type of the IMSMA item on the Main report - See Column E in the Table - Required Parameters for Sub-report below to determine the ImsmaQuery string for your Sub-report.</li>
 
</ol>
 
</ol>
 
  
[[Image:iRep10.png|center|500px|''Figure 10. Define Report Query for Sub-report'']]
+
[[Image:iRep14.png|center|500px|''location_guid example'']]
 
<div align="center">
 
<div align="center">
''Figure 10. Define Report Query for Sub-report''
+
''location_guid example''
 
</div>
 
</div>
  
<ol>
+
To create a subreport using the Location relationship:
<ol type="a" start="5">
+
# From the main "Location" report, pass the location '''''guid''''' to the subreport in a parameter (e.g. in a parameter called '''ItemGUID''').
<li>Click '''OK'''.</li>
+
# Create a parameter on the subreport with the same name as in #1.
:The Report query window closes.  
+
# In the subreport for the related item (e.g. a Victim) use the parameter in the following ImsmaQuery language syntax
<li>Click the [[Image:iRepCompile.png]] button to compile the sub-report.</li>
+
location.guid="$P{parametername}"
</ol>
 
</ol>
 
  
[[Image:iRepStep05.png|center|500px|''Step 5 – Add Subreport Parameter to Main Report'']]
+
This has the effect of limiting the subreport records to '''only those records that are associated to the location''' from the main report.
  
====Step 5 – Add Subreport Parameter to Main Report====
+
===Link relationship subreports===__NOEDITSECTION__
 +
In addition to the Location relationship, the main items in {{IMSMANG}} can also be linked with one another during the reconciliation process. This is how, for example, Activities are linked with Land in the {{IMSMANG}} database. Accidents, land, activities, educations, assistances, QMs, and victims may be related to one another via ''links''. For example, a victim may be associated to an accident in a particular land. If these relationships are known, IMSMA users may define these links while reconciling the Data Entry Form. This special relationship can also be modeled in iReport using a report and subreport(s).
 +
 +
The process for creating a report on an item and its linked items is similar to the process for creating a report on items with a Location relationship. The item in the main report is the primary item for which you would like to find linked items. The subreport would return the records for the particular item that is linked to the primary item. The key difference is the query used in the subreport.
  
<p>We created a parameter on the sub-report to connect to the Main report in Step 3, now we need to create a parameter on the Main report as well.  Below is the instructions to create the parameter you need for the Main report:</p>
+
To create a subreport using the link relationship:
<ol type="a">
+
# From the main report, pass the '''''guid''''' of the main report object to the subreport in a parameter (e.g. pass an accident's '''''guid''''' in a parameter called '''ItemGUID''').
<li>Make sure you are at the Main report by selecting the name of the Main report from the '''Window''' menu or double-clicking the Main report from the Files pane.</li>
+
# Create a parameter on the subreport with the same name as in #1.
<li>Double-click the sub-report box within the Main report.</li>
+
# In the subreport for the related item (e.g. a Victim) use the parameter in the following ImsmaQuery language syntax
:A window displays four tabs (Common, Sub-report, Sub-report (Other), and All).  
+
links.toGuid="$P{parametername}"
<li>Select the Sub-report (Other) tab. Click '''Add'''.</li>
 
<li>From the Add/modify parameter window:</li>
 
<ol type="i">
 
<li>Enter ''“$P{object_guid}”'' for the '''Sub-report Parameter Name''' field where ''object_guid'' is the parameter name you created in Step 3 for the Sub-report. See Column B in the Table – Required Parameters for Sub-report below to determine the parameter name.</li>
 
<li>In the '''Default Value Expression''' field, enter ''$F{guid}''.</li>
 
<li>Click '''OK''' and close the windowthe four tabs.</li>
 
</ol>
 
</ol>
 
  
[[Image:iRepStep06.png|center|500px|''Step 6 – Repeat Step 2-5 for additional sub-reports.'']]
+
This has the effect of limiting the subreport records to only those records that have a '''link''' to the guid or object passed from the main report.
  
====Step 6 – Repeat Step 2-5 for additional sub-reports.====
+
===Geospatial relationships===__NOEDITSECTION__
 +
In addition to Location and Link relationships, many objects in IMSMA can store geospatial/geographic information (i.e. point/polygon information). This relationship with the geospatial data can be modeled in a report/subreport relationship for any item that has geospatial information associated with it. To include point/polygon information on an object's main report, follow 3 basic steps:
  
<p>You can have multiple sub-reports in one Main report.  To add more sub-reports to the Main report, just repeat Step 2 to Step 5.</p>
+
*Step 1: Create a main report for an object with geospatial info
<p>Once you have all the sub-reports created for your Main report, you can compile and run your Main report.</p>
+
*Step 2: Create a GeospatialInfo subreport on the main report, i.e. a report using the GeospatialInfo datasource
<p>Below is the table listing typical parameters required for both Main report and Sub-report.</p>
+
*Step 3: Create a Geopoint subreport on the GeospatialInfo report, i.e. a report using the Geopoint datasource
  
<table border="1">
+
Step 1: Create a main report for an object with geospatial info
<tr>
+
* Create a main report with an object that has geospatial information (e.g. Land).
<td>A</td>
+
* Ensure that the '''''geospatialInfos''''' field is added to the main report.
<td>B</td>
 
<td>C</td>
 
<td>D</td>
 
<td>E</td>
 
<td>F</td>
 
</tr>
 
<tr>
 
<td>If your Main report is</td>
 
<td>Sub-report parameter on Main report</td>
 
<td>Your Sub-report can be…</td>
 
<td>Parameter on Sub-report</td>
 
<td>Report Query defined on Sub-report</td>
 
<td>Comments</td>
 
</tr>
 
<tr>
 
<td>Location</td>
 
<td>location_guid</td>
 
<td>Land,
 
Activity,
 
Accident,
 
Victim,
 
Education, or
 
QM
 
</td>
 
<td>location_guid</td>
 
<td>location.guid = "$P{location_guid}"</td>
 
<td>Relationship is defined as “New” to a Location during the reconciliation. </td>
 
</tr>
 
<tr>
 
<td>Land, Activity,
 
Accident,
 
Victim,
 
Education, or
 
QM
 
</td>
 
<td>object_guid</td>
 
<td>Land, Activity,
 
Accident,
 
Victim,
 
Education, or
 
QM
 
</td>
 
<td>object_guid</td>
 
<td>links.toGuid = "$P{ object_guid}"</td>
 
<td>Relationship is defined using “Link” during the reconciliation.</td>
 
</tr>
 
<tr>
 
<td>MRE</td>
 
<td>mre_guid</td>
 
<td>MRE Detail</td>
 
<td>mre_guid</td>
 
<td>mre.guid = "$P{mre_guid}"</td>
 
<td>Relationship is defined as “New” to a MRE during the reconciliation.</td>
 
</tr>
 
<tr>
 
<td>Activity</td>
 
<td>hazreduc_guid</td>
 
<td>Impact survey,
 
Interviewee, or
 
Vegetation removal
 
</td>
 
<td>hazreduc_guid</td>
 
<td>hazreduc.guid = "$P{hazreduc_guid}"</td>
 
<td>Relationship is defined as “New” to an Activity during the reconciliation.</td>
 
</tr>
 
<tr>
 
<td>Interviewee</td>
 
<td>interviewee_guid</td>
 
<td>Question</td>
 
<td>interviewee_guid</td>
 
<td>interviewee.guid = “$P{ interviewee_guid}”</td>
 
<td>Relationship persisted automatically when Questions are entered for each Interviewee  at Field Report.</td>
 
</tr>
 
<tr>
 
<td>Victim</td>
 
<td>victim_guid</td>
 
<td>Received MREs</td>
 
<td>victim_guid</td>
 
<td>victim.guid = "$P{victim_guid}"</td>
 
<td>Relationship is defined as “New” to a Victim during the reconciliation.</td>
 
</tr>
 
<tr>
 
<td>Task</td>
 
<td>task_guid</td>
 
<td>Work Item</td>
 
<td>task_guid</td>
 
<td>task.guid = "$P{ task_guid}"</td>
 
<td>Relationship is defined when adding a new Work Item to a Task at the Task Editor Window.</td>
 
</tr>
 
</table>
 
  
<p>The following section of the Advance Reports chapter discusses relationships between Items in IMSMA and also provides instructions on how to create a specific report/sub-reports.</p>
+
Step 2: Create a GeospatialInfo subreport on the main report
 +
* On the main report, add a subreport using the '''GeospatialInfo''' datasource
 +
* Pass the '''''geospatialInfos''''' field to the subreport in a parameter (e.g. GeospatialInfoList). '''Note:''' instead of passing the '''''$F{guid}''''' field to the parameter, the parameter value should be '''''$F{geospatialInfos}'''''
 +
* In the GeospatialInfo subreport use the parameter in the following ImsmaQuery language syntax
 +
guid IN $P{parametername}
  
==Reports on Items with a Direct Relationship==
+
Step 3: Create a Geopoint subreport on the GeospatialInfo report
<p>The reports discussed so far in this training module have been based on a single data source. In this part of the training module, you will learn to create more complex reports that reference multiple data sources. Some items are dependent on the existence of another item. This type of relationship is referred to as a direct relationship. For example, an accident, land, activity, education, QM, or victim has a direct relationship to the location to which it is associated. The accident, land, activity, education, QM, or victim cannot exist unless it is associated with a location. This direct relationship is enforced in IMSMA via the reconciliation process.</p>
+
* On the Geospatialinfo subreport, add a subreport using the '''Geopoint''' datasource
 +
* Pass the '''''guid''''' field to the subreport in a parameter (e.g. GeospatialGUID). '''Note:''' Pass the '''''$F{guid}''''' field '''NOT''' the '''''$F{geospatialInfos}''''' value.
 +
* In the Geopoint subreport use the parameter in the following ImsmaQuery language syntax
 +
geospatialinfoguid IN $P{parametername}
  
[[Image:iRep11.png|center|500px|''Figure 11. Location and item records directly associated with it'']]
+
This has the effect of limiting the Geospatial records to only those records whose guid is linked to the geospatialinfo of the main report. This is an example of nested reports, i.e. a main report, a subreport, and a sub-subreport.
<div align="center">
 
''Figure 11. Location and item records directly associated with it''
 
</div>
 
  
Direct relationships also exist when subsets of data are contained within an item. For example, an MRE may have MRE details such as the MRE type, total audience, and percentage of women and men. The MRE details data requires the MRE to exist.
+
===Other subreport relationships===__NOEDITSECTION__
 +
Certain items in {{IMSMANG}} have subsets of data that are contained within them. For example, an education may have education details such as the education type, total audience, and percentage of women and men. Examples of other subreport relationships include:
  
The following sections will describe the process for creating reports on items that have a direct relationship between them.
+
<center>
 
+
{| class="wikitable" width="600"
===Country Structure Areas and Associated Locations===
+
|-
Although a location must be associated with a country structure area, the process for creating a report of locations in a country structure area is very similar to a basic report. The location data source contains a field for each country structure area that is defined in your IMSMA database.
+
| align="center" colspan="2" | '''Other subreport relationships'''
 
+
|-
To create a report that lists locations within a country structure area:
+
| width="150pt" | '''Parent item'''
<ol>
+
| width="450pt" | '''Child item(s)'''
<li>From the '''File''' menu, select '''Report Wizard'''.</li>
 
:The iReport Wizard window displays.
 
<li>From the '''Connection/Data Sources''' list, select ''Location Data Source''.</li>
 
<li>Click the '''Next''' button.</li>
 
:The window to select the attributes to include in the report displays.
 
<li>From the Step 2. select fields screen:</li>
 
<ol type="a">
 
<li>Select the country structure level(s) on which you would like to list the associated locations.</li>
 
<li>Select the fields that you would like to include in the report.</li>
 
<li>Click the '''Next''' button.</li>
 
:A window displays the selected fields.
 
</ol>
 
<li>Click the '''Next''' button.</li>
 
:The window group the report data displays.
 
<li>From the Group lists, select the country structure level(s) that you selected in step 4a.</li>
 
</ol>
 
 
 
{| class="wikitable"
 
 
|-
 
|-
| [[File:Note.jpg | 40px]] || Be sure to select the highest country structure level for Group 1, followed by the next highest country structure level for Group 2, and so on.
+
| Activity  || Activity Device
|}
 
  
<ol start="7">
+
Impact survey
<li>Click the '''Next''' button.</li>
 
:The window to select a layout displays.
 
<li>From the window to select a layout:</li>
 
<ol type="a">
 
<li>Select the layout option for the report.</li>
 
<li>Click the '''Next''' button.</li>
 
:The window displays a message stating that you have successfully created a new report.
 
<li>Click the '''Finish''' button.</li>
 
:The template for your report displays.
 
<li>Click the [[Image:iRepCompile.png]] button to compile the report.</li>
 
:The Save report window displays.
 
<li>Enter a name for the report in the '''File name''' field.</li>
 
<li>If there are no compilation errors, you may click the [[Image:iRepRun.png]] button to run the report.</li>
 
:The results of the report display in the iReport JasperViewer window.
 
</ol>
 
</ol>
 
  
===Location and Associated Items===
+
Interviewee
A report of locations and associated items requires you to create an iReport sub-report. A sub-report is a report that is contained within another report. A report on locations and its associated item records will require you to create a report and a sub-report. The main report will contain the data for the location. For each associated item that you would like to include, you will need to create a sub-report.
 
  
[[Image:iRep12.png|center|500px|''Figure 12. Location and associated item records'']]
+
Question
<div align="center">
 
''Figure 12. Location and associated item records''
 
</div>
 
  
All records in IMSMA have a ''guid''. A ''guid'' is a unique value that identifies the record in the IMSMA database. Because the guid is lengthy and comprised of alphanumeric characters, it is typically not a useful value to display in a report. However, the guid is necessary in determining which item records have a direct relationship.
+
|-
 +
| Education || Education details
 +
|-
 +
| Victim || Received Education
  
All accidents, lands, activities, educations, QMs, and victims are associated with a single location. The information about the location to which an item record is associated is stored in the location_guid field of the item table and corresponds to the location_guid of the location to which it is associated ([[:Image:iRep03.png|Figure 13]]). 
+
Needs Assessment
  
[[Image:iRep13.png|center|500px|''Figure 13. location_guid'']]
+
Cause
<div align="center">
+
''Figure 13. location_guid''
 
</div>
 
 
 
The location_guid field in the item table contains the guid of the location to which the item record is associated. [[:Image:iRep14.png|Figure 14]] shows an example of a location and the accident and land that are associated to the location. Notice that the location_guid value (1234-1234) in the accident and land are identical to the location_guid of the location.
 
 
 
[[Image:iRep14.png|center|500px|''Figure 14. location_guid example'']]
 
<div align="center">
 
''Figure 14. location_guid example''
 
</div>
 
 
 
Creating a report of a location and associated items will require you to complete the following parts:
 
:*Part 1: Create a report with location fields
 
:*Part 2: Create a sub-report for the associated item
 
:*Part 3: Add parameters to the sub-report
 
:*Part 4: Create a query the in sub-report to associate the guid to the location report
 
:*Part 5: Add parameters to the location report
 
:*Part 6: Compile and execute the location report
 
 
 
====Part 1. Create a report with location fields====
 
The first part of creating a report of locations and their associated items is to create a report of the location fields you would like to include.
 
 
 
<ol>
 
<li>Ensure that the IMSMA server is started.</li>
 
<li>From the '''File''' menu, select '''Report Wizard'''.</li>
 
<li>From the '''Connection/Data Sources''' list, select Location Data Source to create a report of locations.</li>
 
<li>Click the '''Next''' button.</li>
 
:The iReport Wizard, Step 2 window displays a list of the location attributes.
 
<li>Select the fields you would like to include for the location.</li>
 
<li>Click the '''Next''' button.</li>
 
:The window displays a list of the attributes that you have selected.
 
<li>Click the '''Next''' button.</li>
 
:The iReport Wizard, Step 3 window displays to allow you to group the report results.
 
<li>Because the report results for this exercise will not need to be grouped, click the Next button.</li>
 
:The iReport Wizard, Step 4 window displays to allow you to select the report layout.
 
<li>Select a layout option.</li>
 
<li>Click the '''Next''' button.</li>
 
:The iReport Wizard, Step 5 window displays.
 
<li>Click the '''Finish''' button.</li>
 
<li>Save the report by doing one of the following:</li>
 
*Click the [[Image:iRepSave.png]] icon.
 
*From the File menu, select '''Save'''.
 
::The Save report window displays.
 
<li>Enter a name for the report in the '''File name''' field.</li>
 
<li>Click the Save button.</li>
 
</ol>
 
 
 
====Part 2. Create a sub-report for the associated item====
 
 
 
<table border="1">
 
<tr>
 
<td>The next part of the process for creating a report on locations and its associated items requires you to create a sub-report within the location report.</td>
 
</tr>
 
</table>
 
 
 
<ol>
 
<li>Expand the detail section of the report by doing the following:</li>
 
<ol type="a">
 
<li>From the '''View''' menu, select '''Bands'''.</li>
 
<li>From the left pane, select ''detail''.</li>
 
<li>In the '''Band Height''' field that is in the right pane, increase the height of the detail section. At a minimum you will want to double the height.</li>
 
</ol>
 
</ol>
 
 
 
[[Image:iRep15.png|center|500px|''Figure 15. Detail band height'']]
 
<div align="center">
 
''Figure 15. Detail band height''
 
</div>
 
 
 
<ol>
 
<ol type="a" start="3">
 
<li>Click the '''Apply''' button.</li>
 
<li>The height of the band increases based on the value that you entered.</li>
 
</ol>
 
</ol>
 
 
 
[[Image:iRep16.png|center|500px|''Figure 16. Increased detail band'']]
 
<div align="center">
 
''Figure 16. Increased detail band''
 
</div>
 
 
 
<ol start="2">
 
<li>Click the [[Image:iRepBand.png]] button to add a sub-report.</li>
 
:The cursor changes to a crosshair.
 
</ol>
 
 
 
[[Image:iRep17.png|center|500px|''Figure 17. Sub-report button'']]
 
<div align="center">
 
''Figure 17. Sub-report button''
 
</div>
 
 
 
<ol start="3">
 
<li>Click the detail section of the report.</li>
 
<li>While holding down the mouse button, drag the cursor to form the rectangle which will contain the sub-report.</li>
 
<li>Release the mouse button.</li>
 
:The window below displays.
 
</ol>
 
 
 
[[Image:iRep18.png|center|500px|''Figure 18. Sub-report creation'']]
 
<div align="center">
 
''Figure 18. Sub-report creation''
 
</div>
 
 
 
<ol start="6">
 
<li>From the window:</li>
 
<ol type="a">
 
<li>Select the ''Create a new report'' option.</li>
 
<li>Click the '''Next''' button.</li>
 
::The How fill the sub-report screen displays.
 
</ol>
 
<li>From the window:</li>
 
<ol type="a">
 
<li>Select the data source for the associated item from the Connection/Data Source list. For example, if you are creating a report of locations and its associated accidents, you would select the accident data source.</li>
 
<li>Click the '''Next''' button.</li>
 
::The window to select the attributes to include in the report displays.
 
</ol>
 
<li>From the window:</li>
 
<ol type="a">
 
<li>Select the attributes that you would like to include in the report.</li>
 
<li>Click the Next button.</li>
 
::The window to select a layout displays.
 
</ol>
 
<li>From the window to select a layout:</li>
 
<ol type="a">
 
<li>Select the layout option.</li>
 
<li>Click the Next button.</li>
 
::The window to specify the sub-report expression displays.
 
</ol>
 
<li>From the window to specify the sub-report expression:</li>
 
<ol type="a">
 
<li>Enter a name for the sub-report.</li>
 
<li>Click the Finish button.</li>
 
::The sub-report displays.
 
</ol>
 
</ol>
 
 
 
====Part 3. Add parameters to the sub-report====
 
 
 
<table border="1">
 
<tr>
 
<td>The next part of the process for creating a report on locations and its associated items is to define parameters that will be used for passing the location id between the sub-report and location report.</td>
 
</tr>
 
</table>
 
 
 
<ol>
 
<li>From the '''View''' menu, select '''Parameters'''.</li>
 
:The window displays the parameters.
 
</ol>
 
 
 
[[Image:iRep19.png|center|500px|''Figure 19. Window of fields, variables, and parameters'']]
 
<div align="center">
 
''Figure 19. Window of fields, variables, and parameters''
 
</div>
 
 
 
<ol>
 
<li>Click the '''New''' button.</li>
 
:The Add/modify parameter window displays.
 
<li>From the Add/modify parameter window:</li>
 
<ol type="a">
 
<li>In the '''Parameter Name''' field, enter a name for the parameter that will be used to identify the guid for the location.</li>
 
</ol>
 
</ol>
 
 
 
{| class="wikitable"
 
 
|-
 
|-
| [[File:Note.jpg | 40px]] || Although there are no requirements for the parameter name, you should enter a name that is easy to remember and meaningful (for example, ''location'' or ''location_guid''). Make note of this parameter name since it will used in a later step.
+
| Land || Land Device
|}
 
 
 
<ol start="4">
 
<ol type="a" start="2">
 
<li>Click the '''OK''' button.</li>
 
<li>Close the window that displays the list of all parameters.</li>
 
</ol>
 
</ol>
 
 
 
====Part 4. Create a query in the sub-report to associate the guid to the location report====
 
 
 
{| class="wikitable"
 
 
|-
 
|-
| [[File:Note.jpg | 40px]] || The next part of the process for creating a report on locations and its associated items is to create a query that defines how the location and associated item are related in the IMSMA database.
+
| Accident || Accident Device
|}
 
 
 
<ol>
 
<li>From the '''Data''' menu, select '''Report Query'''.</li>
 
:The Report query window displays.
 
<li>From the Report query window:</li>
 
<ol type="a">
 
<li>Select ''ImsmaQuery'' from the '''Query language''' list.</li>
 
<li>In the field below the Query language list, enter location.guid = "$P{''ParameterName''}"</li>
 
where ''ParameterName'' is the name of the parameter that you created for the location guid.
 
</ol>
 
</ol>
 
 
 
[[Image:iRep20.png|center|500px|''Figure 20. Query for report on locations and associated items'']]
 
<div align="center">
 
''Figure 20. Query for report on locations and associated items''
 
</div>
 
 
 
<ol start="3">
 
<ol type="a" start="3">
 
<li>Click the '''OK''' button.</li>
 
:The Report query window closes.
 
</ol>
 
<li>Click the [[Image:iRepCompile.png]] button to compile the sub-report.</li>
 
</ol>
 
 
 
====Part 5. Add parameters to the location sub-report====
 
 
 
{| class="wikitable"
 
 
|-
 
|-
| [[File:Note.jpg | 40px]] || The next part of the process for creating a report on locations and its associated items is to update the location report to include the parameter that will be used to associate the location record to item records.
+
| Assistance || Assistance Given
|}
 
 
 
<ol>
 
<li>Display the location report by doing one of the following:</li>
 
*From the '''Window''' menu, select the name of the location report.
 
*Close the sub-report.
 
*Bring the location report to the foreground by double-clicking the location report name that is displayed in the Files pane.
 
<li>Double-click the sub-report box within the report.</li>
 
:A window displays four tabs (Common, Sub-report, Sub-report (Other), and All).
 
<li>From the window:</li>
 
<ol type="a">
 
<li>Select the Sub-report (Other) tab.</li>
 
<li>Click the '''Add''' button.</li>
 
:The Add/modify parameter window displays.
 
</ol>
 
<li>From the Add/modify parameter window:</li>
 
<ol type="a">
 
<li>In the '''Sub-report Parameter Name''' field, enter the parameter name that you used for the location.</li>
 
</ol>
 
</ol>
 
 
{| class="wikitable"
 
 
|-
 
|-
| [[File:Note.jpg | 40px]] || This is the parameter that you created previously.
+
| Task || Work Item
 
|}
 
|}
 +
</center>
  
<ol start="5">
+
The process for creating a report on a parent item and its children is the same as any other report/subreport relationship.  
<ol type="a" start="2">
 
<li>In the '''Default Value Expression''' field, enter ''$F{guid}''.</li>
 
<li>Click the '''OK''' button.</li>
 
</ol>
 
<li>Close the window with the four tabs.</li>
 
</ol>
 
  
====Part 6. Compile and execute the location report====
+
===Example Subreport Relationships===__NOEDITSECTION__
 
+
{| class="wikitable"
<ol>
+
| align="center" style="background:#f0f0f0;"|'''Main Report'''
<li>Ensure that the ''Location'' data source is selected from the list.</li>
+
| align="center" style="background:#f0f0f0;"|'''Subreport can be'''
<li>Click the [[Image:iRepCompile.png]] button to compile the report.</li>
+
| align="center" style="background:#f0f0f0;"|'''Value to Pass to Subreport'''
<li>Click the [[Image:iRepRun.png]] button to execute the report.</li>
+
| align="center" style="background:#f0f0f0;"|'''Report Query'''
:The report results displays.
 
</ol>
 
 
 
==Items with Data Subsets==
 
Certain items have subsets of data that are contained within them. For example, an MRE may have MRE details such as the MRE type, total audience, and percentage of women and men. The MRE details data requires the MRE to exist. Table 3. Parent/child relationships lists the items and the data subsets that depend on them.
 
 
 
<center>
 
{| class="wikitable" width="600"
 
 
|-
 
|-
| align="center" colspan="2" | '''Table 3. Parent/child relationships'''
+
| Location||Any Item with a Location||location guid||location.guid = "$P{ItemGUID}"
 
|-
 
|-
| width="150pt" | '''Parent item'''
+
| Any linked item||Any linked Item||Item guid (e.g. Land guid)||links.toGuid="$P{ItemGUID}"
| width="450pt" | '''Child item(s) which require the parent item'''
 
 
|-
 
|-
| Activity || Impact survey
+
| Activity||Impact survey or Interviewee||Activity guid||hazreduc.guid = "$P{ItemGUID}"
Interviewee
 
Organisation
 
Question
 
Vegetation removal
 
 
|-
 
|-
| Location || Accident
+
| Interviewee||Question||interviewee guid||interviewee.guid = “$P{ItemGUID}”
Land
 
Activity
 
Education
 
QM
 
Victim
 
 
|-
 
|-
| Education || Education details
+
| Task||Work Item||Task guid||task.guid = "$P{ItemGUID}"
 
|-
 
|-
| Victim || Received Education
+
| Any Item with Geospatial information||GeospatialInfo||geoSpatialInfos||guid IN $P{GeospatialInfoList}
|}
 
</center>
 
 
 
The process for creating a report on a parent item and its children is similar to the process for creating a report on locations and their associated items. The key difference is that the main report will contain the attributes of the parent item. The sub-report will contain the attributes for the child item. For example, if you were trying to create a report of MREs and their associated MRE details, the main report would contain the attributes for MRE and the sub-report would contain the attributes for MRE details.
 
 
 
====Part 1. Create a report with attributes for a parent item====
 
The first part of creating a report on a parent and its child items is to create a report which includes the attributes from the parent item you would like to include.
 
<ol>
 
<li>Ensure that the IMSMA server is started.</li>
 
<li>From the '''File''' menu, select '''Report Wizard'''.</li>
 
<li>From the '''Connection/Data Sources''' list, select the data source for the parent item.</li>
 
</ol>
 
 
 
{| class="wikitable"
 
 
|-
 
|-
| [[File:Note.jpg | 40px]] || Table 3. Parent/child relationships lists the items which may be selected as the parent item for a report.
+
| Geospatial Info||GeoPoint||GeospatialInfo guid||geospatialInfoGuid = "$P{ItemGUID}"
|}
 
 
 
<ol>
 
<li>Click the '''Next''' button.</li>
 
:The iReport Wizard, Step 2 window displays a list of attributes for the selected item.
 
<li>Select the attributes you would like to include for the parent item.</li>
 
<li>Click the '''Next''' button.</li>
 
:The window displays a list of the attributes that you have selected.
 
<li>Click the '''Next''' button.</li>
 
:The iReport Wizard, Step 3 window displays to allow you to group the report results.
 
<li>Because the report results for this exercise will not need to be grouped, click the '''Next''' button.</li>
 
:The iReport Wizard, Step 4 window displays to allow you to select the report layout.
 
<li>Select a layout option.</li>
 
<li>Click the '''Next''' button.</li>
 
:The iReport Wizard, Step 5 window displays.
 
<li>Click the '''Finish''' button.</li>
 
<li>Save the report.</li>
 
</ol>
 
 
 
====Part 2. Create a sub-report for the child item====
 
The next part of the process for creating a report on a parent and its child items requires you to create a sub-report within the parent item report.
 
 
 
<ol>
 
<li>Expand the detail section of the report by doing the following:</li>
 
<ol type="a">
 
<li>From the '''View''' menu, select '''Bands'''.</li>
 
<li>From the left pane, select ''detail''.</li>
 
<li>In the '''Band Height''' field that is in the right pane, increase the height of the detail section. At a minimum you will want to double the height.</li>
 
<li>Click the '''Apply''' button.</li>
 
:The height of the band increases based on the value that you entered.
 
</ol>
 
</ol>
 
 
 
{| class="wikitable"
 
 
|-
 
|-
| [[File:Note.jpg | 40px]] || You may also expand the height of the detail band by dragging the line that separates the detail section of the report and the page footer section down.
+
| Any item with devices||Item Device (e.g. AccidentDevice)||Item guid (e.g. Accident guid)||accident.guid = "$P{ItemGUID}" hazard.guid = "$P{ItemGUID}"
|}
 
 
 
<ol start="2">
 
<li>Click the [[Image:iRepCompile.png]] button to add a sub-report.</li>
 
:The cursor changes to a crosshair.  
 
<li>Click the detail section of the report.</li>
 
<li>While holding down the mouse button, drag the cursor to form the rectangle which will contain the sub-report.</li>
 
<li>Release the mouse button.</li>
 
:The window to create a new report or use an existing one displays.
 
<li>From the window:</li>
 
<ol type="a">
 
<li>Select the ''Create a new report'' option.</li>
 
<li>Click the '''Next''' button.</li>
 
:The How fill the sub-report screen displays.
 
</ol>
 
<li>From the window:</li>
 
<ol type="a">
 
<li>Select the data source for the child item from the '''Connection/Data Source''' list.</li>
 
<li>Click the '''Next''' button.</li>
 
:The window to select the attributes to include in the report displays.
 
</ol>
 
<li>From the window:</li>
 
<ol type="a">
 
<li>Select the attributes that you would like to include in the report.</li>
 
<li>Click the '''Next''' button.</li>
 
:The window to select a layout displays.
 
</ol>
 
<li>From the window to select a layout:</li>
 
<ol type="a">
 
<li>Select the layout option.</li>
 
<li>Click the '''Next''' button.</li>
 
:The window to specify the sub-report expression displays.
 
</ol>
 
<li>From the window to specify the sub-report expression:</li>
 
<ol type="a">
 
<li>Enter a name for the sub-report.</li>
 
<li>Click the '''Finish''' button.</li>
 
:The sub-report displays.
 
</ol>
 
</ol>
 
 
 
====Part 3. Add parameters to the sub-report====
 
The next part of the process for creating a report on a parent and its child items is to define parameters that will be used for passing the parent item guid between the sub-report and main report.
 
 
 
<ol>
 
<li>From the '''View''' menu, select '''Parameters'''.</li>
 
:The window displays the parameters.
 
<li>Click the '''New''' button.</li>
 
:The Add/modify parameter window displays.
 
<li>From the Add/modify parameter window:</li>
 
<ol type="a">
 
<li>In the '''Parameter Name''' field, enter a name for the parameter that will be used to identify the guid for the parent item.</li>
 
</ol>
 
</ol>
 
 
 
{| class="wikitable"
 
 
|-
 
|-
| [[File:Note.jpg | 40px]] || Although there are no requirements for the parameter name, you should enter a name that is easy to remember and meaningful. Make note of this parameter name since it will used in a later step.
+
| MRE||MREDetail||MRE guid||mre.guid = "$P{ItemGUID}"
|}
 
 
 
<ol start="4">
 
<ol type="a" start="2">
 
<li>Click the OK button.</li>
 
</ol>
 
<li>Close the window that displays the list of all parameters.</li>
 
</ol>
 
 
 
====Part 4. Create a query in the sub-report to associate the guid to the parent item report====
 
The next part of the process for creating a report on locations and its associated items is to create a query that defines how the location and associated item are related in the IMSMA database.
 
 
 
<ol>
 
<li>From the '''Data''' menu, select '''Report Query'''.</li>
 
:The Report query window displays.
 
<li>From the Report query window:</li>
 
<ol type="a">
 
<li>Select ''ImsmaQuery'' from the '''Query language''' list.</li>
 
<li>In the field below the Query language list, enter ''ParentItem''.guid = "$P{''ParameterName''}"</li>
 
where ''ParentItem'' is the default value expression for the parent item and ''ParameterName'' is the name of the parameter that you created for the parent item guid.
 
<li>Click the '''OK''' button.</li>
 
:The Report query window closes.
 
<li>Click the [[Image:iRepCompile.png]] button to compile the sub-report.</li>
 
</ol>
 
</ol>
 
 
 
====Part 5. Add parameters to the parent report====
 
The next part of the process for creating a report on a parent and its child items is to update the parent report to include the guid attribute and parameters that will be used to associate the parent item to the child item.
 
 
 
<ol>
 
<li>Display the parent item report by doing one of the following:</li>
 
*From the Window menu, select the name of the report.
 
*Close the sub-report.
 
*Bring the parent item report to the foreground by double-clicking the report name that is displayed in the Files pane.
 
<li>Double-click the sub-report box within the report.</li>
 
:A window displays four tabs (Common, Sub-report, Sub-report (Other), and All).
 
<li>From the window:</li>
 
<ol type="a">
 
<li>Select the Sub-report (Other) tab.</li>
 
<li>Click the Add button.</li>
 
:The Add/modify parameter window displays.
 
</ol>
 
<li>From the Add/modify parameter window:</li>
 
<ol type="a">
 
<li>In the Sub-report Parameter Name field, enter the parameter name that you used for the parent item guid.</li>
 
</ol>
 
</ol>
 
 
 
{| class="wikitable"
 
 
|-
 
|-
| [[File:Note.jpg | 40px]] || This is the parameter that you created in step previously.
+
| Victim||Needs Assessment||victim guid||victim.guid="$P{ItemGUID}"
|}
 
 
 
<ol start="5">
 
<ol type="a" start="2">
 
<li>In the '''Default Value Expression''' field, enter ''$F{guid}''.</li>
 
<li>Click the '''OK''' button.</li>
 
</ol>
 
<li>Close the window with the four tabs.</li>
 
</ol>
 
 
 
====Part 6. Compile and execute the parent item report====
 
<ol>
 
<li>Ensure that the data source for the parent item is selected from the list.</li>
 
<li>Click the [[Image:iRepCompile.png]] button to compile the report.</li>
 
<li>Click the [[Image:iRepRun.png]] button to execute the report.</li>
 
:The report results displays.
 
</ol>
 
 
 
==Reports on Linked Items==
 
Part 4 of this training module discussed direct relationships—relationships where the parent item must exist in order for the child item to exist. In this part of the training, you will learn about linked relationships. Linked relationships are optional relationships which may exist between items. Unlike direct relationships that are enforced during the IMSMA reconciliation process, links are optional. Accidents, lands, activities, educations, and QMs may be related to one another via ''links''. For example, a victim may be associated to an accident in a particular land. If these relationships are known, IMSMA users may define these links while reconciling the field report.
 
 
[[Image:iRep21.png|center|500px|''Figure 21. Direct relationships vs. Links'']]
 
<div align="center">
 
''Figure 21. Direct relationships vs. Links''
 
</div>
 
 
 
The process for creating a report on an item and its linked items is similar to the process for creating a report on items with a direct relationship. The item in the main report is the primary item for which you would like to find linked items. The sub-report would return the records for the particular item that is linked to the primary item. The key difference is the query used in the sub-report.
 
 
 
If you would like to report on different items that linked to the item in the main report, you may create a new sub-report for each linked item. For example, to create a report of lands and the accidents and activities that are linked to those lands, you would create the main report on lands. This report would then contain a sub-report to list linked accidents, and another sub-report to list linked activities.
 
 
 
====Part 1. Create a report with attributes for a primary item====
 
The first part of creating a report on linked items is to create a report which includes the attributes from the primary item for which you would like to list linked items.
 
 
 
<ol>
 
<li>Ensure that the IMSMA server is started.</li>
 
<li>From the '''File''' menu, select '''Report Wizard'''.</li>
 
<li>From the '''Connection/Data Sources''' list, select the data source for the primary item.</li>
 
</ol>
 
 
 
{| class="wikitable"
 
 
|-
 
|-
| [[File:Note.jpg | 40px]] || Table 3. Parent/child relationships lists the items which may be selected as the primary item for a report.
+
| Victim||Cause||victim guid||victim.guid="$P{ItemGUID}"
|}
 
 
 
<ol start="4">
 
<li>Click the '''Next''' button.</li>
 
:The iReport Wizard, Step 2 window displays a list of attributes for the selected item.
 
<li>Select the attributes you would like to include for the primary item.</li>
 
<li>Click the '''Next''' button.</li>
 
:The window displays a list of the attributes that you have selected.
 
<li>Click the '''Next''' button.</li>
 
:The iReport Wizard, Step 3 window displays to allow you to group the report results.
 
<li>Because the report results for this exercise will not need to be grouped, click the '''Next''' button.</li>
 
:The iReport Wizard, Step 4 window displays to allow you to select the report layout.
 
<li>Select a layout option.</li>
 
<li>Click the '''Next''' button.</li>
 
:The iReport Wizard, Step 5 window displays.
 
<li>Click the '''Finish''' button.</li>
 
<li>Save the report by doing one of the following:</li>
 
*Click the [[Image:iRepSave.png]] icon.
 
*From the File menu, select '''Save'''.
 
::The Save report window displays.
 
<li>Enter a name for the report in the File name field.</li>
 
<li>Click the '''Save''' button.</li>
 
</ol>
 
 
 
====Part 2. Create a sub-report for the linked item====
 
The next part of the process for creating a report on linked items requires you to create a sub-report for the item to which the primary item is linked.
 
 
 
<ol>
 
<li>Expand the detail section of the report.</li>
 
<li>Click the [[Image:iRepBand.png]] button to add a sub-report.</li>
 
:The cursor changes to a crosshair.
 
<li>Click the detail section of the report.</li>
 
<li>While holding down the mouse button, drag the cursor to form the rectangle which will contain the sub-report. </li>
 
<li>Release the mouse button.</li>
 
:The window to create a new report or use an existing one displays.  
 
<li>From the window:</li>
 
<ol type="a">
 
<li>Select the ''Create a new report'' option.</li>
 
<li>Click the '''Next''' button.</li>
 
:The How fill the sub-report screen displays.
 
</ol>
 
<li>From the window:</li>
 
<ol type="a">
 
<li>Select the data source for the child item from the '''Connection/Data Source''' list.</li>
 
<li>Click the '''Next''' button.</li>
 
:The window to select the attributes to include in the report displays.
 
</ol>
 
<li>From the window:</li>
 
<ol type="a">
 
<li>Select the attributes that you would like to include in the report.</li>
 
<li>Click the '''Next''' button.</li>
 
:The window to select a layout displays.
 
</ol>
 
<li>From the window to select a layout:</li>
 
<ol type="a">
 
<li>Select the layout option.</li>
 
<li>Click the '''Next''' button.</li>
 
:The window to specify the sub-report expression displays.
 
</ol>
 
<li>From the window to specify the sub-report expression:</li>
 
<ol type="a">
 
<li>Enter a name for the sub-report.</li>
 
<li>Click the '''Finish''' button.</li>
 
:The sub-report displays.
 
</ol>
 
</ol>
 
 
 
====Part 3. Add the parameters to the sub-report====
 
The next part of the process for creating a report on linked items is to define parameters that will be used for passing the guid of the primary item between the sub-report and main report.
 
 
 
<ol>
 
<li>Click the '''New''' button.</li>
 
:The Add/modify parameter window displays.
 
<li>From the Add/modify parameter window:</li>
 
<ol type="a">
 
<li>In the '''Parameter Name''' field, enter a name for the parameter that will be used to identify the guid for the primary item.</li>
 
</ol>
 
</ol>
 
 
 
{| class="wikitable"
 
 
|-
 
|-
| [[File:Note.jpg | 40px]] || Although there are no requirements for the parameter name, you should enter a name that is easy to remember and meaningful. Make note of this parameter name since it will used in a later step.
+
| Assistance||Assistance Given||victimAssistance.guid||victimAssistance.guid="$P{ItemGUID}"
|}
 
 
 
<ol start="3">
 
<ol type="a" start="2">
 
<li>Click the '''OK''' button.</li>
 
</ol>
 
<li>Close the window that displays the list of all parameters.</li>
 
</ol>
 
 
 
====Part 4. Create a query in the sub-report to associate the guid to the primary report item====
 
The next part of the process for creating a report on linked items is to create a query that defines how the primary item and the linked item are related in the IMSMA database.
 
 
 
<ol>
 
<li>From the '''Data''' menu, select '''Report Query'''.</li>
 
:The Report query window displays.
 
<li>From the Report query window:</li>
 
<ol type="a">
 
<li>Select ''ImsmaQuery'' from the '''Query language''' list.</li>
 
</ol>
 
</ol>
 
 
 
{| class="wikitable"
 
 
|-
 
|-
| [[File:Note.jpg | 40px]] || The following query is different from the query used when creating a report on items with data subsets.
+
| Task||Objective||SQL Field list of Objectives||guid IN ($P{SQLList})
|}
 
 
 
<ol start="3">
 
<ol type="a" start="2">
 
<li>In the field below the Query language list, enter links.toGuid = "$P{''ParameterName''}"</li>
 
where ''ParameterName'' is the name of the parameter that you created for the parent item guid.
 
<li>Click the '''OK''' button.</li>
 
:The Report query window closes.
 
</ol>
 
<li>Ensure that the Query Executor data source is selected from the list.</li>
 
<li>Click the  button to compile the sub-report.</li>
 
</ol>
 
 
 
====Part 5. Add attributes and parameters to the main report====
 
The next part of the process for creating a report on linked items is to update the main report to include the guid attribute and parameters that will be used to associate the primary item to the linked item.
 
 
 
<ol>
 
<li>Display the main report by doing one of the following:</li>
 
*From the '''Window''' menu, select the name of the report.
 
*Close the sub-report.
 
*Bring the primary item report to the foreground by double-clicking the report name that is displayed in the Files pane.
 
<li>Double-click the sub-report box within the report.</li>
 
:A window displays four tabs (Common, Sub-report, Sub-report (Other), and All).
 
<li>From the window:</li>
 
<ol type="a">
 
<li>Select the Sub-report (Other) tab.</li>
 
<li>Click the '''Add''' button.</li>
 
:The Add/modify parameter window displays.
 
</ol>
 
<li>From the Add/modify parameter window:</li>
 
<ol type="a">
 
<li>In the '''Sub-report Parameter Name''' field, enter the parameter name that you used for the primary report item guid.</li>
 
</ol>
 
</ol>
 
 
 
{| class="wikitable"
 
 
|-
 
|-
| [[File:Note.jpg | 40px]] || This is the parameter that you created previously.
+
| Work Item||Linked Items (Activity, Education, QM, Assistance)||SQL Field list of Items||guid IN ($P{SQLList})
 
|}
 
|}
 
+
{{NavBox HowTo Standardizing Data Analysis and Information Reporting}}
<ol start="5">
+
[[Category:NAA]]
<ol type="a" start="2">
 
<li>In the '''Default Value Expression''' field, enter ''$F{guid}''.</li>
 
<li>Click the '''OK''' button.</li>
 
</ol>
 
<li>Close the window with the four tabs.</li>
 
 
 
====Part 6. Compile and execute the main report====
 
<ol>
 
<li>Ensure that the data source for the item in the main report is selected from the list.</li>
 
<li>Click the [[Image:iRepCompile.png]] button to compile the report.</li>
 
<li>Click the [[Image:iRepRun.png]] button to execute the report.</li>
 
:The report results displays.
 
</ol>
 
 
 
</ol>
 
{{NavBox HowTo use iReport}}
 

Latest revision as of 20:32, 20 February 2020

Creating Subreports

A subreport is a report within a report; thus, providing a way to generate a report that includes data on the target IMSMA item as well as data on other IMSMA items that are associated to the target IMSMA item. Generally a subreport is used in a situation where you have one or more sets of data relating to a single IMSMA item. A common use case would be a Location report with multiple details bands of different IMSMA items (Land, Activity, Accident, Victim, Education, and QM).

Regardless of what IMSMA data you’re including in your report and subreports, there are 5 basic steps to create a report with subreports:

Step 1 – Create the main report
Step 2 – Add a subreport to the main report
Step 3 – Add a parameter to the subreport
Step 4 – Define the report query for the subreport
Step 5 – Add subreport parameter to the main report

Step 1 – Create the Main Report

Before creating the main report, you will need to determine what data should be included in your report. For example, if you are creating a report about Land with all the Progress Report data, then the target IMSMA item for your main report should be Land and the target data for your subreport should be Activity assuming that Progress Reports are entered into the system as Activity. Below is a list of questions and things to be considered when designing a report.

  • What are all the data to be included on the report?
  • What is the target IMSMA item for the main report? This is the primary data of your report.
  • What is the target IMSMA item for the subreports? This is the secondary data of your report.
  • Determine the relationship between the primary data and the secondary data. How did they get reconciled to one another? How are they linked?

The main report should be created with the IMSMA item determined to be the primary data of your report. The main report is just a basic report and can be created using the steps provided in the Create a Basic iReport Template section.

Step 2 – Add Subreport to the Main report

Once the main report has been created you can add a subreport to the main report. The intent of the subreport is to bring data from a different but related datasource into the main report. For example, you could include Activity data on a report about Land. Below are the instructions to create a subreport:

  1. On the main report, from the Palette pane, select Subreport and drag it to the desired band on the iReport template (normally this is the Detail band).
    Subreport Palette
    Subreport Palette
  2. Release the button and the window below displays.
    Add Subreport to the Main report
  3. Click Next to define a new subreport unless you have an existing report that you would like to use for subreport.
  4. Select the desired iReport Template to apply (Blank is recommended).
    Select the desired iReport Template
  5. Select from the Connection/Data Source list. This should be the IMSMA item determined as the secondary data of your report. For example, if you are creating a report about Land with Progress Reports, then “Hazard Reduction” should be the data source for the subreport. Click Next.
    Select the desired datasource
  6. Select the attributes to be included in your subreport. Click Next.
    Select the desired fields for the subreport
  7. Select the fields to group by. This step is not required. Click Next.
    Select the fields to group by
  8. Enter a name for the subreport or use the default. Choose Next.
    Enter a name for the subreport
  9. Select Use the same connection used to fill master report. Click Finish.
    Use same connection
  10. The subreport displays.

Step 3 – Add Parameter to Subreport

To connect a subreport to the main report, we next need to create a parameter for passing the identification (guid) of the primary IMSMA item between the subreport and the main report. In the Report Inspector on the subreport, add a Parameter to hold the guid of the IMSMA item on the main report. It is recommended to add a fairly generic parameter name such as ItemGUID so that the subreport can be more easily re-used.

  1. From the Report Inspector, right click on the Parameter tree and choose Add Parameter.
    Add Parameter
  2. In the Properties pane, enter a parameter name (e.g. ItemGUID} and edit any other properties. Normally it is not required to edit anything other than the name, you might however want to deselect the Use as a prompt option.
    Add Parameter
  3. Once the parameter is added it will be available in the Report Inspector and can be referenced as $P{parametername}. For example:
$P{ItemGUID}

Step 4 – Define Report Query for Subreport

The next step is to create a report query for the subreport you just created in Step 2 to define how the IMSMA item on the main report is related to the IMSMA item on the subreport. Typically the subreport report query will receive the guid from the main report via the parameter created in Step 3 and then use it to limit items in the subreport to those linked to the main report. Below is the instructions on how to define the report query:

  1. Open the report query window.
  2. From the report query window, select ImsmaQuery from the query language list.
  3. Enter a report query filter using the parameter defined above to limit the objects according to the main report object. The most common report query filter would be to filter to only linked objects. For example links.toGuid="$P{ItemGUID}". In this step, the Report Query tells the subreport to return only rows that are linked to the guid of the item in the main report via the link table. Other combinations of report query filters can be used on subreports beyond the link table. These are documented in the Possible Subreport Relationships section below.
  4. Click OK. The report query window closes.
  5. Save the subreport.

Step 5 – Link the Subreport to the Main Report

Now that both the main and the subreport are ready, the only thing that remains to be done is linking the two together. Below are the instructions to link the two reports:

  1. Make sure you are at the main report by selecting the name of the main report from the tabs at the top of the iReport Designer canvas pane.
  2. Select the subreport box within the main report.
    Select the Subreport on the main report
    Select the Subreport on the main report
  3. On the Properties pane for the Subreport, select the Parameter selector.
    Subreport properties
    Subreport properties
  4. Add a parameter and type exactly the name of the subreport parameter created in step 3 (e.g. ItemGUID)
    Add a parameter
    Add a parameter
  5. For the value expression, select the appropriate field to include in the parameter. Normally this is $F{guid} but other choices are available.
    Select the appropriate field
    Select the field to include in the parameter
  6. Click OK and close Subreport Parameters window.

You are now ready to run your main report. Running (i.e. previewing) the main report will automatically run the subreport(s) as well, and the data from the main as well as from the subreport(s) will be included in the output.

Kinds of Subreports

There are three main kinds of relationships in IMSMA on which subreports can be generated from IMSMA data. These are:

  • Location relationship
  • Link relationship
  • Geospatial relationship
  • Other relationship

Location relationship subreports

Because each of the main items in IMSMANG, Accident, Activity, Assistance, Education, Land, QM, and Victim, must be reconciled to a Location during the data entry phase, each of these objects has a relationship with Location and can thus be a subreport on a Location main report. Since all accidents, land, activities, educations, QMs, assistances, and victims are associated with a single location each record knows what location it is related to based on the location guid field. When creating a report where the main report is a Location and the subreport is one of the associated objects the Location's guid is passed to the subreport in a parameter and the subreport can use a special ImsmaQuery language syntax to limit the subreport data to those associated with the main report's location:

location.guid = "$P{parametername}"

The location guid field in the subreport item table contains the guid of the location to which the item record is associated. The figure below shows an example of a location and the accident and land that are associated to the location. Notice that the location_guid value (1234-1234) in the accident and land are identical to the location_guid of the location.

location_guid example

location_guid example

To create a subreport using the Location relationship:

  1. From the main "Location" report, pass the location guid to the subreport in a parameter (e.g. in a parameter called ItemGUID).
  2. Create a parameter on the subreport with the same name as in #1.
  3. In the subreport for the related item (e.g. a Victim) use the parameter in the following ImsmaQuery language syntax
location.guid="$P{parametername}"

This has the effect of limiting the subreport records to only those records that are associated to the location from the main report.

Link relationship subreports

In addition to the Location relationship, the main items in IMSMANG can also be linked with one another during the reconciliation process. This is how, for example, Activities are linked with Land in the IMSMANG database. Accidents, land, activities, educations, assistances, QMs, and victims may be related to one another via links. For example, a victim may be associated to an accident in a particular land. If these relationships are known, IMSMA users may define these links while reconciling the Data Entry Form. This special relationship can also be modeled in iReport using a report and subreport(s).

The process for creating a report on an item and its linked items is similar to the process for creating a report on items with a Location relationship. The item in the main report is the primary item for which you would like to find linked items. The subreport would return the records for the particular item that is linked to the primary item. The key difference is the query used in the subreport.

To create a subreport using the link relationship:

  1. From the main report, pass the guid of the main report object to the subreport in a parameter (e.g. pass an accident's guid in a parameter called ItemGUID).
  2. Create a parameter on the subreport with the same name as in #1.
  3. In the subreport for the related item (e.g. a Victim) use the parameter in the following ImsmaQuery language syntax
links.toGuid="$P{parametername}"

This has the effect of limiting the subreport records to only those records that have a link to the guid or object passed from the main report.

Geospatial relationships

In addition to Location and Link relationships, many objects in IMSMA can store geospatial/geographic information (i.e. point/polygon information). This relationship with the geospatial data can be modeled in a report/subreport relationship for any item that has geospatial information associated with it. To include point/polygon information on an object's main report, follow 3 basic steps:

  • Step 1: Create a main report for an object with geospatial info
  • Step 2: Create a GeospatialInfo subreport on the main report, i.e. a report using the GeospatialInfo datasource
  • Step 3: Create a Geopoint subreport on the GeospatialInfo report, i.e. a report using the Geopoint datasource

Step 1: Create a main report for an object with geospatial info

  • Create a main report with an object that has geospatial information (e.g. Land).
  • Ensure that the geospatialInfos field is added to the main report.

Step 2: Create a GeospatialInfo subreport on the main report

  • On the main report, add a subreport using the GeospatialInfo datasource
  • Pass the geospatialInfos field to the subreport in a parameter (e.g. GeospatialInfoList). Note: instead of passing the $F{guid} field to the parameter, the parameter value should be $F{geospatialInfos}
  • In the GeospatialInfo subreport use the parameter in the following ImsmaQuery language syntax
guid IN $P{parametername}

Step 3: Create a Geopoint subreport on the GeospatialInfo report

  • On the Geospatialinfo subreport, add a subreport using the Geopoint datasource
  • Pass the guid field to the subreport in a parameter (e.g. GeospatialGUID). Note: Pass the $F{guid} field NOT the $F{geospatialInfos} value.
  • In the Geopoint subreport use the parameter in the following ImsmaQuery language syntax
geospatialinfoguid IN $P{parametername}

This has the effect of limiting the Geospatial records to only those records whose guid is linked to the geospatialinfo of the main report. This is an example of nested reports, i.e. a main report, a subreport, and a sub-subreport.

Other subreport relationships

Certain items in IMSMANG have subsets of data that are contained within them. For example, an education may have education details such as the education type, total audience, and percentage of women and men. Examples of other subreport relationships include:

Other subreport relationships
Parent item Child item(s)
Activity Activity Device

Impact survey

Interviewee

Question

Education Education details
Victim Received Education

Needs Assessment

Cause

Land Land Device
Accident Accident Device
Assistance Assistance Given
Task Work Item

The process for creating a report on a parent item and its children is the same as any other report/subreport relationship.

Example Subreport Relationships

Main Report Subreport can be Value to Pass to Subreport Report Query
Location Any Item with a Location location guid location.guid = "$P{ItemGUID}"
Any linked item Any linked Item Item guid (e.g. Land guid) links.toGuid="$P{ItemGUID}"
Activity Impact survey or Interviewee Activity guid hazreduc.guid = "$P{ItemGUID}"
Interviewee Question interviewee guid interviewee.guid = “$P{ItemGUID}”
Task Work Item Task guid task.guid = "$P{ItemGUID}"
Any Item with Geospatial information GeospatialInfo geoSpatialInfos guid IN $P{GeospatialInfoList}
Geospatial Info GeoPoint GeospatialInfo guid geospatialInfoGuid = "$P{ItemGUID}"
Any item with devices Item Device (e.g. AccidentDevice) Item guid (e.g. Accident guid) accident.guid = "$P{ItemGUID}" hazard.guid = "$P{ItemGUID}"
MRE MREDetail MRE guid mre.guid = "$P{ItemGUID}"
Victim Needs Assessment victim guid victim.guid="$P{ItemGUID}"
Victim Cause victim guid victim.guid="$P{ItemGUID}"
Assistance Assistance Given victimAssistance.guid victimAssistance.guid="$P{ItemGUID}"
Task Objective SQL Field list of Objectives guid IN ($P{SQLList})
Work Item Linked Items (Activity, Education, QM, Assistance) SQL Field list of Items guid IN ($P{SQLList})