Skip to main content

Desktop Application - What's New in Version 2026.5.2

August 31, 2026 - Bug Fixes

Written by Flexibot

⚠️ Important Notices

Restoring a backup with a PostgreSQL extension that requires database administrator privileges (for example postgres_fdw) will continue to work correctly on on-premise installations. The exception is extensions that require permissions beyond the database itself — reading files from the server's disk or executing commands (for example foreign tables via the file_fdw extension); for security reasons, such a backup cannot be restored.

We therefore recommend verifying that your backups can be restored, or removing incompatible objects if necessary. If needed, a "non-functional" backup can still be restored — Flexi can skip objects listed in the pg_restore_skip_list.txt file in the installation directory (on Linux, /usr/share/flexibee). Each object should be listed on a separate line exactly as output by pg_restore --list; for extensions, this means a pair of lines, EXTENSION - file_fdw and COMMENT - EXTENSION file_fdw. Lines starting with # are ignored.

Nothing changes for cloud installations.

Improvements

  • The new web interface design is gradually becoming the default, rolled out in groups based on license type — starting with BASIC licenses, followed by other variants. This change only affects users who have not yet manually selected a design — anyone who previously switched back to the old design will remain on it. You can still switch between designs using the ?channel= parameter in the application URL.

Bug Fixes

  • The PostgreSQL data directory upgrade now completes successfully when installing a new version. Previously, the upgrade tool crashed immediately after launch on all platforms — the installation appeared to succeed, but the server then failed to start and displayed a misleading error about the firewall and antivirus software. Additionally, on Windows, if the database upgrade fails, the installation now stops and rolls back instead of silently continuing.

  • The custom button with ${objectIds} now works correctly when applied to a large selection of records in the desktop client, even when the resulting address exceeds the length limit.

  • Upgrading the database to a new version no longer fails due to duplicate GUID identifiers in employer's monthly report items. Duplicates are now removed.

Did this answer your question?