Asta Powerproject version 15.0.01.332 release notes
This topic lists the issues that have been addressed in the Asta Powerproject version 15.0.01.332 fast track release.
| Issue | 31052 | ||||
| Category | Asta Enterprise | ||||
| Summary | Unable to convert databases when using the MSOLEDBSQL driver in the Serveradmin connection string. | ||||
| Description | Asta Enterprise has supported the MSOLEDBSQL driver since the release of version 14.0.03.446. However, since the release of version 15.0.01, it has not been possible to convert databases to version 15.0.01 when using this driver. | ||||
| Resolution | It is now possible to convert databases to version 15.0.01 when using the MSOLEDBSQL driver. | ||||
| Issue | 31055/31066 | ||||
| Category | Import and export | ||||
| Summary | Error reported when importing an XER file. | ||||
| Description | A customer reported that an "Invalid date parameter" error was reported when they tried to import an XER file into Asta Powerproject version 15.0.01. | ||||
| Resolution | This error was caused by Asta Powerproject assigning incorrect dates to calendar exceptions that covered the whole day during the import process. This error has now been resolved. | ||||
| Issue | 31056 | ||||
| Category | Spreadsheet | ||||
| Summary | Original start date not retained when an actual start date is entered into the spreadsheet. | ||||
| Description | The Original start field is supposed to be kept in step with the start date of tasks until a task is started, at which point it should be fixed at the start date of the task immediately before progress was entered. Before this release, the original start date was not retained in this field if an actual start date was entered into the spreadsheet; the field was updated incorrectly to match the actual start date. | ||||
| Resolution | The Original start field now retains the correct date when an actual start date is entered into the spreadsheet. | ||||
| Issue | 31057/31095/31096/31113 | ||||
| Category | Progress | ||||
| Summary | Progress line does not "jag" backwards to show progress behind schedule for some summary tasks. | ||||
| Description | A customer reported that since the release of version 15.0.01, the progress line did not "jag" backwards to show progress behind schedule for some summary tasks in a project. Three other related issues regarding the display of progress on summary tasks were raised. | ||||
| Resolution | This problem occurred in summary groups that contained some tasks that were ahead of schedule and others that were behind schedule. The progress line now jags backwards correctly for summary tasks if progress is behind schedule and progress is now displayed correctly for summary tasks. | ||||
| Issue | 31061 | ||||
| Category | Printing | ||||
| Summary | Error reported when attempting to print a project with a code library legend included on all or relevant pages. | ||||
| Description | A customer reported that an error was reported when they tried to print a project with a code library legend included on all or relevant pages. | ||||
| Resolution | It is now possible to print with a code library legend included on all or relevant pages without an error being reported. | ||||
| Issue | 31065 | ||||
| Category | Import and export | ||||
| Summary | Links exported incorrectly to XML and XER format if tasks have been progressed. | ||||
| Description | A customer reported that since the release of version 15.0.01, if they exported a project to Primavera software in XML or XER format, links to or from tasks that have been progressed disappeared. | ||||
| Resolution | Links to or from tasks that have been progressed are now exported correctly to XML or XER format. | ||||
| Issue | 31067 | ||||
| Category | Project hierarchy | ||||
| Summary | Top-level summaries take a long time to expand and contract. | ||||
| Description | A customer reported that since the release of version 15.0.01, top-level summaries in a project were taking a long time to expand and contract. | ||||
| Resolution | Summaries now expand and contract as quickly as they did before the release of version 15.0.01. | ||||
| Issue | 31071 | ||||
| Category | General | ||||
| Summary | Fields missing from the Conditional tab of the Ruling Lines Properties dialog. | ||||
| Description | A customer reported that since the release of version 15.0.01, all fields except Name were missing from the Conditional tab of the Ruling Lines Properties dialog. | ||||
| Resolution | All fields on the Conditional tab of the Ruling Lines Properties dialog have now been reinstated. | ||||
| Issue | 31073 | ||||
| Category | Import and export | ||||
| Summary | Error reported when exporting a project containing tasks with elapsed durations to XER format. | ||||
| Description | A customer reported that an "Unknown exception occurred (bad optional access)" error was reported when they tried to export a project containing tasks with elapsed durations to Primavera software in XER format. | ||||
| Resolution | This error was caused by Asta Powerproject exporting the elapsed calendar incorrectly. This error has now been resolved. | ||||
| Issue | 31081 | ||||
| Category | Printing | ||||
| Summary | Unable to print a project when in "jagged progress" mode. | ||||
| Description | A customer reported that since the release of version 15.0.01, they were unable to print a project when the view was displayed in "jagged progress" mode. | ||||
| Resolution | The error that prevented this project from printing has been resolved. | ||||
| Issue | 31086 | ||||
| Category | Asta Siteprogress Mobile | ||||
| Summary | Asta Powerproject crashes when you click on a dated note that has been imported from Asta Siteprogress Mobile. | ||||
| Description | Before this release, Asta Powerproject could crash if you clicked on a dated note that had been imported from Asta Siteprogress Mobile. | ||||
| Resolution | The error that caused this crash has been resolved. | ||||
| Issue | 31110 | ||||
| Category | Views | ||||
| Summary | Cannot display a view in "jagged progress" mode. | ||||
| Description | A customer reported that since the release of version 15.0.01, they were unable to display a view in "jagged progress" mode. | ||||
| Resolution | The error that prevented this project from displaying a view in "jagged progress" mode has been resolved. | ||||
| Issue | 31111 | ||||
| Category | Asta Powerproject 4D | ||||
| Summary | IFC produce assignments lost when moving to a different revision of an IFC model. | ||||
| Description | A customer reported that some product assignments were lost when moving to a different revision of an IFC model in Asta Powerproject 4D. | ||||
| Resolution | The functionality that copies splits from one revision of an IFC model to another was not working correctly, resulting in this problem. This problem has now been resolved. | ||||
| Issue | 31117 | ||||
| Category | Import and export | ||||
| Summary | Cannot open a project in Primavera software when exported in XML format. | ||||
| Description | A customer reported that since the release of version 15.0.01, they were unable to open a project in Primavera software that had been exported from Asta Powerproject in XML format; if the project was exported in XER format, it was possible to open it in Primavera software. | ||||
| Resolution | This problem was caused by two tasks having duplicate Start to Start links. Asta Powerproject handles this situation, as does Primavera software when a project is exported in XER format, but Primavera could not handle this situation when a project was exported in XML format. This problem has now been resolved. | ||||
| Issue | 31118 | ||||
| Category | Printing | ||||
| Summary | Page breaks ignored by Print Preview in projects converted from version 14. | ||||
| Description | A customer reported that since the release of version 15.0.01, page breaks were ignored by Print Preview in projects that had been converted from version 14 format. | ||||
| Resolution | The error that prevented page breaks from being respected has been resolved. | ||||
| Issue | 31123 | ||||
| Category | Printing | ||||
| Summary | Histogram pane appears blank in Print Preview. | ||||
| Description | A customer reported that since the release of version 15.0.01, the histogram pane appeared blank in Print Preview when trying to print it on its own. | ||||
| Resolution | The error that prevented the histogram pane from appearing in Print Preview has been resolved. | ||||
