Context: As we work with clients to leverage the benefits of Project Server, clients frequently ask how they can migrate locally-saved master schedules to Project Server while retaining cross-project dependencies.
The objective of this blog is not to cover the broader topic of schedule migration and general best practice, or how to create cross project dependencies (great link here) but rather to specifically identify a sequence of events that, in my experience, retains the cross-project dependencies for this very specific scenario.
- Open Project Professional 2013 (I have not tested this method with earlier versions) and connect to your PWA environment
- Open your local master project
- Remove the embedded sub-projects (if present) but ensure the cross-project dependencies are retained, save and close the master project
- Open the local dependant projects individually and select save as to save them into Project Server (you can change the names if needed)
- Open the local master project and re-insert the sub-projects from the Project Server database. Add the successors field and observe that the successors in the master project update with the new path to the now enterprise sub-projects
- Save the master project into the server and, as the save completes, observe that the sub-project predecessor links will update to the new master project (or other enterprise sub- projects)
- Check each project and using the Manage Links option remove old links to local projects (there will be duplicate links – those to local files and those to enterprise projects)In my testing, if the local master project is saved first and then the enterprise sub-projects inserted, the links don’t automatically update.
I would like to hear of anyone else’s experiences in this particular area so please post them (successful or otherwise) below.