March 2024 - Dashboard Release Notes

Following on from other changes around Sub Totals, as introduced in the February 24 release, we are now introducing improvements to Totals and Sub Totals for Measures, using Averages.

To help explain this, imagine you have a table with:

1. A measure defined with AVG() or / in the select statement

2. A total type of average defined in the attributes on that table

Additional queries have been built to generate more accurate averages for the Grand Total and all Sub Totals on the table (Sub Totals being defined by the sub dimension breaks). This will obtain the accurate average value, taking the average of all values in the database - as opposed to the average of only what appears on the table.

The process generates 1 additional query for the Grand Total, and 1 additional query for each Sub Total you have defined. The additional queries for the Sub Totals follow a hierarchy from the left side to the right side of the table.

Open

In the example below, the Grand Total at the bottom would previously have been 33.866 without the new additional queries, as that is the average of all 5 rows in the table (excluding Sub Totals). That method however is not a representative of the averages of all rows in the database, so the additional queries now generate a more accurate average calculation, for the Grand Total & Sub Totals.

Open

Open

This feature is not currently configured to work with percentages. If you select the check display as percentage for the measure with this specific scenario, it will not change the result on the table.

Exports and Scheduled Report are now internationalised (i18n) in the same way as they are in the web product. The dashboard remembers the last used language for a user, and applies that to the export.

A new API endpoint (/users/all) has been added that obtain all of the users, not just those manageable by the authenticated user. To retrieve all of the users, the authenticated user must be either an Admin or have permission to schedule.

When attempting to delete a Theme, when pressing the ‘Delete’ button, if the theme is either being used by a User or set as the Global Theme, the deletion attempt will fail. An error stating which theme(s) cannot be deleted and if this is being used by a User or set as the Global Theme will be shown to help direct the user.

Previously, when attempting to run migrations against a MySQL 8 database without an ssl connection, the connection would fail. This was due to the MariaDB JDBC being used for both MySQL and MariaDB. We have now configured migrations with the MySQL JDBC driver should the user choose to do so. You can set it to be used in the config tool:

Open

Or in the docker dashboard Environment Variables with the following:

PI_DB_IS_MYSQL: "true"

We’ve released a new version of our out-of-the-box Dashboard for people using the product for the first time!

Open

Open

Open

A Horizontal Scroll Bar would appear over the top of the last row of data for several different table types, obscuring the data for that row - as shown below;

Open

This has been addressed for regular Table charts and also Merged, Editable or Rotated tables too.

We’ve reworked how non-secure variables are stored to significantly boost performance when you have a large number of them, whilst still protecting any secrets used for secure variables.

Tables with Additional Data, and Row and/or Column Totals enabled were failing to export to Excel, returning the error ‘There were problems downloading the Excel file’. This is now resolved.

Open

When exporting tables into PowerPoint Exports, the tables have a tendency to spill vertically over the edge of the page under certain circumstances, including when there are lots of columns. To overcome this, we have decreased the percentage of the PowerPoint slide that the table takes up to avoid this from happening as frequently. It will however still happen if you have a very large amount of columns, approx 10+, and it will cause smaller tables to take up a smaller portion of the slide too.

This is a temporary adjustment whilst alternative solutions are explored to further optimise the PowerPoint Export functionality.

When using the same table multiple times in the report, only the first instance of the table would displayed correctly - in some cases this presented tables with missing columns from the header. Any duplicates of the same table will now be shown in its full length containing all the data. Further improvements have also been made in the positioning of the elements within the slide - to ensure that no content is displayed outside of the slide body.

When attempting to export to Word, should an image be present in the header that has no position defined, this will no longer fail to export. Should no position be defined, this will now set to the default position.

When attempting to use the Drill to Chart, on a values that contained an XML special character (< > “ ' &), the Drill would previously fail - as would attempting to open the Chart Editor. An error would be displayed for a ‘Response with Status: 500 OK for URL’ error, which is now resolved.

As part of the new Auto User Sync functionality introduced in the February 24 release, creating Users through the /users/sync POST endpoint would fail unless you were authenticated as the Super Admin User - this is no longer the case.

Upgrades performed to several libraries, including;

• Go which has been upgraded v1.22 for both the Scheduler and Excel Reader modules.

• Logback has also been upgraded from 1.2.11 to 1.2.13.

Resolution of a Known Issue introduced in the February 24 release, Windows & Linux distributions now include the upgraded PostgreSQL driver (v 42.6.1) as standard, which resolves known vulnerabilities.

We’ve addressed errors when running migrations using an external MySQL database for Dashboard Repos, due to syntax discrepancies between it and MariaDB updates made in MySQL 8 - that changed the name of a table that was used for validation.

Resolved an issue where Databases with multiple schemas configured would eventually run into migration errors. This was due to non schema specific querying of certain INFORMATION_SCHEMA tables, resulting in migrations that had already taken place on the active schema being attempted again.