Stoplight Indicator Fields -- Published Fields Display Wrong Names
Terry Peters
in the Project Server 2003 Enterprise Global Template to display Task Finish
Date Variance with Stoplight Indicators & added custom views to the Project
Center & Project Detail Views. D.H., we used your FAQ procedure, "How do I
create stoplight indicators..." and it made it a breeze. The custom fields
work correctly in calculating finish date variances.
However, in the Project Center view the field displays with the name
"Enterprise Text39" & in the Project Detail custom view, the field displays
with the name "Start 4", rather than displaying the custom name assigned to
these fields.
Did we miss something in the procedure steps? What can we do to get the
correct names to display in Project Web Access.
Thanks,
Terry
--
Terry Peters
Dale Howard [MVP] dot at dot
Several questions:
1. Specifically, what field(s) did you customize with the formula and
graphical indicators?
2. After you created the custom field(s), did any of your PM's open any of
their projects and press the F9 function key to recalculate the project?
3. If so, did any of your managers publish their projects using
Collaborate - Publish - All Information or Collaborate - Publish - Project
Plan?
Let us know.
--
Dale A. Howard [MVP]
Enterprise Project Trainer/Consultant
http://www.msprojectexperts.com
http://www.projectserverexperts.com
"We wrote the book on Project Server"
"Terry Peters" <Terry...@discussions.microsoft.com> wrote in message
news:EC85611E-8433-4115...@microsoft.com...
Terry Peters
(1) In Project Pro/Enterprise Global Template, we used the "Enterprise
Duration 1" to create a field labeled "Task Slippage" using the formula "Task
Slippage = [Finish Variance]" and displaying graphical indicators. Then we
created a custom field called "Project Slippage" using the "Enterprise
Project Duration 1" field by importing the formula and graphical indicators
from the "Task Slippage" field.
(2) The Server is just being customized now, so I am the only project
manager publishing at this point (working with Aaron and Dan from our INDY
class). I opened my one test project and used F9 to recalc the project.
(3) I then published the project using the Collaborate Menu.
So I believe we followed your steps to the letter, with the exception of the
custom field names. The graphical indicators and formulas are working
correctly--I have tested them.
I reviewed the setup yesterday while onsite. I thing I noticed in the
ADMIN/MANAGE VIEWS/MODIFY VIEW screens: The Project Center view I created
(called "PROJECT SUMMARY FOR EXECUTIVES") indicated that I had added to the
view the custom field "Enterprise Project Duration 1" but it did not
retain/display the specific name I gave the field in the Enterprise Global
Template; that is, it did not show the name "Project Slippage". I tried
adding it again, but it still loses the custom name of the Enterprise field
when I leave the MANAGE VIEWS/MODIFY VIEW screen.
One other difference I noted: I did not use a leading underscore character
when I named the custom fields and views as you did in your FAQ procedure. I
assumed it was placed there to put the custom element at the top of the menu,
but is there another reason that I overlooked?
Thanks much for your help (& Aaron and Dan say "Heh!"),
Terry
--
Terry Peters
Dale Howard [MVP] dot at dot
The problem that you are seeing is a problem I also saw at a client site
this past week (a custom field name appears in place of the new field name,
and it is the WRONG name, no less!). This problem has been documented a
couple of times in the newsgroup. We are researching this issue with
Microsoft. Keep watching in the newsgroup for a potential hotfix or
something to fix this problem.
Thanks for being so thorough in describing what you have done. It's not
your fault, my friend! :)
--
Dale A. Howard [MVP]
Enterprise Project Trainer/Consultant
http://www.msprojectexperts.com
http://www.projectserverexperts.com
"We wrote the book on Project Server"
"Terry Peters" <Terry...@discussions.microsoft.com> wrote in message
news:5C8567DF-8386-42F0...@microsoft.com...
Susan Cobb
I have had the same experience, but, only when I tried to use SQL 2005
instead of SQL 2000. Which version of SQL are you using?
Susan Cobb
susan...@synogistics.com
Terry Peters
Thanks a bunch! I will keep my eyes open. One thing that may be part of
the answer: Susan Cobb's response below! She is correct. This client is
using SQL Server 2005.
I will keep watching for an update.
Terry Peters
Thanks for your reply. You may have hit the problem on the nose. We are
using SQL Server 2005, which they had in place before we installed Project
Server 2003. I will pass that information along to the people at the client
site.
--
Terry Peters
Dale Howard [MVP] dot at dot
I just learned today that our client is using SQL Server 2005 as well. This
appears to be one common connection between everyone's problem. I will
advise when I know more from Microsoft. Thanks!
--
Dale A. Howard [MVP]
Enterprise Project Trainer/Consultant
http://www.msprojectexperts.com
http://www.projectserverexperts.com
"We wrote the book on Project Server"
"Terry Peters" <Terry...@discussions.microsoft.com> wrote in message
news:774F1CB8-7FDA-43FF...@microsoft.com...
Renke Holert [MVP]
> I just learned today that our client is using SQL Server 2005 as well. This
> appears to be one common connection between everyone's problem. I will
> advise when I know more from Microsoft. Thanks!
I'd like to add that the same issue occurs even with SQL Server 2005 SP1.
Dale, did you get any feedback from Microsoft? I will raise a support call as
well.
Thanks in advance
Renke
Renke Holert, Project MVP Germany
Linking Project Server with Lotus Notes and Microsoft Outlook
http://www.allocatus.com