In a previous post I talked about assumptions and the reality of data access and security when configuring a simple "hands off" timesheet solution in 2010, and some concerns around functionality that is made available to users by default. The other areas of concern for me were: 3 - Limitations of creating projects from templates via PWA 4 - curious behaviour of the auto-publish function when calculating Actual Cost So here's some more little tidbits of information that I hope may help... Limitations of creating projects from templates via PWA (Project.CreateProjectFromTemplate method) As part of my solution I wanted to allow a two phase project to be created, with Phase 2 tasks disabled when the project is produced to avoid these tasks being available via the Timesheet function without the need to work via MS Project. Then I wanted the new phase tasks to be activated at a given point in the schedule ideally via PWA. To do this I... - Created a MSP
sharing the love