Editing custom field through PWA

[anovak]

I'm sure I could test this, but if a user edits custom field values at
the project level via PWA, I assume that there is no need to back
through the client software and republish, correct?

Thanks,
Andy Novak
UNT

 

[Jack Dahlgren]

If they edit and publish the field through PWA then there is no need to go
into Project Professional to republish.

However, there are a few issues with Project Server 2007 which are related
to custom fields. For example, if you have a calculated field or an
indicator for the custom field, it will not recalculate without going
through the Project Professional client.

-Jack Dahlgren
http://zo-d.com/blog

 

[Dale Howard [MVP]]

Andy --

In addition to Jack's sage comments, I think you would be wise to avoid
publishing projects using the PWA interface at all. When the publishing
operation is performed from PWA, there are several known bugs that can
either "wipe out" your custom enterprise Project field values in the
published project, or "scramble" the lookup table values for custom
enterprise Project fields in that project. Therefore, our advice for the
moment is this:

1. The PM should accept all task updates from within the Microsoft Project
2007 application. He/she should open any project for which their are
pending updates, and the system will tell him/her there are updates pending.
He/she can walk through a very cool process of approving and accepting the
updates directly into the project.

2. After studying the effect of the updates, doing variance analysis, and
plan revision, the PM can then click File - Publish to publish the latest
schedule changes.

This approach totally eliminates the problems with publishing from within
PWA. Hope this helps.

 

[anovak]

Andy--

In addition to Jack's sage comments, I think you would be wise to avoid
publishing projects using the PWA interface at all. When the publishing
operation is performed from PWA, there are several known bugs that can
either "wipe out" your custom enterprise Project field values in the
published project, or "scramble" the lookup table values for custom
enterprise Project fields in that project. Therefore, our advice for the
moment is this:

1. The PM should accept all task updates from within the Microsoft Project
2007 application. He/she should open any project for which their are
pending updates, and the system will tell him/her there are updates pending.
He/she can walk through a very cool process of approving and accepting the
updates directly into the project.

2. After studying the effect of the updates, doing variance analysis, and
plan revision, the PM can then click File - Publish to publish the latest
schedule changes.

This approach totally eliminates the problems with publishing from within
PWA. Hope this helps.

I've certainly experienced these that you talk about and will, at
least until SP1, suggest that folks always use the client for updating
meta data

Thanks!
Andy