...
1 | Listed options under Report Design Manager page. | |
2 | This type of renderer should always be a default output option for any user-defined report. | |
3 | Expected output |
Delimited Text Report Renderer
The Report Designs section has two types of Delimited Text Report Renderer: CSV Report Renderer and TSV Report Renderer and they share the following characteristics:
- Both handle multiple data set definitions. If only one Data Set Definition is used then the final output will be a cvs, tsv or a user-defined file extension file. In case that the Report Definition has more than one data set, then the output will be a zip containing all of the delimited text files (csv, tsv or user-defined) for each data set (see examples below).
- The user can easily change what delimiters should be used when rendering the data. Please keep reading to learn more about this.
CSV Report Renderer
This comma-separated value renderer will allow you to export the data of your report to a flat file suitable for importing into Excel, SAS or another external analysis tool. The main characteristics of this renderer are:
...
- It allows you to change the filename extension of the final file.
- Even when the output is pre-configured to be a comma-separated value file, the user can change both the field delimiter and text delimiter (see examples below).
1 | Select the CSV option from the drop-down list and click on the Add another button. | |
2 | On the configuration page, only the description field is optional. The filename extension, field delimiter and text delimiter fields have default values. | |
3 | If you run your report, the new added design will appear as an output option of the Report Definition you previously linked it to and it will be added to the list displayed on the Report Designs Manager page as well. | |
4 | Running the same report used earlier in the Default Web Renderer example, the expected output should be a file with csv extension containing columns separated by a comma and with a text delimiter which is the closing quotation mark (the text delimiter is the character that follows a field, in this example the field is composed of the opening quotation mark and the word: type). | |
5 | Now let's say you would like your fields to be separated by a dash, then you would have to modify the field delimiter like this: | |
6 | Then the expected output file is a character-separated value (the character is a dash).value (the character is a dash). | |
7 | In case that your report has more than one Data Set Definition, then the output will be a zip of delimited text files (csv files for this example). |
TSV Report Renderer
There’s not much difference between the CSV and TSV (tab-separated value) renderers, both share the same characteristics. The main discrepancy is that the user cannot change the field delimiter value which always will be a Tab. The filename extension and the text delimiter are the only fields that can be modified.
1 | The Field Delimiter value will always be a Tab. | |
2 | If you run your report, the new added design will appear as an output option of the Report Definition you previously linked it to and it will be added to the list displayed on the Report Designs Manager page as well. | |
3 | The expected output is a file with tsv extension and the columns are separated by a tab with a text delimiter which is the closing quotation mark (the text delimiter is the character that follows a field, in this example the field is composed of the opening quotation mark and the word: type). | |
4 | In case that your report has more than one Data Set Definition, then the output will be a zip of delimited text files (tsv files for this example). |
HTML Report Renderer
It is a very basic renderer that produces an HTML file that contains the data of your report. Its main characteristics are:
...
Section | Configuration and Access Information | Examples | |||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Expressions |
Both will help to identify in the template pieces of text that are expected to be replaced with data. | If you stick with the default values, then everything that is between the # character will be replaced: #myDataset.myValue# You can change to the Suffix and Prefix to be an character, for example the $ character, then you should be able to access your data in your template this way: $myDataset.myValue$ | |||||||||||||||||||||||||||||||||||
Repeating Sections | The output data of your report might have rows and columns of information instead of just having one single value. If this is your case, then you should configure Repeating Sections to access all of your rows and/or columns. As a side note, if the data of your report has a lot of rows and columns, might be possible that the XLS Report Renderer is more suitable for you. The following options literally mean if a sheet | row | column should be repeated in a template.
| For the following examples let's assume that our report output the following table using the encountersByType key as name for the Data Set Definition:
| |||||||||||||||||||||||||||||||||||
Designing Properties | You can define any key-value property that your template might need.
|
| |||||||||||||||||||||||||||||||||||
Miscellaneous |
|
...