Asta Powerproject 2026.1 release notes
This topic lists the new features that have been introduced, and the issues that have been addressed, in the Asta Powerproject 2026.1 release.
DevOps Work Item | 3561 | ||||
Category | Project timeline | ||||
Summary | Colour-code tasks in the project timeline using the appearance of the codes that have been assigned to them. | ||||
Description |
You can now colour-code tasks in the project timeline using the appearance of the code library entries that have been assigned to them. If you use code library entries to colour-code tasks in the bar chart, choosing to colour-code tasks in the project timeline as well makes it easier to differentiate between tasks, and to identify which tasks in the project timeline correspond to which specific tasks in the bar chart.
To enable you to colour-code tasks in the project timeline using code library entries, a new Code library check box has been added to the Timeline Appearance dialog, with a Display Libraries field to the right of it. Clicking this button launches the Multiple Display Libraries dialog, which you can use to specify which code libraries to use to colour tasks in the bar chart, in the calendar view and in the project timeline.
More information on configuring a project timeline
More information on the Timeline Appearance dialog
|
DevOps Work Item | 4538 | ||||
Category | Project timeline | ||||
Summary | New 'Displayed in timeline' spreadsheet field. | ||||
Description |
A new 'Displayed in timeline' spreadsheet field has been added to the 'Miscellaneous' group of fields. If you display this field in the spreadsheet, it appears as a check box. As well as using this field to identify which tasks are included in the project timeline, you can select the check box against a task to include that task in the project timeline, and clear the check box to exclude the task from the timeline.
More information on adding tasks to a project timeline
|
DevOps Work Item | 4871 | ||||
Category | Task activities | ||||
Summary | New 'Task activity names' spreadsheet field. | ||||
Description |
A new 'Task activity names' spreadsheet field has been added to the 'Task activities' group of fields. This displays the names of each task's task activities, in a comma-separated list. If you display this field in the spreadsheet, you can identify each task's activities without having to view the properties of the task.
The field displays the task activity names in the order in which they appear in the Bar and Task Properties dialog. If a bar contains more than one task, the task activity names for each task on the bar are displayed, in task order, then in task activity order.
If you display this field in the spreadsheet and you have more than one task on a bar, you will find it easier to interpret the information in the field if you display the bar in one-task-per-line mode.
More information on breaking down tasks into smaller steps using task activities
More information on the available 'task activities' fields
|
DevOps Work Item | 4921 | ||||
Category | Dialogs | ||||
Summary | Display the start and finish dates of predecessor and successor tasks in columns on the Links tab of the Bar and Task Properties dialog and on the Links tab of the properties view. | ||||
Description |
You can now display 'Start (predecessor)' and 'Finish (predecessor)' columns in the upper grid on the Links tab of the Bar and Task Properties dialog, and 'Start (successor)' and 'Finish (successor)' columns in the lower grid. These columns display the start and finish dates of predecessor and successor tasks - as opposed to the start and finish dates of incoming and outgoing links.
You can also add these new columns to the Links tab of the properties view.
It is still possible to display the start and finish dates of incoming and outgoing links on the Links tab of the Bar and Task Properties dialog, using the 'Start (link)' and 'Finish (link)' columns.
More information on the Links tab of the Bar and Task Properties dialog
|
DevOps Work Item | 4926 | ||||
Category | Asta Vision | ||||
Summary | Classify programme revisions. | ||||
Description |
You can now classify Asta Vision programme revisions, to identify the type of each programme revision that is created. The different classifications you use depends on how your organisation works with revisions. For example, you could set up a series of classifications including 'Progress update', 'Client change' and 'Scenario planning', to apply to your revisions.
In Asta Powerproject, if programme revision classification is enabled:
More information on checking programmes into Asta Vision
More information on submitting programmes to Asta Vision
|
DevOps Work Item | 4986 | ||||
Category | Asta Vision/Asta Enterprise | ||||
Summary | Unable to create new baselines in Asta Vision projects that have been saved as local files, then saved into Asta Enterprise. | ||||
Description | Before this release, if you saved an Asta Vision project as a local file, then saved it into an Asta Enterprise data source, you were unable to create new baselines in the project. | ||||
Resolution |
You are now able to create new baselines in Asta Vision projects that have been saved as a local file, then saved into an Asta Enterprise data source.
More information on saving projects
|
DevOps Work Item | 5214 | ||||
Category | Code breakdown structure | ||||
Summary | Spreadsheet fields that show a percent complete figure display no progress against the subheadings of a code breakdown structure that contains only milestones. | ||||
Description | Before this release, if a code breakdown structure contained only milestones, spreadsheet fields that show a percent complete figure displayed no progress against the code breakdown structure's subheadings. This was also the case for the subheadings of sorted/grouped views, if the view contained only milestones. This affected the 'Duration percent complete', 'Overall percent complete' and 'Percent complete' fields. | ||||
Resolution |
The 'Duration percent complete', 'Overall percent complete' and 'Percent complete' fields now display correct progress values against subheadings in a code breakdown structure or sorted/grouped view that contains only milestones.
More information on the available 'progress' fields
|
DevOps Work Item | 5376 | ||||
Category | Powerdraw | ||||
Summary | Custom colours used in border files do not print correctly when the borders are used for printing in Asta Powerproject. | ||||
Description | Before this release, if you edited a Powerdraw border file and included one or more custom colours in it - as opposed to selecting colours from the standard colour palette - the custom colours did not print correctly when the border file was used for printing in Asta Powerproject. | ||||
Resolution |
Custom colours in Powerdraw border files now print correctly when the borders are used for printing in Asta Powerproject.
|
DevOps Work Item | 6402 | ||||
Category | 'Jagged progress' mode | ||||
Summary | Jagged progress line does not accurately reflect the progress of milestones that are progressed after the progress period report date. | ||||
Description | Before this release, when a view was displayed in 'jagged progress' mode, the progress line was not displayed to the right of milestones that had been progressed after the progress period report date, thereby giving an inaccurate view of progress. | ||||
Resolution |
When a view is displayed in 'jagged progress' mode, the progress line is now displayed correctly to the right of milestones that have been progressed after the progress period report date.
|
DevOps Work Item | 6594 | ||||
Category | Reschedule | ||||
Summary | ASAP/ALAP placement affecting the placement of tasks unexpectedly when rescheduling. | ||||
Description | A customer reported that if they changed the placement of tasks from ASAP to ALAP and rescheduled a project, with Tasks with no links and Tasks with only outgoing links both set to 'Leave as drawn within constraints' on the Reschedule dialog, certain tasks were moved to an unexpected position. | ||||
Resolution |
The reschedule algorithm did not correctly handle tasks with only outgoing links during its backwards pass; the algorithm has been updated so that such tasks are now positioned correctly following a reschedule, regardless of whether they are placed ASAP or ALAP.
More information on changing the ASAP/ALAP placement of tasks and how this affects rescheduling |
DevOps Work Item | 6628 | ||||
Category | Histograms | ||||
Summary | Unable to export histogram information from Asta Powerproject to Microsoft Excel when sensitivity labels are enabled in Microsoft Office. | ||||
Description | A customer with sensitivity labels enabled in Microsoft Office reported that they were unable to export histogram information from Asta Powerproject to Microsoft Excel. No errors occurred when they attempted to export histogram information, but the export file was not created in the expected location. | ||||
Resolution |
A new set of histogram Excel templates have been incorporated into Asta Powerproject, which enable the export of histogram information from Asta Powerproject to Microsoft Excel when sensitivity labels are enabled in Microsoft Office.
More information on exporting histogram information to Microsoft Excel |
DevOps Work Item | 6791 | ||||
Category | Filters | ||||
Summary | Combine two or more existing filters into one single filter. | ||||
Description |
Before this release, if you wanted to combine two existing filters into one single filter, you had to create a new filter and manually edit its filter criteria to match the criteria of the filters you wanted to combine, which could be a time-consuming and error-prone task.
You can now combine two or more filters into one single filter automatically. For example, if you have one filter that returns tasks that have been assigned a particular code, and a second filter that returns tasks that have been completed, you can now combine these two filters into a single filter that returns tasks that have been assigned a particular code and that have been completed.
More information on combining two or more filters into one single filter |
DevOps Work Item | 6800 | ||||
Category | Bar chart | ||||
Summary | Display dates instead of durations for milestones when displaying bar and task information in the bar chart. | ||||
Description |
Before this release, if you chose to display a duration field in the bar chart - to the left or right of each task or over the top of each task - a duration of zero was always displayed for each milestone. As every milestone has a duration of zero, this information is not particularly useful; a more useful piece of information about a milestone is its date.
You can now choose to display the date of each milestone instead of its duration when a duration field is displayed in the bar chart, using the new Show dates instead of durations check box that has been added to the Task data display group, on the Tasks tab of the Format Bar Chart dialog. If you select this check box, the date of each milestone is displayed when a duration field is displayed in the bar chart; if you clear the check box, the duration of each milestone - which is always zero - is displayed.
More information on displaying bar and task information in the bar chart |
DevOps Work Item | 6801 | ||||
Category | Spreadsheet | ||||
Summary | Easier way of finding fields to display in the spreadsheet. | ||||
Description |
Before this release, to add a field to the spreadsheet you had to first find the category of the field, then search for the field within that category. If you knew the name of a field but were not sure of the category to which a field belonged, it could take some time to find the field you wanted.
You can now find spreadsheet fields by typing a few characters of their name. For example, if you type 'per', Asta Powerproject will suggest all fields that start with the characters 'per' - or, if you prefer, all fields that contain the string 'per' somewhere in their name.
To find new spreadsheet fields using this new feature, right-click a column in the spreadsheet and select either Add Column - Search for Column (to add a new column), or Field - Search for Column (to replace an existing column with a different column).
|
DevOps Work Item | 6802 | ||||
Category | Bar chart | ||||
Summary | Pan around the bar chart without using the scroll bars. | ||||
Description |
You can now pan around the bar chart without having to use the scroll bars, using a new 'hand' mouse pointer.
To access the new 'hand' mouse pointer and pan around the bar chart, hold down ALT on the keyboard then click and drag in the bar chart, holding down the left mouse button as you do so. As you click and drag, the mouse pointer changes to
You can pan around the right-hand sections of the resource usage view pane and the Line of Balance pane, and around both sections of the histogram pane, in the same way.
|
DevOps Work Item | 6803 | ||||
Category | Library Explorer | ||||
Summary | Copy and paste lists of codes, resources and users into Library Explorer. | ||||
Description |
You can now copy and paste lists of codes, consumable resources, permanent resources and users into Library Explorer. This speeds up the process of setting up new projects in situations where a list of these items is available in another application.
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.
|
DevOps Work Item | 6893 | ||||
Category | Asta Vision | ||||
Summary | Create Asta Vision projects from within Asta Powerproject. | ||||
Description |
Before this release, to create new projects in Asta Vision you had to access the Asta Vision web app in a web browser, then navigate to the Create Project from Template page.
You can now create Asta Vision projects from within Asta Powerproject, using the New Vision Project control that has been added to the New tab of the Backstage view. Clicking this control launches the Asta Vision Create Project from Template page within the Asta Powerproject Backstage view, so you can create new Asta Vision projects without having to access the Asta Vision web app separately.
More information on creating Asta Vision projects from within Asta Powerproject |
DevOps Work Item | 7292 | ||||
Category | Import and export | ||||
Summary | Implied links between tasks on the same bar are lost when exporting a project into XER format and creating a work breakdown structure in the exported project based on the project's WBS. | ||||
Description | Before this release, if you exported a project to Primavera software in XER format and chose to create a work breakdown structure in the exported project based on the project's WBS, rather than based on the natural order hierarchy of charts and summary groups, implied links between tasks on the same bar were lost in the resulting file. | ||||
Resolution |
A new Export implied bar links for WBS hierarchy check box has been added to the Primavera XML & XER Export Options dialog. If you select this check box, which becomes available if you choose to create a work breakdown structure in the exported project based on the project's WBS, links are created between tasks that are located on the same bar in the exported project, which capture the link logic of the 'implied links' between the tasks on the bar.
If you clear this check box, these links are not created between tasks that are located on the same bar. This enables you to export projects using the behaviour as it used to be before this release.
If a bar is configured to allow the tasks on that bar to overlap, no links between the tasks on that bar are created in the exported project, regardless of whether the Export implied bar links for WBS hierarchy check box is selected.
More information on exporting projects to Primavera software
More information on setting up a work breakdown structure (WBS)
More information on implied links
More information on specifying that tasks on a bar can overlap |
DevOps Work Item | 7426 | ||||
Category | Project Viewer | ||||
Summary | Line of Balance View control not available on the Project Viewer Ribbon when a Line of Balance graph exists in the current view. | ||||
Description | If the view you are currently looking at in Project Viewer contains a Line of Balance graph, you should be able to use the Line of Balance View control, in the Show group on the Home tab of the Ribbon, to toggle the graph on and off. Before this release, you could not do this. | ||||
Resolution |
If the view you are currently looking at in Project Viewer contains a Line of Balance graph, you can now use the Line of Balance View control, in the Show group on the Home tab of the Ribbon, to toggle the graph on and off.
More information on turning Line of Balance graphs on and off in Project Viewer |
DevOps Work Item | 8104 | ||||
Category | Reschedule | ||||
Summary | Reschedule report incorrectly identifies certain milestones as having been progressed out of sequence. | ||||
Description | Before this release, if a completed milestone had a completed successor task, the 'Out of sequence progress - Incomplete tasks which logically precede completed or in-progress tasks' section of the reschedule report incorrectly reported the milestone as being incomplete, even though both items were complete. | ||||
Resolution |
The 'Out of sequence progress - Incomplete tasks which logically precede completed or in-progress tasks' section of the reschedule report no longer incorrectly includes completed milestones that have a completed successor task.
More information on working with out of sequence progress
|
DevOps Work Item | 8251 | ||||
Category | Project view | ||||
Summary | Code library appearance icons are not resized correctly when the Windows Display 'Scale' percentage is changed. | ||||
Description | A customer reported that if they changed the Windows Display 'Scale' percentage to change the size of text, apps and other icons, the icons in the project view that illustrate the appearance of each code library entry did not change size correctly; the higher the Scale percentage, the smaller the icons appeared. | ||||
Resolution |
The icons in the project view that illustrate the appearance of each code library entry now change size correctly when you change the Windows Display 'Scale' percentage.
More information on displaying the appearance of codes in the project view |
DevOps Work Item | 8407 | ||||
Category | Calendars | ||||
Summary | Calendars in the Asta Powerproject version 17 templates give the wrong dates for the 2026 Easter bank holidays. | ||||
Description | A customer reported that in the calendars within the Asta Powerproject version 17 templates, the dates of the 2026 Easter bank holidays were incorrect. | ||||
Resolution |
The dates of the 2026 Easter bank holidays have been corrected in the calendars within the Asta Powerproject version 17 templates.
|
DevOps Work Item | 8971 | ||||
Category | Printing | ||||
Summary | Line numbers do not appear in printouts if you specify a different appearance for levels of the project hierarchy with the font colour set to white. | ||||
Description | Before this release, if you used the Hierarchy Appearance dialog to specify a different appearance for levels of the project hierarchy and set the font colour to white, line numbers did not appear in printouts. | ||||
Resolution |
The line numbers did not appear because the printing process was incorrectly applying the hierarchy appearance font colour to the line numbers, which did not show up against the white background. The printing process no longer applies the hierarchy appearance font colour to the numbers in the Line column, so these numbers are always visible in printouts.
More information on highlighting bars that indicate the project hierarchy
|
DevOps Work Item | 9142 | ||||
Category | Asta Vision | ||||
Summary | Unable to copy a view in which a histogram is displayed to a project that has been checked out from Asta Vision. | ||||
Description | A customer reported that they were unable to copy a view in which a histogram was displayed from one project to project that had been checked out from Asta Vision. | ||||
Resolution |
It is now possible to copy views in which histograms are displayed to projects that have been checked out from Asta Vision.
|
DevOps Work Item | 9231 | ||||
Category | Asta Vision Live/Ribbon | ||||
Summary | Adding the Chat command to the Vision group on the Ribbon removes the group from the Ribbon. | ||||
Description | Before this release, if you opened an Asta Vision Live project in collaboration mode and attempted to add the Chat command to the Vision group, on the Home tab of the Ribbon, the entire Vision group was removed from the Ribbon. | ||||
Resolution |
You are now able to add the Chat command to the Vision group on the Home tab of the Ribbon without the Vision group being removed from the Ribbon.
More information on collaborating with other users on Asta Vision programmes
More information on customising the Ribbon
|
DevOps Work Item | 9287 | ||||
Category | Views | ||||
Summary | An error occurs if you click View in the Ribbon, when no views are configured to appear on the menu. | ||||
Description | Before this release, in the Dutch version of Asta Powerproject, if you clicked the View control, in the Views group, on the View tab of the Ribbon, when no views are configured to appear on the menu, a virtual thread error occurred. | ||||
Resolution |
An error no longer occurs when you click the View control when no views are configured to appear on the menu.
|
DevOps Work Item | 9701 | ||||
Category | Bar chart/Resources | ||||
Summary | Colour-code tasks in the bar chart using the appearance of the resources that have been assigned to them. | ||||
Description |
You have always been able to colour-code tasks in the bar chart using the appearance of the codes that have been assigned to them. Now, as an alternative, you can colour-code tasks in the bar chart using the appearance of the permanent or consumable resources that have been assigned to them. Colour-coding tasks by resource is a good way of identifying the resources that have been assigned to tasks without having to display resource allocation bars in the bar chart.
To enable you to colour-code tasks in the bar chart using resources, new Consumable resources and Permanent resources radio buttons have been added to the Task appearance group, on the Tasks tab of the Format Bar Chart dialog. If you click one of these radio buttons then click the Display button, a new Multiple Display Resources dialog appears, which you can use to specify which resources to use to colour tasks in the bar chart.
New Display Resource and Multiple Display Resource menu commands have been added to the menu that appears when you right-click a resource or resource folder in the project view, enabling you to specify which resources to use to colour-code tasks without having to access the Format Bar Chart dialog.
More information on colour-coding tasks using the appearance of their assigned resources
More information on the Tasks tab of the Format Bar Chart dialog
|
DevOps Work Item | 9825 | ||||
Category | Asta Site Progress | ||||
Summary | Enable federation for Asta Site Progress, to enable users to sign in using their Microsoft Entra ID credentials. | ||||
Description |
You can now enable federation for Asta Site Progress, which enables users to sign in using their Microsoft Entra ID credentials.
|
DevOps Work Item | 10224 | ||||
Category | Help | ||||
Summary | Typographical error in the 'File Open Error dialog' Help topic. | ||||
Description | The 'File Open Error dialog' Help topic included a typographical error in the 'How to access the File Open Error dialog' section: the word 'duration' appeared in place of the word 'location'. | ||||
Resolution |
This error has been corrected.
|
DevOps Work Item | 10387/10602 | ||||
Category | Asta Powerproject 4D | ||||
Summary | Asta Powerproject 4D stops responding when attempting to open a particular 3D model. | ||||
Description | A customer reported that when they attempted to open a particular 3D model, Asta Powerproject 4D stopped responding. | ||||
Resolution |
The 3D model in question was extremely large and its particular properties meant that it took Asta Powerproject 4D a long time to open it - which made it look as if Asta Powerproject had stopped responding. Asta Powerproject 4D has been enhanced so that it is now able to open very large 3D models much more quickly.
|
DevOps Work Item | 10547 | ||||
Category | Asta Vision Live/Asta Enterprise | ||||
Summary | Tasks remain locked permanently to users when attempting to recover a failed collaboration or Asta Enterprise session. | ||||
Description | Since the release of Asta Powerproject version 17, if a collaboration session or Asta Enterprise session failed while a task was locked to a user - for example, if Asta Powerproject crashed for some reason before a user's edit could be saved - neither clicking Resume nor Abandon on the Select Failed Connection dialog enabled you to unlock the task. | ||||
Resolution |
It is now possible to unlock tasks that were locked to a user when a collaboration session or Asta Enterprise session failed.
More information on collaborating with other users on Asta Vision programmes
|
DevOps Work Item | 11062 | ||||
Category | Printing | ||||
Summary | Cell shading that highlights baseline variance in German builds of Asta Powerproject is overwritten by project hierarchy shading in printouts. | ||||
Description | German builds of Asta Powerproject include the ability to shade spreadsheet cells in which there is a variance between the live data and a baseline. In the spreadsheet, this variance shading appears on top of project hierarchy shading, but in printouts it is overwritten by project hierarchy shading. | ||||
Resolution |
In German builds of Asta Powerproject, spreadsheet cell variance shading is no longer overwritten by project hierarchy shading in printouts.
More information on highlighting bars that indicate the project hierarchy |
DevOps Work Item | 11435 | ||||
Category | Filters | ||||
Summary | Show only relevant allocations check box hides all allocations in task-based filters in Asta Powerproject version 17. | ||||
Description | A customer reported that when the Show only relevant allocations check box in the Filter Wizard was selected for a task-based filter, allocations of all resources were hidden in Asta Powerproject version 17; in version 16, only allocations of irrelevant resources were hidden. | ||||
Resolution |
The Show only relevant allocations check box in the Filter Wizard now hides only allocations of irrelevant resources, as it did in version 16.
More information on creating new filters using the Filter Wizard |