R
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 as expected.
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.
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 as expected.
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.