Publishing routine when using MASTER projects.

J

John Sitka

Hi,

I'm in a situation where depending on which project is open or edited the
tasks are getting pushed twice.

That is if I edit publish from the MASTER project I get tasks in a PWA
hierarchical form

MASTER
- PROJECT 1
--SUMMARY TASK
---TASK

and

if I edit publish from PROJECT1 I get task hierarchy

PROJECT 1
-SUMMARY TASK
--TASK


Both task trees are visable when the resource logs in, duplicates? not
really...

So please share succssful editing/publishing procedure when using a MASTER,
SUB, SUB-SUB project set up.
I guess there are two cases
1.) where a Project Manager exploits a Master and he is Project Manager of
all SubProjects
2.) the Enterprise Manager uses the Master to gather all contributions from
the set of Progect Managers.

How to lock down one model or the other? Either by procedure or
configuration.
 
J

John Sitka

Maybe this is the root of the issue.

from "Help"
Note Typically, if you create master projects and subprojects, only the
subprojects are saved to the enterprise server. The master projects are only
saved on your local computer, unless your organization has specified that
they can be saved to the server. Saving the master projects to Microsoft
Office Project Server 2003 can result in erroneous reporting data. Microsoft
Office Project Professional 2003 and Project Server 2003 have built-in
reporting and analysis features that replace the need to create master
projects and subprojects.

Comments?
 
G

Gary L. Chefetz \(MVP\)

John:

Generally speaking, it's OK to save master projects in Project Server, but
it's a good idea not to allow publishing from them. Keep your publishing
activities in the individual project plans.

--

Gary L. Chefetz, MVP
"We wrote the book on Project Server
http://www.msprojectexperts.com

-
 
Top