Stonefield Query Enterprise Version 5.0

We are pleased to announce the release of version 5.0 of Stonefield Query Enterprise. There are lots of new features in this release.

• Two factor authentication is now available for users that require additional security. You can enable it via a new tab in options.

• Improved loading times when initially opening a report for the first time.

• Administrator users can now specify that their email settings be used as the default settings. Any users that don't have email settings specified will use the default settings when sending emails.

• It's now much easier to create a SQL Passthrough report with parameters. Stonefield Query will detect each '?' placeholder in the SQL Statement and prompt for a caption and parameter value for it.

• User names with backslashes are now supported.

• When entering a server address for FTP, you can now optionally specify a ftp:// prefix if you'd like.

• The author and title properties are now set on generated Excel documents.

• Stonefield Query now supports multiple schedules with the same name (even across tenants).

• The user interface has several new progress indicators.

• The scheduler has a new "New schedule" button.

• When registering for a new user account, you can now choose the password rather than one being generated automatically.

• You now get a warning if you try to edit a report that is already being edited by another user.

• The properties dialog now includes the table each field is from to make fields with the same name easier to identify.

• The ask-at-runtime filter display now includes the connection for a filter condition.

• The ability to email and upload (to FTP) reports can now be restricted by role.

• The tooltip for a formula in the formulas list will display all reports a formula is being used in.

• A new button in step 2 of the report wizards will filter the list of tables to only those tables related to tables already appearing in the selected list.

• Stonefield Query is now built using ASP.NET Core. The new platform has a number of benefits, including greatly improved loading performance, the ability to self host, and support for additional hosting platforms.

• The Stonefield Query Enterprise installer no longer installs IIS Express since that's no longer needed. When testing a project locally from Stonefield Query Enterprise Studio, the new self-hosting option is used.

• Stonefield Query is now available in 64-bit and 32-bit versions, the latter necessary if you have to connect to a 32-bit data source. By default, the Launch Stonefield Query function in Stonefield Query Studio launches the 64-bit version, but if you want to be prompted for which version to use, turn on the Prompt For 32-bit vs 64-bit setting in the Options page.

• The Refresh dialog has a new Extended Logging option that, if turned on, performs additional diagnostic logging in case issues arise.

• External authentication via Open ID 2.0 is no longer supported, and has been replaced with Open ID Connect instead. In addition, you can also enable external authentication using Google, Twitter, Facebook, and Active Directory Federated Services.

• The Open Project dialog now has a text box so you can type a path if desired.

• If you use the SQL Server ODBC driver to connect to a database, you are now asked if you want to the use SqlClient provider instead, since it works better.

• The Select Table dialog now shows the type of each object: table, view, or "sproc" for stored procedure.

• If a table uses StoredProcedurePlugin as its plugin, you are prompted to refresh the table so the list of fields is correct.

• Added additional logging to various scenarios.

• A new provider is available for SQLite data sources.

• Field values retrieved from the database are now converted to the type stored in the data dictionary for that field.

• Added better support for field names that begin with a digit.

• A new configuration option is available to skip retrieving the schema for a query.

• You can now specify a complex join that includes additional tables in the join. This is useful if you need to specify a join that must always include a third table, for example.

• User themes are now loaded from an xml file (themes.xml). Add any additional themes to this file to make them available to the end user.

• Stonefield Query now supports encrypted query strings in the URL.