Sanity Check: Enterprise field or project file field

[ProjectAnalyst]

I'm going to track whether certain task costs can be capitalized using a
yes/no flag.

It seems adequate to simply create this using flag1 in a project template,
or in individual projects if necessary.

Can anyone think of reasons I might prefer to use an Enterprise level flag?

It seems I might need it later if I wanted to roll up all capitalized costs
in the portfolio analyzer. Any other ideas?
Thanks!

 

[Amanda.Murphy]

Hey - just a thought but if you are planning on doing some reporting on this
using the portfolio analyzer you may want to consider using an enterprise
outline code with characters and a lookup table of yes / no. It's slight
overkill but it would allow you to filter later in the Portfolio Analyzer.

Hope this helps!

 

[Reid McTaggart]

That won't work unless the Cube is extended. Out of the box, Task Outline
codes do not make it into the Cube.

There's a tricky workaround that involves calculating Capitalized costs at
the task level and then copying them to assignment fields to sneak them into
the Cube along with other resource-related info.

 

[Reid McTaggart]

The reason to use an Enterprise field is to ensure that no individual user
uses your field for their own purposes.

 

[ProjectAnalyst]

Thanks for your insights.

The reason to use an Enterprise field is to ensure that no individual user
uses your field for their own purposes.