# What the best way to check task baseline status on PWA with formula?

• ### Question

• Dear experts,

We need to rebuild formula for our enterprise project custom field that would be check baseline status for tasks based on 'baseline finish" field on PWA. So i found following constructions of formula:

1) IIf(ProjDateValue([Baseline Finish]) = 4294967295;"No Baseline";"On Schedule") this example we use now, but he does not work correctly for some our enterprise projects.

2) IIf([Baseline Finish] > 50000; "4_ No Baseline";"On Schedule") this example from this article "Working with Custom Field Formulas"

3) IIf([Baseline Finish] = ProjDateValue("NA");"No Baseline";"On Schedule") i found this example from Dale A. Howard by this link

But in another topic from this forum i also found information from Gary Chefetz that don`t recommend to use ProjDateValue () function for PWA calculations.

First example of formula construction do not work correctly for project task on PWA. So we are looking for correct construction of this formula for our custom field that would be working fine for all projects on Project Web Application (Project Server 2010).

What you recommend for us in this case?

Alexey
Wednesday, March 9, 2011 5:34 PM

• #3 has always worked for me in the past.

Wednesday, March 9, 2011 6:06 PM

IIf([Baseline Finish]=4294967295,'NA',Switch(ProjDurValue([Finish Variance])>=ProjDurValue(ProjDurConv("11 d",pjMinutes)),'Red',ProjDurValue([Finish Variance])>=ProjDurValue(ProjDurConv("6 d",pjMinutes)),'Yellow',True,'Green'))

Options:

Use formula, Roll down, graphic indicators

For troubleshooting, I would first turn off the graphic indicators so you can view the actual results of the formula.  This may pinpoint where you have a problem.  Inspect it both in Project Pro and then after you publish to PWA.

Terrie T - MCTS - PMP - MBA****PMO & Project Server Admin
• Marked as answer by Thursday, March 10, 2011 4:13 PM
Thursday, March 10, 2011 2:20 PM
• Thank you to all,

We found a reason of issue that caused us wrong behavior. And in our case, unfortunately or fortunately, this issue was not associated with the construct of the formula (at least I was not able to prove otherwise). So i tested following designs of formula:

1.  IIf(ProjDateValue([Baseline Finish]) = 4294967295;"No Baseline";"On Schedule")

2. IIf([Baseline Finish] = ProjDateValue("NA");"No Baseline";"On Schedule")

3. IIf([Baseline Finish]=4294967295;"No Baseline";"On Schedule")

on new enterprise custom fields

1. IIf([Baseline Finish] = ProjDateValue("NA");"No Baseline";"On Schedule")

for existing new enterprise custom field and all works fine.

We resolved this issue for some our projects when recalculate and then republish projects from MS Project 2007. Before this we worked and  tested custom fields from this some projects only from MS Project 2010.  I do not know exactly why issue occured but i know that he occured only if both version of clients used for working with enterprise projects.

Alexey
• Marked as answer by Thursday, March 10, 2011 4:13 PM
Thursday, March 10, 2011 4:12 PM

### All replies

• #3 has always worked for me in the past.

Wednesday, March 9, 2011 6:06 PM
• I use a variation of #1, without the call to ProjDateValue(), just a direct comparison of the field to the value.  Haven't had any issues; what are you seeing when you say that it's not working?
Terrie T - MCTS - PMP - MBA****PMO & Project Server Admin
Wednesday, March 9, 2011 7:17 PM
• Andrew, Terrie,

Terrie,

We use #1 variant and can see that some of our enterprise projects, when we open them, have some tasks (but not all) without values on enterprise custom field based on formula (we use indicators associated with this field). We republish this projects but no luck.

Can you please, write your example, how you compare [Baseline Finish] or maybe another field, when you want to check - does any "baseline" status for project task or not?

Alexey
Thursday, March 10, 2011 8:10 AM
• I use a different formula for #1 IIF(Len([Baseline Finish]) < 5 , "NoBaseline", "Baselined") , it has always worked for me
Thanks | Sunil Kr Singh | http://epmxperts.wordpress.com
Thursday, March 10, 2011 8:54 AM

IIf([Baseline Finish]=4294967295,'NA',Switch(ProjDurValue([Finish Variance])>=ProjDurValue(ProjDurConv("11 d",pjMinutes)),'Red',ProjDurValue([Finish Variance])>=ProjDurValue(ProjDurConv("6 d",pjMinutes)),'Yellow',True,'Green'))

Options:

Use formula, Roll down, graphic indicators

For troubleshooting, I would first turn off the graphic indicators so you can view the actual results of the formula.  This may pinpoint where you have a problem.  Inspect it both in Project Pro and then after you publish to PWA.

Terrie T - MCTS - PMP - MBA****PMO & Project Server Admin
• Marked as answer by Thursday, March 10, 2011 4:13 PM
Thursday, March 10, 2011 2:20 PM
• Thank you to all,

We found a reason of issue that caused us wrong behavior. And in our case, unfortunately or fortunately, this issue was not associated with the construct of the formula (at least I was not able to prove otherwise). So i tested following designs of formula:

1.  IIf(ProjDateValue([Baseline Finish]) = 4294967295;"No Baseline";"On Schedule")

2. IIf([Baseline Finish] = ProjDateValue("NA");"No Baseline";"On Schedule")

3. IIf([Baseline Finish]=4294967295;"No Baseline";"On Schedule")

on new enterprise custom fields

1. IIf([Baseline Finish] = ProjDateValue("NA");"No Baseline";"On Schedule")

for existing new enterprise custom field and all works fine.

We resolved this issue for some our projects when recalculate and then republish projects from MS Project 2007. Before this we worked and  tested custom fields from this some projects only from MS Project 2010.  I do not know exactly why issue occured but i know that he occured only if both version of clients used for working with enterprise projects.

Alexey
• Marked as answer by Thursday, March 10, 2011 4:13 PM
Thursday, March 10, 2011 4:12 PM
• Hi

this is the only one that works for me in Project Online !

The variants with the magic number only work without issues in Project Professional.

The comparison with "NA" has a language issue. Might work in single language environments.

Christoph

Christoph Muelder | Senior Consultant, MCTS, MCSE | SOLVIN information management GmbH, Germany

Friday, November 23, 2018 8:32 AM