RDL Reports

<< Click to Display Table of Contents >>

Navigation:  Professional > Reports >

RDL Reports

EQuIS supports RDL (Report Definition Language) reports. RDL is the XML markup language used in Microsoft SQL Server Reporting Services (SSRS). RDL reports may use a variety of data visualizations and other logic to display data. Using RDL reports in EQuIS does not require Microsoft SQL Server Reporting Services, however, it does require a third-party RDL editing application (e.g. Microsoft SQL Server 2014 Report Builder) to design the RDL reports.


Note: This documentation is not intended to provide information on the technical capabilities of RDL or third-party design tools. EQuIS should be installed using .exe file in order to have this feature available.


Data Sources


Generic RDL allows for a variety of data sources, including a direct connection to common relational database systems such as Microsoft SQL Server. When designing or viewing RDL reports in EQuIS, the database connection information is intentionally omitted from the RDL. This omission is intentional and is designed to prevent unauthorized access to your EQuIS Database. Explicitly including the database connection information within the RDL would allow users to circumvent EQuIS application-level security. RDL generated by EQuIS will contain a Data Source with the database name, but that is the only information that will be included.




Generic RDL allows for a variety of datasets, including SQL queries executed directly against the database. EQuIS does not support (and will not execute) RDL reports that contain direct SQL queries. Executing direct SQL queries would allow users to circumvent EQuIS application-level security. Instead, RDL generated by EQuIS will contain a dataset that references another EQuIS report (e.g. Analytical Results) that produces tabular data (i.e. EarthSoft.Common.Reports.IGridReport). The table of data produced by the underlying report is fed into the RDL dataset as the report is rendered.


Not only does referencing an underlying EQuIS report maintain security, it also gives more power and flexibility (as opposed to writing direct SQL queries). For example, using the Analytical Results Report as a dataset in an RDL report gives the full functionality of that report (e.g. unit conversions, non-detect multiplier/symbol, etc.). Another example is using the Action Level Exceedance Report as a dataset in an RDL report, which gives the powerful logic of flagging exceedances, with the visualization flexibility provided by RDL.


If you need to use a specific SQL query as the dataset in a RDL report, ask your EQuIS administrator to publish the SQL query (*.sql) as a report, and use that report as the dataset in your RDL report.