||The module comes with two standard skins - the DnnBro blue skin and a grey skin. If the module should adapt to your specific color scheme a custom skin can be chosen - and you can define the colors of the module (see guide for details).
||Define your own header for the table. The header name will also be used as the filename if download the table as a CSV file.
|Enable or Disable download option
||From the settings you can define whether the download button should be visible to the user. Determined on each use of the module in case some tables are to be downloaded and others not.
||Determine if the builtin SQL connection from DNN should be used, a stand alone connection for this module only or a shared connection between all instances of this module across the installation. Be careful about the last one if this installation have multiple sites, as it is shared across all sites.
If stand alone or shared connection is chosen you must fill in which SQL server to connect to and provide a username and password. A button for testing the connection is available to ensure the provided information is correct.
All passwords will be saved encrypted in the database for added security.
||Two SQL execution types are supported. Use Text for SELECT statements and StoredProcedure if you have a stored procedure to call (without parameters).
If you need to call a stored procedure with parameters you can choose the Text option and type: EXEC StoredProcedureName @Param1, @Param2, etc.
||Resizeable textbox for entering the SQL to execute
|Test SQL Execution
||A button for testing the SQL execution is available so the settings can be tested before updating the site.
Can be relevant in a production site where you need to know whether the entered SQL will work.
|Disable options in web.config
||If needed some of the available SqlConnectionTypes or SqlExecutionTypes can be disabled. This could be a relevant scenario in a multisite environment where the shared between all type is not desired – or if the individual site users are not allowed to use the built-in SQL connection.
To adjust which connection types and execution types are available the web.config file must be altered manually.