- Estimating → Cost Estimate Reports → Cache Data: All of the cost estimating reports now use a cache. This cache greatly speeds up all of the cost estimating reports. However, if you change data in Dash360, then you will have to click the Refresh button on your Report / Project to get the new data to load.
- Estimating → Cost Estimate Reports → Optional Cache: You can now cache the Cost Summary Reports so they run more quickly. By default, the cache is turned off. To turn it on, go to the Admin → Projects → Registry tab and look for the registry key called “Enable-Reporting-Cache”. If this is turned “On” for a project, then that project’s Cost Estimating Reports will be cached. To clear the cache and reload the data, click the refresh button. There is also a cache timestamp that will appear when the cache is turned on so that you can see the age of the cached data. There is also a nightly job that now runs that will cache all of your Cost Estimating Reports every night.
- Recalculate Unit Cost: The unit cost field on resource assignments is now reset when a project is recalculated. This reset sometimes needs to occur when a unit cost field should be emptied out when a non-labor / travel rate is changed from 1 to a real value.
- Admin → Projects: You can now select up to 3 projects to send to Tableau. Dash360 now sends these 3 favorite projects and your default project to Tableau for reporting.
- Admin → Projects → Registry: There is a new “Time-Zone” registry setting that allows you to select the time zone that you’d like to see time represented in Dash360. There are only a few places where a time shows up. This is a per project registry setting so you can have a different time zone per project.
- Admin → Import / Export → Export Resource Assignments: You can now choose the cost class you want to export when exporting Resource Assignments.
- Bug Fixes: 2 bugs were fixed in this release. One occurred when you recalculated a project and that project had resource assignments with start / finish dates but no cost data. The system would throw an error. Another issue was slowing down Dash360 and accidentally loading User History data on every page of the application. Removing this extra call that was not needed should help to speed up some customer systems.

