Repost - Lock indivdual fields in 2007

S

Steve Scott

Sorry I need to repost this....

The below lack of functionality essentially could negate my company choosing
project server 2007 for Portfolio Office use becuase we could set up data
centrally against projects but then PMs could change the information that
needs to remain unchanged. Is there a workaround???

Rgds

Steve


Sorry, no !
 
D

Dale Howard [MVP]

Steve --

No, there is no way to prevent PM's from changing the values for custom
enterprise Project fields. Therefore, this makes it a training and
performance issue. If your Portfolio Office has the authority, then train
your PM's to leave the values along, hold them accountable for this
behavior, and deal harshly with anyone who tampers with the values. Hope
this helps.
 
B

Ben Howard

The only fields that can be locked are the baseline0 fields (there is a
permission to set the baseline which could be removed from Project Managers),
depending on your processes this might be sufficient. All other data is
amendable.
 
S

Steve Scott

thanks.



Ben Howard said:
The only fields that can be locked are the baseline0 fields (there is a
permission to set the baseline which could be removed from Project Managers),
depending on your processes this might be sufficient. All other data is
amendable.
Click to expand...
 
M

Marc Soester [MVP]

Hi Steve,

Sorry mate, the answer is still no. Custom fields do not contain security
functionality. I cant even think about the ability to custom develop a
solution that would give you the functionality ( I supose you could - not
beeing a developer).

What I could imagine is that you may be able to introduce a process within
your PMO office that checkes on a regular basis if Custom fields have
changed. I know that may be lots of manual work, but that is the only thing I
can think of as a workaround
 
S

Steve Scott

Could you also clarify are Project Properties and Enterprise fields the same
thing?

Rgds

Steve
 
D

Dale Howard [MVP]

Steve --

They are two entirely different things. There is no way to lock the Project
Properties either. Again, it is a training and performance issue with your
PM's. Hope this helps.
 
Top