Release September 2026

We are back from the summer break and are very happy to deliver the brandnew September 2026 Release with the refreshed Website and great new Features in the software! Try it now!

Remember, the Frontend is the user friendly spreadsheet for your Collector Users to deliver their monthly/weekly/daily data. The Modeller is the tool for the Power User to setup and control your organization’s collection workflows.

(1) Website Relaunch: new Brand, new Content and Multilingual

After the rebranding the data-one Service with the July 2026 release, we are happy to pronounce that our webpage now is also relaunched. It is designed with the new brand data-one.cloud and of course we took the chance to update all contents:

Furthermore our webpage is now multilingual – the major contents are now also in German language available:

(2) Frontend: New Workflow Widgets

We redesigned the Workflow Widgets to make the information on the widgets easier to use:

See here in action:

(3) Frontend: Finetuning Rebranding

After rebranding to data-one Cloud in July 2026 release we decided to do some finetuning in the header both of the frontend as well of the modeller. We colored the header orange and added the complete logo:

This is how the frontend now looks like …

… and here is the backend:

(4) Frontend: Performance Analyzer Improvements

The Performance Analyzer has become an essential tool for optimizing performance of data-one solutions.

a) New processes added

Until now, the focus of the Performance Analyzer were the READ and the WRITE processes – which are of course the most important processes by far. But since some processes were not documented by the Performance Analzer it could happen that waiting time in reality was (by far) not the same as documented in the Performance Analyzer.

This has changed now – all proceses are documented now by the Performance Analyzer. This has a big impact especially for the logged durations of the initial opening process of a workbook:

b) Database DTU Usage added

A very big step forwards is the integration of the “Database DTU Usage” directly into the Performance Analyzer. Until now, this information was only available in the Tenant Settings.

With the integration in the Performance Analyzer you get an idea if your process maybe was slower than usual due to the general capacity usage of the database. Since the usage information has a time delay of about 2 minutes, we cannot see in real-time the database usage when executing a process:

But after a few minutes we can see the usage of the database (= the green line on the bottom in relation to the red line at the top) at the time of the process execution (= vertical lines).

(5) Frontend: Performance Improvements

We could improve the performance for rendering the dimension tree when initially loading the workbook but also when initially entering a sheet the first time. With large dimension trees the rendering time could be reduced from 15 sec to 1.5 sec!

(6) Modeller: Archive & Restore Fact Records

Speaking of performance: data-one will be probably faster if there are less records in the fact table.

This is the reason why we provide you new Archive & Restore functions for the maintenance of the fact table. Simply filter the records you want to archive …

… and press the Move to Archive button. For security reasons you have to type the string “ARCHIVE” in the dialog box in order to start the process:

The process is executed as a task on the server and you`ll get the success message as soon as the archiving is finished:

During archiving, the records are moved from the “Fact Table” to a new table called “Fact Table Archive”. You can select this Archive table, select records and restore the records to the Fact Table if needed again.

Pleas be aware that the performance of the frontend can be worse after archiving data since the SQL query plans have to be updated. This is done automatically by the database itself but it has to learn from your queries. After a while you will see that your workbooks will be faster if there are less records in the fact table.

(7) Further Improvements

We improved the tenant dropdown in case an application owner is not tenant admin in an external tenant. And we improved the application dropdown in case a tenant has no application left.

We extended the ODATA API to create also new users via the API.

---

We hope you like the new features – we are very curious about your feedback!

Please let us know what you think about data-one and what kind of planning and data collection processes you evaluate to automate.

we #StandWithUkraine

This post is also available in: