Publishing Changes to Assignments

[Justin Fults]

I have had quite a bit of difficulty getting changes to
task information and resource assignments to successfully
publish to Project Server. My team accesses and udpates
progress on their assignments daily. So, the need to
publish changes arises on a daily basis.

I have tried a variety of different ways to do this and
my changes are not being published appropriately. I have
even selected to have the "Information Successfully
Published" prompt appear when information has been
successfully published (through the Options menu). I
receive the prompt and still do not see my changes in Web
Access.

My latest example I can share is the replacement of an
assigned resource to a task. When I check out and open
the Project file in Professional, the appropriate
resource is shown as being assigned to the task. But,
after successfully (allegedly) republishing assignments
the original resource remains assigned to the task.

Any suggestions? Please e-mail me.

Thanks,
Justin

 

[Gary Chefetz [MVP]]

Justin:

How do you know the original resource is still assigned to the task? What
evidence are you relying on? If you remove a resource from a task and
republish it, that should set a red-X indicator in the original resources
timesheet which tells the resource it's ok to hide the task. Is the new
resource not receiving the assignment?

 

[Justin Fults]

Hi Gary:

Thanks for the response.

Here is my evidence:

1. I had the Project file checked out and opened in
Project Pro. I replaced a resource assigned to a task
with another. I leveled the plan, saved it (thus
publishing "All Information" to Project Server. I
received the "Information Successfully Published" message.

2. About 1/2 later I was told that the new assignment
was not appearing in the newly assigned resources' My
Tasks View in Web Access.

3. I then went to Project Web Access, clicked on the
Resources link, then the Resource Assignments View. I
did a search for the "Unique ID" of the task. I found a
single instance of that task. While in this view, in the
Resource Name column, the Original Resource was still
shown as being assigned to this task.

After some additional time (a couple hours) the change
has appeared as it should. However, this prompted me to
look through more of my data to see if there were any
additional synchronization issues. Sure enough, I have
found a number of tasks that are marked as complete (and
have been for some time) in the Project Pro file, but are
show as incomplete on Web Access.

What is the best way to publish project information? I
currently have Pro set to publish all information each
time I save the file. I do this multiple time daily.
Our project plan changes very often. Is there a certain
amount of time I should allow the Server database to
update itself upon publishing project information? This
specific project plan is roughly 2000 tasks in size.
Could it be that Server is taking an inordinate amount of
time to slice up the data?

Let me know your thoughts.

Thanks,
Justin

 

[Gary Chefetz [MVP]]

Justin:

What's the scale of your implementation: number of resources, number of
plans, number of users? What kind of hardware?

I don't like the automatic publish feature, but that's personal preference.
For the tasks that you're currently showing as out-of-synch, what happens
when you republish those tasks, choosing to overwrite actual work in PWA?

--
Gary Chefetz [MVP]

*** Remember to look for line breaks in links posted to the news group, use
cut and paste for these.