Custom Formula Value Being Converted to Text on Summary Tasks

[rw]

We are using a custom formula on a text field to track various date
scenarios in our plan. We intentionally did not switch on the
calculation for task and group summary lines as we don't want to see
them at this level.

Here is the problem: When we create a new task in the plan, project
evaluates the formula correctly. Once we make it a summary task,
project no longer evaluates the formula for the task. However instead
of clearing out the field, project takes the original calculated value
and converts it to text.

Outside of running the formula on both task and summary levels, any
suggestions on how to prevent this from happening or a way to code for
it?

Much Appreciated. -rw

Note 1: We use a combination of Project 2000 and 2002.

Note 2: It seem you can differentiate between a calculated value vs.
text by clicking on the custom field and viewing the value in the text
edit entry bar on the top on the window. Black seems to be text vs.
uneditable light gray which is shows it was evaluated by the custom
formula.

 

[Gary L. Chefetz [MVP]]

RW:

This is the expected behavior of summary tasks. Summary tasks *should* be
created from tasks containing no prior values, as all prior values are
preserved in the underlying data. Making a summary task changes the behavior
of the task, not its underlying values. Therefore, if you mistakenly make a
task a summary task, you can quickly revert back to normal without losing
data. This is effectively the price we pay for having this ability to
recover, which IMO far outweighs the annoyance of the value preservation.

 

[Ed Morrison]

You can also check the [Summary] value in your formula to see if the task is
a summary task.

--
Ed Morrison
msProjectExperts
"We wrote the books on Project Server"
http://www.msprojectexperts.com
FAQ - http://www.projectserverexperts.com