How to tell if a project plan has been published - task assignments

P

Pam Clark

We have a problem with our PM's saving the plans to the
Project Server, but not actually publishing the task
assignments (Collaborate | Publish | All Information).
Does anyone know how to tell if a plan has been
published. I know when you save the plan to the server it
gets a .published extension, but I am looking for if the
plan's task assignments have been published. I want to
create a view which shows which plans have been published
and which haven't. I know in a perfect world all plans
would be published, but this is reality.

Thanks,

Pam
 
B

Bartolini

Hi Pam,

If the plan is published....the global resources with tasks assigned should
be notified.
If you want to...publish a plan your self and use you and the person next to
you ask resources...

Does this help?

~TS
 
G

Gary L. Chefetz [MVP]

Pam:

Easiest way is to go to the Resource Center in PWA and click on View
Resource Assignments. If the assignments show up in this view, they've been
published. If you don't see assignments for the project, they haven't been
published.
 
I

ITG_Mike

Pam, et al

I determine which projects are published by going into the SQL database and querying the Web Tables for projects without assignments. This method is not perfect, as projects that happen to have NO assignments (i.e. the resources will self-assign) appear the same as projects that have assignments but have not been published

WARNING..
- - - - - - -
Based on personal experience, projects that are saved, but not published, can cause HUGE problems in PS 2003 (if users are allowed to self-assign). Here is what happens. The PM assigns a resource to a task, saves, but does not publish the assignments. Then, after the project is saved, the resource adds themself to the same task (assign myself to an existing task) and begins to enter time. Later, the PM opens the schedule and publishes new and changed

At this point, the resource has two assignments on their timesheet for the same task. One of the two has time entered (the one they added). When the resource does an "Update All" this task is sent to the PM for approval. When the PM approves the task and updates the project, they will receive a message that some changes cannot be updated in project (it does not say so, but the change being referenced is the duplicate assignment). PWA then tells the PM to save the project file

If the file is saved (and PWA told the PM to save it) the duplicate assignment is made permanent and from then forward, any update or publication of the project returns a SYSTEM ERROR in the spooler

I have found to way to fix the project at this point. We have been forced to delete and recreate projects because of this

This problem has been reported to Microsoft and they agree what I describe can happen. One of their responses is that PM's should NEVER save without publishing. Though this is problematic for a PM that is making extensive project changes over a period of hours or days as they will be creating and deleting assignments which should not really be made visible to resources until the PM is done

Mik
 
Top