NOTICE! Release Saturday, November 7, 2026
The release notes below are preliminary for the planned release on November 7, 2026. The content may be adjusted until the release date, for example if planned features need to be postponed or additional items are added to the release.
Additions to the release notes after the article is published are marked with green highlighting. If anything is potentially removed from the release, it is marked with red highlighting.
What's new
Diary
Diary and Diary 2.0 are now merged into a single module with two different views.
You can now configure per project whether the diary should be reported at the work order/changes and additions level or at the project level. The setting determines which diary view is displayed in the project. Work order/changes and additions diary is the default for new projects. You cannot switch from work order/changes and additions diary to Project diary if there are multiple notes of the same type.
- Diary sheets from Diary 2.0 can now be published in Next Portal. For a post to be visible, the portal must be shared with the customer on the project and the post must have the status Approved by performer. The portal user can approve or reject the post and add a comment, and the status is visible in the client. Note that this also applies retroactively.
- New status Rejected by customer (red, locked) and a new column for customer comments in the diary grid for the AO/changes and additions diary
- Project diary view
- Adjusted note headings to align with the AO/changes and additions diary view.
- Expanded support for multiple checklists per diary sheet.
- The three project diary reports are replaced by a single report with more selection options.
- Support for KPIs is discontinued due to (NOTICE: Internal information only)
- Mobile - All mobile diary reporting is now performed through mobile (the new version), with a new, simpler design.
- You can now report diaries at the project level in the mobile app based on the project settings.
- You can also select a work order per order row in the project diary.
- Weather data is now retrieved automatically through a weather service when you tap “add weather” in the mobile app.
- Permissions from Diary and Diary 2.0 are merged. Changing the status of a diary sheet requires the Update diary status permission.
Data migration when merging the diary modules
- All posts in the project diary are moved to the new diary under the project's base commitment, with the date, reporter, worksite, and construction day preserved. If an active diary sheet already exists for the same project and date, the old one is not moved; instead, a PDF with the conflicting data is saved in the current project.
- Notes are sorted under Started, ongoing, and completed work; Deviations, disruptions, and obstacles; and Changes and additional work. Note that Completed work no longer has its own field.
- Order rows, weather (a maximum of two observations per post), and workforce are moved with their information. The checklist is also migrated. Documents are moved if the file exists in the base commitment's folders; otherwise, they are detached with an informational note.
e-Invoice
- You can now once again see the time along with the date in the approval field on the accounting row in e-Invoice.
Fixes
e-Invoice
- When you saved a new supplier with both a country code and VAT registration number in e-Invoice, the page would freeze and you had to close the window or reload it. This has now been fixed, so you can save a new supplier without any problems.
- If an accounting entry on a supplier invoice has an account number beginning with 1 or 2, the invoice must be marked as Ready for approval to be counted as approved.
Performance in e-Invoice has been improved. After an update, only the affected invoice is now reloaded instead of the entire invoice list, and approving an invoice is faster.
Customer invoice, c-Invoice
- Outgoing customer invoices sent through c-Invoice (Crediflow) now use the company's GLN (EDI address) as the sender when one is specified for the company. Otherwise, the organization number is used as before. This ensures that invoices reach the correct portal even when the organization number is linked to multiple portals at Crediflow.
Budget
- If you added rows on one of the Revenue or Expenses tabs and switched to the other tab without saving manually, the rows were saved twice. The rows are now saved only once.
Deviations
- In databases with more than 1,000 deviations, the deviation list in the mobile app could cause the browser to close the page on some mobile devices. The list now opens and can be browsed, regardless of how many deviations you have.
Tenders/Contracts
- Tenders and contracts could appear empty after reloading, or display content from another project when you switched projects. They are now displayed correctly without you needing to switch projects to show the correct content.
Next ID
- A user who was invited to Next ID and was deactivated and reactivated before the first login to Next could get stuck in a login loop without an error message. This has been fixed, and the user can now log in as usual after being reactivated.