- Dashboard Designer: The Admin now has the ability to delete and rename Dashboards from the Designer area.
- Dashboard: Notebook entries in the dashboard were showing incorrect values. The mapping for notebook fields was incorrect. This has been fixed.
- Dashboard: Improved performance of the dashboard. We used to loop through all of the timephase data 2 times. Once to create the normal records with costs and again to create the same records with contingency information. Now, the system loops only 1 time and creates both sets of records.
- WBS Summary Report: If the admin user went to Admin → Projects → Edit Project → Reports and turned on the WBS Summary Report Settings → Estimate Type Basis Code option to say With Description, then the WBS Summary Report would hang and never load. This is because the WBS Summary Report was not properly grouping the graph labels with the description added. This caused 1000s of entries to improperly be fed into the graph and caused the system to hang. This has been corrected.
- Format 1030 Report: If you selected any project besides the default project on this report, you would get a Javascript error and the report would not load. This has now been corrected.
- The Import, Export, Backup Project & Restore Project Tasks object now supports Constraint Date.
- Backing up a project with duplicated Format 1030 codes for the same Resource Code ID but in different projects causes costs to inflate on restore. Fixed the issue by insuring only the project’s current resource file is exported. Also, fixed client’s data to remove duplicated format 1030 mappings (LCCF). This was due to a bug previously in Format 1030 that was corrected but the data was not.
- Copy Project: When copying a project with a Format 1030 Code file, the reference to the 1030 code file was lost. This is now corrected.
- Codes / Resource Codes: When creating or updating a code, the Name and Resource ID fields are now automatically trimmed when you save the code. This insures that you do not have any spaces at the beginning or end of your code name. Some clients had accidentally added a space to some of their codes. Then, they would export those codes and try to reimport them again without the trailing space. Dash360 would then throw an error stating that code did not exist because the space was missing from the import file. This was a tricky bug because it’s hard to see that extra space. This has now been fixed and with this update any data already in your database in these 2 fields has been trimmed.