They can be accessed through the Reports drop-down menu on the grid view of you dataset, or directly from the Data Views web part. Reports are saved on the LabKey Server, not on your local file system. When your script is complete and report is satisfactory, return to the Source tab, scroll down, and click Save to save both the script and the report you generated.Ī saved report will look similar to the results in the design view tab, minus the help text. This can be a helpful resource as you write or refine your script. Select the data tab to see the data on which your R report is based. If the pipeline option is not selected, the script will be run in batch mode on the server. When you select the Report tab, you'll see the resulting graphics and console output for your R report. Notice the options available below the source entry panel, describe below. Enter the R script for execution or editing into the Script Source box. The R report builder opens on the Source tab which looks like this. By default, R reports not associated with a grid are listed under the Uncategorized heading in the list on the Manage Views page. For details on using Rlabkey, see Rlabkey Package. R reports that pull data from additional tables (other than the associated grid) must use the Rlabkey API to access the other table(s). R reports created independently of grids do not have access to labkey.data objects. R reports associated with a grid automatically load the grid data into the object "labkey.data".