Should stoplight (calculated) fields be flagged as "Required"?

A

anovak

Since they are calculated, not sure if it would better or not to flag
them as "Required".

Thanks,
Andy Novak
UNT
 
B

Ben Howard

As they are calculated it won't make any difference whether the required
field is selected or not.
 
M

Mark Everett | PMP

Since they are calculated, not sure if it would better or not to flag
them as "Required".

Thanks,
Andy Novak
UNT
Click to expand...

Andy, no, they should not be flagged as Required. A new project with
very little data would contain Indicator fields that displayed <error>
since no data would exist for the calculations to take place. I
honestly don't know if that would throw an error and prevent a save or
not as I haven't experimented with that, but why risk it? The
stoplight will be available in any view you include the field in. The
value will depend upon how you set up the indicators.

Now, if you are using some manually set (subjective) indicator, you
can make that required.

HTH,
Mark Everett | PMP
www.catapultsystems.com
 
M

Marc Soester [MVP]

Hi Andy,

I guess I need to give my 2 cents worth too :)
The only reason why you want to mark a calculated field is if you would want
to display the field higher in the order within the Project Information
field. Please note, within Project Professional in the Project information
dialog window you will see that "required" fields are always displayed first,
then the optional fields. Should you need to show this calculated field
higher in the order of fields, you would achieve this by using the required
flag.

From a calculation point of view it will not make any difference if you flag
it as required or optional.
Hope this helps
 
Top