Report options

From Drillbridge Wiki
Jump to: navigation, search

Drill-through reports have many options that can be used to customize their output and behavior.


When turned on, multiple tables will be generated instead of one large table. The number of rows per table is defined by the BREAK_TABLES_ROWS option. Breaking up tables may improve rendering performance by some browsers, although if possible the result caching mechanism is preferred.


The maximum number of rows per table when then BREAK_TABLES option is turned on.


When turned on, an additional column is inserted on the report table that will have the row number, starting with 1. This option also applies to Excel reports.


When turned on, Drillbridge will inspect the return types from the relational database and attempt to format it as nicely as it can. This affects numbers, dates, and times. Drillbridge will apply the user's locale setting from their web browser to enhance formatting. For example, if the user's locale is DE (German [Deutsch]), then the proper date formatting and thousands/decimal separators will be used.


When turned on, an HTML page will not be generated, instead, a download to an Excel file with the results will be initiated (as if the user had clicked on the Excel button).


Instructs Drillbridge to use "Data Table" formatting. Best used with smaller tables (< 3000 rows). Allows for sorting data.


Fetch the original value (if possible) from the cube and display it at the top of the drill-through report.


When turned on, the advanced Drillbridge caching mechanism will be used to store the results of the drill-through operation so that the user can page through them without repeated trips back to the database.


Number of rows per page to show when using Result Caching.


Specify the method used to authenticate against the backend database. The default option is to use credentials that are setup in the database connection itself. Additional options are to use credentials from a prompt to to try and use the SSO token from the drill-through request.


Turn on to prompt the user for credentials (a username and password) before executing the report. In the case of the normal drill-through report, these credentials will then be used to connect to the relational database.