Skip to main content
February 23, 2022 Cost Estimate Form
  • When signing off on a work package, the system tracks the total cost of all resource assignments for your work package. With this change, now only resource assignments in the “Budget” cost class are included in the total.
  • If a project is locked or a CAM has read only access, then there was no way for a user to see the details of a resource assignment because all of the icons were hidden. Now, the edit icon still appears. Clicking it will allow you to view the resource assignment in a read-only state (you still cannot modify the data).
  • Export Timephased Data: If you had a Work Package without a resource assignment in one of the resource types (labor, nonlabor or travel), then the system would throw an error whenever trying to export the timephased data for all work packages. This has been corrected.
  • Copy / Move Resource Assignment: If you copy or move an Actual Resource Assignment to another work package, Dash360 was allowing this to occur even if there was already another Actual Resoure Assignment with the same Resource Code. This is not allowed in Dash360 as it breaks the Earned Value system. The code has been updated to instead throw an error to the user that the action is not allowed.
  • If you only had 1 Resource Assignment in the Labor, Non-Labor or Travel sections, then the process icons Copy / Move Resource Assignment dropdown menu was partially cut off. This has been corrected.
  • Built a feature to allow a user to apply the same basis code to all Resource Assignments in a Work Package. It is in the Details tab. Select a Basis code, click Save and all of the Resource Assignments for that Work Package will now have that basis code.
  • Add / Edit Resource Assignment: When modifying the Units of a Resource Assignment, entering a 0 or non-numeric character or space into the field would sometimes return an error. Now, the system assumes the value of zero (0) if you do not enter a valid value. The system also has been corrected to always be able to accept 0 as a valid value.
Dashboard
  • You can now export any dashboard component as an image allowing you to download charts and graphs from the dashboard and put them in other reports.
Schedule
  • Replaced the schedule sorting arrows with text.
  • Date format on the schedule dropdown was not always in the correct format. This is corrected.
  • Added a tooltip to the undo and redo buttons on the schedule.
  • Fixed the sorting so users can now sort by multiple columns.
Earned Value
  • Performance Index Report used to throw an error in some cases. This has been corrected.
General
  • All user’s can now upload a profile photo. If completed, your profile image will show up in the left-hand menu at the bottom of the screen next to your name.
  • When showing the column chooser on multiple reports through Dash360, the system would show 2 column choosers. One in the correct location and another at the bottom of the page (under the report). This one at the bottom of the page was an error and the object could not be removed from the screen. This has been corrected so it no longer appears.
Admin
  • The admin now has the ability to turn any user view they create into a system view. The admin can also set any system view as the default system view for all of their users of Dash360. User views have also been fixed to allow apostrophes in the view name (something that caused an error before).
  • Export Resource Assignments: When exporting Resource Assignments for projects with multiple Resource Assignment Notebook fields, the system would sometimes improperly put the notebook field data in the wrong Excel columns. This could cause a big mapping issue if this same file was used to reimport the data back into Dash360. This error has been corrected.
  • Import New Earned Resource Assignments (RA): If you import new Earned RAs without a RA ID, then the system will now present you with a mapping modal after import. In order for your earned RAs to make it into Dash360, you must now map them to their correct Budget counterpart. The system will do it’s best to map them for you, but if you have the same Resource Code in the same Work Package, then you will have to map them manually. This is required to insure Dash360 Earned Value (EV) calculation system can continue to calculate EV for you when you are bringing Earned data in from another system. This only impact Earned resource assignments during import. This also only impacts new Earned RA records without a filled in ID field. If you supply the ID, then the mapping for that record will not appear.
  • WBS Hierarchy: WBS hierarchal state is now preserved whenver you copy or restore a project.
  • Edit Project → WBS Tree: If no WBS code file was associated with a project, the WBS Tree would show weird results. This has been corrected.
  • If you had a WBS code file attached to multiple projects, modifying a WBS code would remove the WBS file from some of the multiple projects. This has been corrected so modifying a WBS code will not remove the WBS File from any of your projects.
  • Edit Resource Code: If you change the resource type (labor, nonlabor or travel) on a resource code, Dash360 will now automatically update all of the Resource Assignments created with that resource code and move them to the new resource type selected.
  • Export Resource Assignment Timephased Replace: Added the Project, WBS, Work Package, Resource Code and Resource Assignment Description to the export file.