10-19-2011 01:43 PM
We are working through a pilot PPM implementation and have stumbled into some challenges using dependencies.
Our Project Managers use MS Project Integration to upload their projects. Unfortunately it looks like there is no way to set external dependencies amongst tasks within MS Project (ie pointing into PPM). The only way to set is to upload the project plan and then go into the PPM Workplan view and add (or re-add) external dependencies to the tasks. Finally, when the project with the external dependency is downloaded, the depedency information is removed. Thus...when it is uploaded again, the dependency is cleared in PPM.
This is only for external dependencies. Internal dependencies (ie those within a project) do not appear to be affected.
Has anyone else run into this? Any best practices or work arounds?
10-19-2011 06:50 PM
Unfortunately, this is a limitation of PPM Plugin for MS Project, documented in the PM User Guide. All external dependencies will be removed from the work plan whenever a synchronization occurs between MSP and PPM.
There is no workaround as far as I can tell, but there are enhancement requests already opened to add this feature to PPM.
10-19-2011 07:57 PM
Thanks for the response. We were hoping someone had workarounds or best practices. We have talked to a few people at companies that have implemented PPM'; their projects (apparently) were not complex enough to warrant external dependencies. Our projects will often have multiple dependencies...especially the projects in a program.
10-20-2011 05:29 PM
On a related note, our Pre-Sales consultant has set up a meeting for next week with a/the PPM Product Manager to review this functionality. It sounds like this has already been submitted, which makes sense, though we'll talk through the request as well. Hopefully, we can get some movement with this feature.
04-03-2014 11:55 PM
we have implemented a solution in order to overcome this missing functionality in PPM.
Right now our customers can set up the external dependencies in PPM and they are not lost upon resync of the MS Project plan.
The solution is based on database update, so it is not supported by HP.
--remember to kudos people who helped solve your problem