#ERROR when formula used

[anovak]

I created an enterprise text field at the task level (Enterprise Task
Text2). Two problems:

1. After I save Enterprise Global and add the field to a particular
view (Copy of Task Summary), the system-level column label appears
(Enterprise Task Text2) instead of "Schedule" (which I renamed the
field in Enterprise Global). I
added to project level enterprise fields called "Performer" and
"Product" and they display just fine within the modified PWA view.
What's the deal???

2. I pasted a formula into the enterprise text field. When I view the
field in the view within a project in PWA, all lines are blank. When I
view using the client, "#ERROR" is showing in each row but no clue as
to what the error is.

Please advise. Thanks, Andy

 

[Dale Howard [MVP]]

Andy --

1. After creating the field, and then saving and closing the Enterprise
Global file, you must exit and relaunch Microsoft Project Professional to
"refresh" the Enterprise Global file.

2. When you insert the new custom field into a Table in Microsoft Project
Professional, you need to press the F9 key to recalculate the project. Then
you need to click Collaborate - Publish - All Information to "push" this
information to PWA.

Hope this helps.

 

[Dale Howard [MVP]]

Andy --

1. After creating the field, and then saving and closing the Enterprise
Global file, you must exit and relaunch Microsoft Project Professional to
"refresh" the Enterprise Global file.

2. When you insert the new custom field into a Table in Microsoft Project
Professional, you need to press the F9 key to recalculate the project. Then
you need to click Collaborate - Publish - All Information to "push" this
information to PWA.

Hope this helps.

 

[anovak]

Dale, then does it makes sense to use local custom fields exclusively
for this (ie., red/yellow/green) and force the use of templates that
contain them rather than use enterprise fields in order to stay away
from the F9 requirement? The stoplights we are using are for the
benefit of senior mgt, not necessarily the PMs and it seem to me that
it would be better to remove the potential F9 bottleneck. Please
advise.

Thanks,
Andy Novak
University of North Texas

 

[Dale Howard [MVP]]

Andy --

Use enterprise custom Task fields for this purpose. Your project managers
will only need to press the F9 key one time to recalculate their projects.
Hope this helps.

 

[Gary L. Chefetz [MVP]]

Andy:

Don't name a custom field "Schedule" as this is a reserved word.

 

[anovak]

Gary, one more thing. I succeeded in the above technique and ended up
with a custom Project task view that showed stoplight indicators for
each task (yeah!!).

Now then, when I create a "Project Schedule" enterprise custom field at
the project level and import the "Task Schedule" stoplight I had just
had success with (both formula and graphical indicators are imported),
it doesn't seem to work.

I bring up the Project Information in each project to view the newly
created field and press F9 to recalculate, and nothing happens. After
I go through each project, hit F9 upon bringing up the Project
Information dialog box, republish all and save, I do not get the same
results. Yes, I've added the "Project Schedule" field to the Project
Center view.

Perhaps there's another little tip I haven't received yet that will
shed light on this.

Thanks
Andy Novak
University of North Texas

 

[Gary L. Chefetz [MVP]]

Andy:

Without the ability to examine your work, it's rather difficult to say
what's going wrong. Are you certain that the field structure is correct?

 

[anovak]

Gary, may I ask what you are referring to as "field structure"?

Thanks,
Andy

 

[Gary L. Chefetz [MVP]]

The structure of your filed customization. Are you certain there isn't a
silly typo in there?

 

[anovak]

Answer: I had to bring up the Enteprise Outline Code field "Project
Schedule" within the schedule grid before I could do a recalc.
Bringing that up in the Project Information dialog box wouldn't
accomodate.

Thanks,
Andy