Once you know that the views you need are available, you’re ready to set-up a new report.  To do this, click back to the Reports App on the left navigation.  You will see a list of existing reports.  If you have the Report Configurator role you will also be able to create a new report.


Click ‘Add global report’, enter a name and click OK.  The first report set-up form opens.  In this form you must:


  • Enter a name and description for your report
  • Select the report type


There are four types of reports available:


  • Performance report - This is a custom report for the Performance App.  This App is designed to record indicator data in a shared log frame or results framework.
  • Data object - This is the primary report type you will use to export data from forms.
  • JRXML (Custom layout) - This option allows you to embed a custom report that has been manually created (ie not set up using this App) in the Reports App.  It enables your colleagues to run a custom report in the same way as reports created with the App
  • JRXML (Automated layout) - This is the same as the data object report, except that it allows you to upload your own custom template.  This can be used to display your own header, footer and styling in the report.


Save the form and open the next form in the workflow.


This form has two questions:


Context - You may select approved (ie only data that has the status approved) or pending (ie data in an App, but not yet approved)

Views - This menu allows you to select one or more views.  Select all the views you need for your report here.


Save the form and open the next form in the workflow.


The views you selected are shown at the top of this form.  If you selected more than one view, you must now specify how the different views will be joined.


The data dictionary has a number of ID fields that can be used to join data from different views.  In most cases there are two scenarios:


  • You have views that extract data from different forms in the same App.  In this case you should join the views using the profile ID.  This ensures that all forms in the same profile are connected.
  • You have views that extract data from the primary view and repeat views in the same form.  In this case you should join the views using the Document ID.  Remember, if you have a view for another form, you must also join the primary view to this form via the profile ID
  • You have views that extract data from forms in two different Apps.  This is more complex and depends on the relationship between the two Apps.  The most common scenario here is that one App has a form with a taxonomy that shows a list of profiles from the other App.  In this case you will join using the code for that taxonomy to the profile ID for the other App.


In the view table you can select the following:


  • Left view - choose from the views you previously selected the first one.  Normally the left view will be the one showing the profile name.
  • Left field - choose the field from that view you will join by
  • Join type - you may choose from three options:
    • Inner - this shows data only where it is present in both the left view and the right view
    • Left - this shows all data from the left view, but only shows data from the right view where it is present
    • Full - this shows all data from both views, even if it is not present in one view or the other
  • Right view - choose the right view
  • Right field - choose the field from that view you will join by


In your final step, you will choose which fields from the views you wish to include on the report.  Remember to select them in the order you wish them to appear.  The first row will be the first column and so on.  For each field you can select the column header (ie the label) you wish to appear on the report.