These release notes describe the changes in version 20261000.0, released on October 29, 2026.

Bug fixes

"Rebuild Pending" marker on Component Address Groups is now updated

When the Equipment-Informationcenter was opened from the Component Address Groups list, the Rebuild Pending marker stayed set even though the structure had already been rebuilt while opening. The marker only disappeared after a manual page refresh (F5).

• The list is now updated straight away, so the marker shows the actual state.
• The rebuild status fields on the list can no longer be edited, as changes to them were never saved.

Performance Characteristic Ledger Entries: Actual Value and Total Value no longer rounded to two decimal places

Fixed an issue where the Actual Value and Total Value fields in the performance characteristic ledger entries were displayed rounded to two decimal places: values with more decimal places appeared distorted or even as 0.00, although the correct value was stored.

Both fields are no longer rounded. Entries that have already been posted now also show their actual value.

Missing translations in the Equipment-Informationcenter

In the Equipment-Informationcenter, the texts of the page navigation below the tables and the equipment structure were previously always displayed in English, regardless of the selected language, e.g. items per page, No items to display or the number of entries shown. These texts are now displayed in the user's language.

Contract fields in sales invoice lines moved

In the sales invoice lines, the Contract No. and Contract Pos. No. fields are no longer shown as the first columns, but at the end together with the other maintool fields.

Default values extrapolation from the object monitoring line card corrected

Fixed an issue that occurred when the Default Values Extrapolation action was opened from the card of an object monitoring line. The extrapolation was not assigned to the monitoring line, so no due dates were calculated for counter monitoring. As on the Object Monitoring Lines page, the action now shows the correct monitoring line.

Improvements & enhancements

Work order demand in planning

Open work order lines of type Item are now considered as demand by Calculate Plan in the requisition worksheet and the planning worksheet, separated by location and variant on the execution date. This automatically creates purchase proposals for required spare parts.

• Closed and canceled work orders are not considered.
• If a demand forecast is selected, the work order demand consumes the forecast in the same way as sales orders.

Item demand from time schedules and object monitoring

Future maintenance from time schedules and object monitoring now creates item demand, even if no work order has been created yet. This allows you to order items with long lead times in time.

• The item lines of the time schedule are considered for every due date of the date preview. You define the period in the Date Preview Period field on the Work Order Management Setup page; Create Date Preview must be enabled on the time schedule.
• If object monitoring lines use a time schedule as template, the demand is created per object. For counter and attrition monitoring, the projected dates apply.
• As soon as a work order has been created for a due date, only its demand is counted.
• Blocked or expired time schedules and monitoring lines are not considered.

The demand is shown on the Item Availability by Event page and considered by Calculate Plan in the requisition and planning worksheet. For this purpose, the new action Line > Item Availability by > Event is available on the time schedule lines.

Also included

• For time schedules for which a date preview is already created, Calculate Plan considers the demand after the update without any further setup. The requisition and planning worksheet may therefore contain additional lines.
• On the Untracked Planning Elements page, the time schedule is now shown as the source of demand from time schedules.
• On the Order Tracking page, the Show action now also opens the work order.

Extensibility

New codeunit GLI Time Schedule Avail. Mgt. with ShowItemAvailabilityFromTimeScheduleLine; in the table GLI Time Schedule Line the procedures FilterLinesWithItemToPlan and FindLinesWithItemToPlan. New integration events: OnBeforeShowItemAvailabilityFromTimeScheduleLine, OnAfterTransferFromTimeScheduleLine, OnAfterGetDemandDates, OnAfterTransferInventoryProfileFromTimeScheduleLine, OnBeforeIsTimeScheduleDemandToBePlanned, OnAfterFilterLinesWithItemToPlan.

Enhancements for resource groups in work order planning

In work order planning, resource groups now behave largely like individual resources.

• For a planned resource group, an availability conflict is shown when the quantity planned for an execution date exceeds the capacity of the group. The calculation can be switched off in the Work Order Management Setup using a new check box.
• Resource groups can have a base unit of measure as well as alternate unit of measure codes with a conversion factor, so that quantities can also be entered in differing units such as day or hour.
• When a work order line is entered with a resource group, any unit cost and unit price stored on the group are applied, provided they exist.
• From the resource group list and the resource list, two new menu entries lead directly to the related work order lines.

Upgrade note

• The conflict calculation for resource groups is active by default after the update.
• For existing groups with a unit of measure already assigned, the base unit of measure is created automatically during the update.

Product name "maintool" in the user interface

The former product name “MAIN-TOOL” has been replaced by “maintool” throughout page titles, FastTabs, tooltips, messages and permission sets, for example in the maintool setup, the assisted setup and on the customer, vendor, item and resource cards.

Existing personalizations and extensions are not affected.

Maintenance Planner Role Center: configurable calculation interval for date proposals

The setup of the Maintenance Planner Role Center now contains the new Calculation Interval field. It determines whether the date proposals are recalculated every time the role center is opened, hourly or daily. By default, the field is set to Always.

• With an hourly or daily interval, the proposals are only recalculated when the next calculation is due, so the role center opens considerably faster, especially when there are many date proposals.
• You can trigger a recalculation manually at any time with the Update action in the date proposal list.

Also included

• The calculation of the date proposals itself has been sped up.

Operating status for technical objects

You can now maintain an operating status for component addresses, mounting positions, technical components and vehicles: Installation, Operating, Standby, Shutdown or Decommissioned.

• Every status change is recorded in the new operating status entries with start, end, duration and user, which can be opened from the object's card.
• The operating status is also shown as a column in the lists of component addresses, mounting positions, technical components and vehicles.
• Similar to the location, the operating status can be passed on to subordinate objects and inherited from higher-level objects.
• The operating status can also be set through the REST API.

Upgrade note

For newly created objects, passing on and inheriting are enabled by default. For existing objects, both options are disabled after the update and can be enabled manually if needed.