Forcing WBS to be fixed length display

[Jim Aksel]

The WBS column displays such as
1.
1.1
1.1.1

Etc. Using a mask, I am able to force something such as
A.01.
A.01.01
A.01.01.01

However what I would like to do is also force the length of the WBS to
"right fill" with .00 so that it is always a fixed width ...

A.01.00.00.00
A.01.01.00.00
A.01.01.01.00
A.02.00.00.00

I attempted to modify a text1 field with a formula similar to:
trim(str([WBS]))+choose(len([WBS]),".00.00.00",".00.00",".00","")
I think if I play with that long enough I can get it to concatenate.

Additionally, The summary level tasks are not reporting a length on WBS if I
use the formala text2=len([WBS)]. That is Text2 is blank on summary lines.
So, my Text1 formula returns blank on summary tasks as well.

Should I reapproach the problem using [Outline Level]?

However, I would like two more things..
1. Stop the formula at Level 6 of the WBS... Just combine with an IF
statement I suppose? So anything at WBS level 7 or higher just carries the
same number as level 6 (or perhaps it's just blank). Probably a "Choose"
function combine with Len([WBS])?
2. I would rather do this in the WBS field itself rather than the Text1
field. I will settle for use of WBS field only , even if I am forced to
accept a display all the way down to Outline Level 99.

Any ideas? Remember, we can't let the software win....

Jim

 

[Jack Dahlgren]

Jim,

One of the conventions of WBS or other sorts of outline codes is that you
can tell by the length of the code where in the heirarchy it is.
For example if something has a WBS code of A I know it is top level at a
glance. I don't need to check all the digits. With your scheme I need to
read a lot to determine that

A.01.00.00.00.00 is a top level task while
A.01.00.00.00.01 is a bottom level task

However, if you follow convention and you see a list like this:

A
B.02
A.01.00.00.03.01

it is really clear where each of these things belong.

Making sense of a list of a dozen values like this:

A.00.00.00.00.00
B.02.00.00.00.00
A.01.00.00.03.01
A.00.00.02.01.05
B.02.00.00.00.10
A.01.01.00.03.01
A.00.00.04.00.00
B.02.00.10.00.08
A.01.00.00.03.01
A.01.00.08.00.00
B.02.00.00.03.00
A.01.00.00.03.01
A.00.00.10.00.00
B.02.00.01.00.00
A.01.00.01.03.00

would be hard on the eyes and brain.

Sorry to not offer a solution, but there is a good reason for convention in
this case, so it might be worth reconsidering why you are going against it.

-Jack Dahlgren

 

[Jim Aksel]

That was my first argument to my customer. I was informed their requirement
for this numbering is that it must be 3 sets wide (A.01.02.03).
To them A.01.00.00 means something. A.01 is "ambiguous" I am told. Welcome
to my world....

I think I am going to keep to the Text1 field. The WBS can stay as is
without the extra characters as you suggested.

Do you believe I am on the right course with the If, Leng and Oultine Levels
to concatenate the "answer" the customer wants to see?

--
If this post was helpful, please consider rating it.

Jim
It''s software; it''s not allowed to win.

Visit http://project.mvps.org/ for FAQs and more information
about Microsoft Project

Jim,

One of the conventions of WBS or other sorts of outline codes is that you
can tell by the length of the code where in the heirarchy it is.
For example if something has a WBS code of A I know it is top level at a
glance. I don't need to check all the digits. With your scheme I need to
read a lot to determine that

A.01.00.00.00.00 is a top level task while
A.01.00.00.00.01 is a bottom level task

However, if you follow convention and you see a list like this:

A
B.02
A.01.00.00.03.01

it is really clear where each of these things belong.

Making sense of a list of a dozen values like this:

A.00.00.00.00.00
B.02.00.00.00.00
A.01.00.00.03.01
A.00.00.02.01.05
B.02.00.00.00.10
A.01.01.00.03.01
A.00.00.04.00.00
B.02.00.10.00.08
A.01.00.00.03.01
A.01.00.08.00.00
B.02.00.00.03.00
A.01.00.00.03.01
A.00.00.10.00.00
B.02.00.01.00.00
A.01.00.01.03.00

would be hard on the eyes and brain.

Sorry to not offer a solution, but there is a good reason for convention in
this case, so it might be worth reconsidering why you are going against it.

-Jack Dahlgren

The WBS column displays such as
1.
1.1
1.1.1

Etc. Using a mask, I am able to force something such as
A.01.
A.01.01
A.01.01.01

However what I would like to do is also force the length of the WBS to
"right fill" with .00 so that it is always a fixed width ...

A.01.00.00.00
A.01.01.00.00
A.01.01.01.00
A.02.00.00.00

I attempted to modify a text1 field with a formula similar to:
trim(str([WBS]))+choose(len([WBS]),".00.00.00",".00.00",".00","")
I think if I play with that long enough I can get it to concatenate.

Additionally, The summary level tasks are not reporting a length on WBS if
I
use the formala text2=len([WBS)]. That is Text2 is blank on summary
lines.
So, my Text1 formula returns blank on summary tasks as well.

Should I reapproach the problem using [Outline Level]?

However, I would like two more things..
1. Stop the formula at Level 6 of the WBS... Just combine with an IF
statement I suppose? So anything at WBS level 7 or higher just carries
the
same number as level 6 (or perhaps it's just blank). Probably a "Choose"
function combine with Len([WBS])?
2. I would rather do this in the WBS field itself rather than the Text1
field. I will settle for use of WBS field only , even if I am forced to
accept a display all the way down to Outline Level 99.

Any ideas? Remember, we can't let the software win....

Jim

 

[Jack Dahlgren]

To them A.01.00.00 means something. A.01 is "ambiguous" I am told.
Welcome
to my world....

No thanks, I prefer my own reality.

Do you believe I am on the right course with the If, Leng and Oultine
Levels
to concatenate the "answer" the customer wants to see?

That is the direction I'd head.

-Jack Dahlgren