Help Center

Sapera - hotfixes 10 September 2026

Minor update (hotfixes) - fixes and improvements in Sapera.

This update is a minor rollout (hotfixes) with a number of fixes and improvements. The changes are rolled out gradually across environments.

Calendar

  • Fixed a performance regression, so the calendar (Task planner) is fast again when loading and switching weeks – including when a task is moved from one day to another.

  • Fixed that selecting an empty time slot from a sales order with a task type that has a defined expected duration could fail.

Inventory

  • Fixed that the price-update dialog for serial-number items also listed already-sold units; it now shows only the available ones.

Purchasing and purchase invoices

  • When moving a purchase invoice back to draft, the real reason is now shown if it cannot be done (instead of a misleading settlement error), and a blocked cost-price adjustment is now handled correctly.

Accounting and finance

  • Fixed that a supplier FIK without a Payment ID blocked the payment and disabled "Enter FIK".

  • Bank reconciliation (Aiia): Bank transactions that change date without being marked as deleted are now handled via a nightly resync back in time (the number of days can be configured). Entries removed by the bank are now marked ("Removed by the bank") and can be filtered, and you can choose to delete them – optionally with automatic reversing entries first.

SyncTool and data synchronization

  • SyncTool can now settle gift cards and refund coupons (credit notes).

  • New action to unzip ZIP files (Unzip).

  • Dynamic fields (EAV fields) now appear in the field merge dialog.

  • Category import now matches category identifiers case-insensitively, so text-based identifiers are matched and updated correctly.

  • Clearer message when an .ssd file contains no credentials (instead of incorrectly reporting a wrong password).

  • Publishing SaperaBI is now refused if the permission lookup (RLS) is empty, so data is not exposed without security.

  • Guidance on how to resolve a Fabric capacity error (403).

If you have any questions about the changes, you are welcome to contact support.

Did this answer your question?
😞
😐
😁