Custom project outline codes sequence problem

[JP]

We created a custom project outline codes called project status.
1Low Effort Task
2Inprocess
2Testing
2Closed
2Etc...
1 Medium Effort Task
2Inprocess
2Testing
2Closed
2Etc...
1Etc
2Etc

Sometimes when we try to select the code they are out of order or sequence
i.e The level 2 medium effort task end up under the level 1 Low effort and
visa versa. The level 2 tasks some time display as level 1 tasks.

We installed the SP2 and ran the suggested scrip to fix the problem. It
doesn't seem to happen all the time. Tis week it is happing all the time. You
can even go in to enterprose global codes open the custom outline code select
the edit look up table and they are out of order. Close the code and reopen
and they are now back in order. Any ideas. This is also play havoc on the
ProjectInitiation screen. The are always out of order. I can live with that
since it is a freebee from MS.

Jack

 

[Gary L. Chefetz [MVP]]

JP:

Are you certain that you have SP2a applied to Project Server?

 

[JP]

Yes. Atleast that is what my Admin tells me.

JP:

Are you certain that you have SP2a applied to Project Server?

 

[Gary L. Chefetz [MVP]]

The symptoms you describe were rampant when Microsoft released the first
version of SP2 and recalled it. The new version of the SP is SP2a. If by
chance your admin installed the older one, which is still in circulation
here and there, then it would explain the problem. The other possibility is
that you violated the bad character rule in creating the codes or their
values. The field names should contain only alpha-numeric characters and no
dashes, commas, or other special characters.

 

[JP]

Gary,
We are going to re-install the SP2a. Also, I just checked to see if we have
invalid characters. The codes are out of order. I don't see any invalid
characters except a possible tab or something. If a project manager is in a
project, and I go in the Enterprise outline codes would that affect the
order? I can't see how? Anyway, I'll have the admin re-install sp2a and run
the script. I'll check again for invalid characters spaces or tabs as well.