Asta Powerproject version 17.1.3.035 release notes
This topic lists the issues that have been addressed in the Asta Powerproject version 17.1.3.035 release.
| DevOps Work Item | 3377 | ||||
| Category | File locations | ||||
| Summary | Specify file locations in Asta Powerproject that include the '%userprofile%' environmental variable. | ||||
| Description | A customer requested it should be possible to specify file locations in Asta Powerproject that include the '%userprofile%' environment variable. | ||||
| Resolution |
You can now specify file locations in Asta Powerproject that include the '%userprofile%' environment variable. This means that you can specify file locations that are within a user's profile folder. For example, you can now specify a file location of '%userprofile%\Templates\', or '%userprofile%\Documents', and these will be resolved into the individual user's Templates or Documents folder.
You can also use the '%userprofile%' environment variable to specify file locations that exist in a user's OneDrive, or in SharePoint. For example, if you specify a file location of '%userprofile%\OneDrive\Documents\Powerproject\Projects\', this will be resolved to the folder in the user's OneDrive (note that the name of the user's OneDrive may differ from 'OneDrive'). |
||||
| DevOps Work Item | 3434 | ||||
| Category | Resource usage view | ||||
| Summary | Resource usage view changes not being saved. | ||||
| Description | A customer reported that if the customer selected a number of permanent resources in the resource usage view pane then saved and closed the project, the resources were not selected in the pane when they re-opened the project. | ||||
| Resolution | Before this release, the internal field in which the resource selections were saved had a maximum size limit, and if this limit was breached, the resource selections were lost. The field has been replaced by a variable length field, which has resolved the problem. | ||||
| DevOps Work Item | 3705 | ||||
| Category | Asta Powerproject 4D | ||||
| Summary | Some IFC models are not displayed when included in an IFC group model. | ||||
| Description | A customer reported that certain IFC models were not displayed in the IFC Model pane when they were included in an IFC group model, and the IFC group model was displayed. When displayed on their own, the IFC models appeared perfectly. | ||||
| Resolution | The relative positions of the IFC models were being calculated incorrectly. If the IFC models are reimported into this version of Asta Powerproject 4D, they will be displayed correctly when included in an IFC group model. | ||||
| DevOps Work Item | 3739 | ||||
| Category | Asta Enterprise | ||||
| Summary | Enterprise server service name changed back to 'Powerproject - Enterprise Server'. | ||||
| Description | In the initial release of Asta Powerproject version 17, the Enterprise server service name was changed to 'Asta Powerproject - Enterprise Server'. A request was made for this name to be changed back to 'Powerproject - Enterprise Server'. | ||||
| Resolution | The Enterprise server service name now appears in the Windows Services window as 'Powerproject - Enterprise Server', as it used to do before the release of Asta Powerproject version 17. | ||||
