Asta Powerproject 2026.2 release notes

This topic lists the new features that have been introduced, and the issues that have been addressed, in the Asta Powerproject 2026.2 release.

DevOps Work Item 1029
Category Export to Business Intelligence
Summary Unable to export data to Business Intelligence from a project that includes a formula that refers to a non-existent code.
Description Before this release, it was not possible to export data to Business Intelligence from a project that included a formula that referred to a non-existent code.
Resolution

This issue has now been addressed. If the project from which you are trying to export data includes a formula that refers to a non-existent code, rather than this causing the formula compiler to fail, the result from the non-existent code is now treated as 'null' - meaning that no such codes are assigned - which allows the formula compiler to work.

 

More information on exporting Business Intelligence data

 

DevOps Work Item 6778
Category Asta Powerproject 4D
Summary Imperial units of measurement are converted into metric units when 3D models are opened in Asta Powerproject 4D.
Description Before this release, if a 3D model in which imperial units of measurement were used was opened in Asta Powerproject 4D, the values were converted into, and displayed using, metric units for the purposes of displaying the calculated area and calculated volume fields.
Resolution

If you open a 3D model in which imperial units of measurement are used in Asta Powerproject 4D, the calculated area and calculated volume values are now displayed using imperial units, rather than being converted into metric units.

 

More information on opening 3D models

 

DevOps Work Item 7079
Category Asta Powerproject 4D
Summary Create project schedules automatically from 3D models.
Description

You can now create a project schedule automatically from one or more 3D models, or from one or more IFC group models. This provides you with a quick and easy way of constructing a schedule, based on the properties of the 3D models themselves, and is particularly useful if you are starting a new project with one or more 3D models that contain a substantial amount of information from the outset that is relevant to the schedule.

When you create a project schedule automatically from one or more 3D models, you specify the properties within the 3D models on which you want to base the project hierarchy. For example, you could base the hierarchy on the 'Site', 'Building' and 'BuildingStorey' properties. If you did this, the resulting hierarchy would have three levels: one for each of the selected properties. The top two levels would be represented by summary tasks, while the lowest level would be represented by individual tasks, which would be associated with the 3D objects in the 3D models using IFC product searches which are created by the wizard.

 

At the same time as creating the project hierarchy, you can choose to create one or more code libraries, containing code library entries that correspond to the values contained within specific 3D model properties. If you choose to do this, the code library entries are assigned to the relevant tasks at the lowest level of the hierarchy. The creation of code libraries is optional, but it does provide you with a powerful way of making the most of the data that is contained within your 3D models.

 

More information on creating project schedules automatically from 3D models

 

DevOps Work Item 7080/14968
Category Asta Powerproject 4D
Summary Improvements to the Ribbon for Asta Powerproject 4D.
Description

This release of Asta Powerproject introduces a number of 4D-related improvements to the Ribbon, which make it easier to work with your 3D models in Asta Powerproject 4D.

 

The following improvements have been made to the 4D tab of the Ribbon:

  • The Configuration control has been renamed to 'Manage Models'.
  • A new 'Project' group of controls has been added, comprising controls that you can use to create a project schedule automatically from one or more 3D models; to reschedule your project; and to open Library Explorer. The latter two controls are duplicates of commonly-used controls that exist elsewhere; they have been added to the 4D Ribbon tab to save you from having to switch from tab to tab so frequently as you work with your 3D models.
  • The drop-down control that you used to use to display and hide various elements of the user interface including the IFC Model pane, the IFC Properties pane and the IFC Comparison Model pane, has been replaced by a series of controls in a new 'Panes' group, which you can use to toggle different elements of the user interface on and off. This means that these controls are easier to locate and more convenient to use.

In addition to this, when either the IFC Model pane or the IFC Comparison Model pane is in focus, the Format tab of the Ribbon now displays a selection of controls that you can use to work with the 3D model. Some of these controls used to appear on the 4D tab, but other controls - those relating to splitting and merging 3D objects - were previously available only via right-click menus. Duplicating these controls on the Format tab makes them easier to locate and use.

 

More information on the 4D Ribbon tab

 

More information on the 4D controls on the Format tab of the Ribbon

 

DevOps Work Item 8407
Category Calendars
Summary UK Easter 2026 bank holidays have the incorrect dates in calendars.
Description A customer reported that the UK Easter 2026 bank holidays appeared on the wrong dates in Asta Powerproject's calendars: they appeared a week too early.
Resolution

Asta Powerproject's calendars have been updated so that the UK Easter 2026 bank holidays appear on the correct dates.

 

More information on marking exceptions on calendars

 

DevOps Work Item 12113
Category Asta Powerproject 4D
Summary The Hide/Show Items dropdown now indicates which option has been selected.
Description Before this release, the Hide/Show Items dropdown, which used to appear on the 4D tab of the Ribbon, did not indicate which option had been selected.
Resolution

A tick now appears next to the last-chosen selection in the Hide/Show Items dropdown, indicating which option is currently selected.

 

As the visibility of items can be adjusted manually, the last-chosen selection is cleared - and the tick disappears - when any of the following actions are taken:

  • The 3D model is reset.
  • A 3D object is hidden manually.
  • IFC product searches or selections are shown or hidden, via the project view right-click menu.
  • A timeline simulation is run.
  • Unassigned or unscheduled tasks are shown.
  • The 3D model is changed.

Along with a number of other controls, the Hide/Show Items dropdown has now been moved from the 4D tab of the Ribbon to the Format tab.

 

More information on hiding and displaying 3D objects in a 3D model

 

DevOps Work Item 12532
Category Asta Powerproject 4D
Summary 3D model does not display correctly in Asta Powerproject 4D.
Description A customer reported that when they opened a particular 3D model in Asta Powerproject 4D, it did not display correctly; two beams appeared separate from the main body of the model. The beams appeared correctly when the 3D model was opened in other applications.
Resolution

This issue has been addressed, so the 3D model is now displayed correctly when it is opened in Asta Powerproject 4D.

 

More information on opening 3D models

 

DevOps Work Item 12588
Category Asta Vision global libraries
Summary Global library date synchronisation issue.
Description Before this release, in very rare cases - possibly in which the clock on a customer's computer is set to a slightly different time that the Asta Vision server clock (ie their computer's clock is slow) - global library synchronisation issues could occur. This could result in global entries not appearing.
Resolution

Asta Vision global libraries can now cope with users' computer clocks being set to a different time than the Asta Vision server clock, so these synchronisation issues no longer occur.

 

More information on managing global libraries with Asta Vision

 

DevOps Work Item 12950
Category Business Intelligence Controller
Summary Incorrect period start dates in time-sliced Business Intelligence data exports.
Description Before this release, if you exported time-sliced Business Intelligence data, the start date of each period was aligned with the start of the first item to be encountered, rather than with the start of the period. For example, if you created a duration time slice set to '1em', and the first task encountered started on 7th February, the output periods for all items would start on the 7th of the month, rather than on the start of each month.
Resolution

Time-sliced periods are now aligned correctly - they now start on the start date of each year, quarter, month or week.

 

More information on exporting Business Intelligence data

 

DevOps Work Item 12996
Category Object Edit toolbar
Summary Code library entry names truncated when displayed via the Object Edit toolbar.
Description Since the release of Asta Powerproject 2026.1, the names of code library entries appeared in truncated form when they were accessed via the 'Code/link category' control on the Object Edit toolbar.
Resolution

The names of code library entries now appear correctly when accessed via the 'Code/link category' control on the Object Edit toolbar.

 

More information on the Object Edit toolbar

 

DevOps Work Item 13131
Category Asta Powerproject Help
Summary A number of example queries in the 'TQL' topic of the Asta Powerproject Help do not work.
Description A number of the example queries in the 'TQL' topic of the Asta Powerproject Help did not work, and resulted in errors when people attempted to use them in Asta Powerproject.
Resolution

The syntax of the example queries in the 'TQL' topic has been corrected to ensure that the queries work without returning errors.

 

More information on using TQL in Asta Powerproject

 

DevOps Work Item 13267
Category Asta Powerproject 4D
Summary The 'IFC product count' field displays too low a value when a project is opened without its 3D model.
Description A customer reported that when they worked with an Asta Powerproject 4D project without its 3D model open, the 'IFC product count' field displayed a lower value than it did when the 3D model was open.
Resolution

The 'IFC product count' field previously relied upon a 3D model - or an IFC group model - being open in order to be populated correctly with information from the model. If a project was opened without its 3D model being opened too, this field displayed incorrect information.

 

If the 'IFC product count' field is present in any of a project's initial views when the project is opened without its 3D model being opened too, it now displays information about the 3D model that you last had open. Provided the project you last had open was the same as the project you have just reopened, this means that the 'IFC product count' field now displays the correct information.

 

If you add the 'IFC product count' field to the spreadsheet when a project's 3D model is not currently open, or if you display a view in which this field is included after a project has been opened without its 3D model, the information displayed in the field may not be reliable; in this case, you should close and re-open the project in order to refresh the field with data from the 3D model that you last had open.

 

While addressing this issue, a number of other issues that affected projects that were opened without their 3D models being opened too were identified. To address these issues, the following improvements have been made to Asta Powerproject 4D when a project is opened without its 3D model being opened too:

  • Previously, if an IFC product selection was associated with an IFC group model rather than with an individual 3D model, no information about the relevant 3D objects were displayed in a project if it was opened without its IFC group model being opened too. Information about IFC group models is now displayed correctly in projects that are opened without their IFC group models being opened too.
  • It can take some time for Asta Powerproject 4D to connect to an IFC group model to access information to display in a field when the IFC group model is not currently open. A progress indicator now appears when Asta Powerproject 4D is connecting to an IFC group model for information that it needs to populate a field, which makes it clear that Asta Powerproject 4D is doing something, and has not stopped responding.
  • If no 3D model is specified against an IFC product search, it operates on whichever 3D model or IFC group model is currently open. If no 3D model is currently open, such IFC product searches previously displayed no information about 3D objects. If no 3D model is currently open, IFC product searches for which no 3D model has been specified now display information about the 3D model that you last had open.
  • Previously, Asta Powerproject 4D was unable to identify that a 3D object had been split or merged unless the 3D model was open. Information about split and merged 3D objects is now displayed correctly when a project is opened without its 3D model being opened too.
  • Improvements have been made to the way in which information about the 3D objects that are grouped together by IFC product searches and IFC product selections is loaded into Asta Powerproject 4D. This means that if you open a project, close it and reopen it within a single Asta Powerproject 4D session, reopening the project now takes less time, as the 3D object data no longer needs to be loaded a second time.
  • Previously, errors could occur if you previewed a view for printing in which the 'IFC product count' field was displayed in the spreadsheet. These errors no longer occur.
  • Previously, if you closed a project that had an open IFC group model, the cache of data about the IFC group model's 3D objects was retained. This caused issues if you subsequently re-opened a different project without its 3D model, as Asta Powerproject 4D used the cache from the IFC group model that had been open to populate fields. Now, when you close a project that has an open IFC group model, the cache of data about its 3D models is cleared. This ensures that when you reopen a project, Asta Powerproject 4D uses the correct 3D model or IFC group model to populate fields.

Note that site objects are excluded from IFC product searches when a project is opened without its 3D model being opened too.

 

More information on opening 3D models

 

DevOps Work Item 13317
Category Calendars/Milestones
Summary Unable to save a project after having turned a task with no assigned calendar into a start milestone.
Description A customer reported that after they had turned a task with no assigned calendar into a start milestone, a 'Save failed' error appeared when they tried to save the project.
Resolution

Asta Powerproject was failing to assign an original start date to the start milestone in this situation, due to the original task having no assigned calendar. Milestones are now assigned an original start date when they are created from tasks with no assigned calendar, meaning that it is now possible to save projects in this situation.

 

More information on assigning calendars to tasks and resources

 

More information on working with milestones

 

DevOps Work Item 13582
Category Histograms
Summary Task work-based histograms ignore task work for completed milestones when configured to include all tasks, regardless of progress.
Description Before this release, if you used the 'AllocatedWork(TODATE)' resource graph formula in a task work-based histogram and configured the histogram to include all tasks, regardless of progress, task work for completed milestones did not appear in the histogram.
Resolution

Task work-based histograms no longer ignore task work for completed milestones when they are configured to include all tasks, regardless of progress.

 

More information on using histograms to graph activity days and task work

 

DevOps Work Item 13696
Category Calendars/Resource modelling
Summary Changing the calendar of a task that has a modelled resource allocation can result in the task having an incorrect duration.
Description

A customer reported that when they changed the calendar of a task that had a modelled resource allocation, the task was given the duration of the allocation, rather than retaining its own duration in terms of days, in the following circumstances:

  • The resource was modelled as 'Effort on Allocation' and was configured to use the task's calendar.
  • The days in the newly-assigned calendar had a different duration to the days in the original calendar.
  • When the task's calendar was changed, Retain the existing duration and change the dates if necessary was selected on the Change Task Calendar dialog.
Resolution

Changing the calendar of a task in the above circumstances now results in the task retaining its original duration in terms of days, rather than being given the duration of the modelled resource allocation.

 

Note that this change does depend on the modelling type of the resource allocation, and that if the allocation's modelling type cannot be changed, the original behaviour will persist.

 

More information on changing a task's calendar

 

DevOps Work Item 13808
Category Asta Powerproject 4D
Summary 3D model does not display correctly in Asta Powerproject 4D.
Description A customer reported that when they opened a particular 3D model in Asta Powerproject 4D, it did not display correctly. Several windows appeared in the wrong places; some walls displayed little detail and overlapped windows; and a random block appeared on the edge of the model. The 3D model appeared correctly when it was opened in other applications.
Resolution

This issue has been addressed, so the 3D model is now displayed correctly when it is opened in Asta Powerproject 4D.

 

More information on opening 3D models

 

DevOps Work Item 14590
Category Printing
Summary The paper dimensions of some non-standard printer page sizes are not displayed correctly on the Print dialog.
Description A customer reported that when they selected certain non-standard printer page sizes, in the Printer page size field, on the Details tab of the Print dialog, the dimensions of the paper were not displayed correctly.
Resolution

This issue has been addressed, so the dimensions of non-standard printer page sizes are now displayed correctly on the Details tab of the Print dialog.

 

More information on specifying the size and orientation of paper to print on

 

DevOps Work Item 14788
Category Library Explorer
Summary Copy and paste lists of cost centres into Library Explorer.
Description

Asta Powerproject version 2026.1 introduced the ability to copy and paste lists of codes, consumable resources, permanent resources and users into Library Explorer, to speed up the process of setting up new projects in situations where a list of these items is available in another application.

 

You can now also copy and paste lists of cost centres into Library Explorer.

 

You can copy and paste lists from a variety of applications. For example, you can copy lists in which each item is separated by a 'carriage return' from text editors such as Microsoft Notepad or Microsoft Word; and you can copy lists in which each item comprises an individual cell in a spreadsheet column from spreadsheet editors such as Microsoft Excel.

 

More information on creating objects in Library Explorer

 

DevOps Work Item 14878
Category Progress
Summary The 'Progress at period' field displays nothing in the spreadsheet for summary tasks when configured to use a newly-created progress period.
Description Before this release, if you created a new progress period and configured a spreadsheet column to display the 'Progress at period' field for the new progress period, no data was displayed in the spreadsheet column for summary tasks.
Resolution

The 'Progress at period' field now correctly displays the cumulative progress from previous progress periods for summary tasks, when the spreadsheet column is configured to use a newly-created progress period.

 

More information on progress periods

 

More information on progress fields

 

DevOps Work Item 14942
Category Asta Vision Live
Summary Asta Powerproject saves changes automatically during Asta Vision Live collaboration sessions.
Description

Asta Powerproject now saves changes automatically every two and a half minutes when users are working on an Asta Vision programme in a collaboration session. This prevents large amounts of data from being lost if users forget to save their work manually.

 

More information on collaborating with other users on Asta Vision programmes

 

DevOps Work Item 14943
Category Asta Enterprise
Summary Asta Powerproject is unable to access projects in one of its Asta Enterprise data sources.
Description A customer reported that when they tried to open projects that were located in one of their two data sources, an 'An error has occurred sending data' appeared, and the projects failed to open.
Resolution

Asta Enterprise has been enhanced so that this problem no longer occurs.

 

More information on opening projects

 

DevOps Work Item 14957
Category Asta Vision
Summary Having created a new Asta Vision project from within Asta Powerproject, a new prompt asks whether you would like to check out the project's initial programme or display the list of Asta Vision projects.
Description

A prompt now appears after you have created a new Asta Vision project from within Asta Powerproject, giving you the choice of checking out the project's initial programme or displaying the list of Asta Vision programmes on the Open tab of the Backstage view, from where you can download the programme, check out the programme, or start a collaboration session on the programme.

 

More information on creating Asta Vision projects

 

DevOps Work Item 15024
Category Project Viewer
Summary 'N/A' appears in the 'Task ID (WBN)' and 'Task ID (WBN) path name' spreadsheet columns when a project is opened in Project Viewer.
Description A customer reported that when they opened a project in Project Viewer, 'N/A' appeared in the 'Task ID (WBN)' and 'Task ID (WBN) path name' spreadsheet columns.
Resolution

Investigation showed that this issue affected WBS-related fields as well as Task ID (WBN)-related fields. The data in these fields should have appeared as read-only in Project Viewer, rather than not appearing at all. Data in WBS-related fields and Task ID (WBN)-related fields now appears correctly in Project Viewer

 

More information on identification fields

 

More information on Project Viewer

 

DevOps Work Item 15048
Category Bar chart
Summary Splitting partially-progressed tasks that have task work and a task work rate recorded against them increases the task duration.
Description A customer reported that when they split the unprogressed segment of a partially-progressed task that had task work and a task work rate recorded against it, the total duration of the task increased.
Resolution

This was caused by Asta Powerproject calculating the task work on the tasks that resulted from the split based on the total task work, rather than on the actual and remaining task work. Asta Powerproject now calculates task work on the resulting tasks correctly when a task is split, which means that such tasks retain the correct total duration.

 

More information on splitting and merging tasks and allocations

 

DevOps Work Item 15052
Category Asta Powerproject 4D
Summary Bar chart tracking does not work when running a timeline simulation.
Description A customer reported that when they ran a timeline simulation on a particular IFC group model with the Track in Bar Chart control selected, the bar chart tracking did not work: the camera did not move, the bar chart did not move, and tasks were not highlighted.
Resolution

This was caused by early sections of the project being completed, and selection tracking and bar chart tracking not working for completed sections of tasks. Selection tracking and bar chart tracking now work for completed sections of tasks.

 

More information on running a timeline simulation of a 3D model

 

DevOps Work Item 15071
Category Asta Vision
Summary Unable to sign into Asta Vision from within Asta Powerproject.
Description A customer that uses conditional access policies with Microsoft Entra ID reported that they were unable to sign into Asta Vision from within Asta Powerproject.
Resolution

Asta Powerproject has been enhanced to address this issue, so it is now possible for the customer - and other customers in the same situation - to sign into Asta Vision from within Asta Powerproject.

 

More information on working with Asta Vision projects