From: Andrew Lavinsky on 2 Oct 2009 05:11 1) To filter on the Outline Level, it would look something like this: IIF([Outline Level]<3,IIf([UserReview]=Null,Null,dateadd("m",3,[UserReview])),Null) I don't think that's correct w/ the "nulls" but don't have Project client open in front of me to give you the exact formula. I can check when I pull up my work laptop in a couple of hours. Conceptually, that's how you would modify the formula. 2) You'll need to pop that formula into a Text field. It won't display True/False in a Date field. I'd actually use a Flag field myself, which just displays Yes/No. If using as a Flag field, this formula should work: IIf([Date3]<Date(),Yes,IIf([Date3]=ProjDateValue("NA"),Yes,No)) "Maver1ck666" wrote: > Sorry, forgot to mention the User Review and Next Review columns are both > date fields. > > "Andrew Lavinsky" wrote: > > > If I follow (and I am not entirely sure I do), have you tried: > > > > > 1) Is there a way I could have the 3 columns on the right only apply > > > to the outline level 2 entries? At the moment, the data appear for all > > > rows which is confusing as those columns only apply to the actual > > > system entry. > > > > > > > Filtering on the Outline Level field using an IIF statement? > > > > > > > 2) The [Next Review] column shows #ERROR if the [User Review] date has > > > not been changed from the default NA. Is there any way around this? > > > > IIf([Date3]<Date(),"True",IIf([Date3]=ProjDateValue("NA"),"True","False")) > > - assuming it's a text field. > > > > > > > > > I have a project which i am using as a schedule to monitor all the > > > systems I develop. > > > > > > The schedule looks like this: > > > > > > Project #1 (outline level 2) User Review > > > Next > > > Review Overdue > > > Change request #1 (outline level 3) 01/10/2009 > > > 01/01/2010 > > > False > > > Change request #2 > > > Documentation (outline level 4) > > > Planning > > > Development > > > Project #2 01/10/2009 > > > 01/01/2010 False > > > Project #3 01/06/2009 > > > 01/09/2009 True > > > [User Review] is set as a date field. > > > > > > [Next Review] has the formulae: > > > > > > IIf([UserReview]=Null,Null,dateadd("m",3,[UserReview])) > > > > > > [Overdue] has the formulae: > > > > > > IIf([Date3]<Date(),"True",IIf([Date3]="NA","False","False")) > > > > > > Right then, I have a number of problems with this layout/format im > > > hoping you can help with please. > > > > > > 1) Is there a way I could have the 3 columns on the right only apply > > > to the outline level 2 entries? At the moment, the data appear for all > > > rows which is confusing as those columns only apply to the actual > > > system entry. > > > > > > 2) The [Next Review] column shows #ERROR if the [User Review] date has > > > not been changed from the default NA. Is there any way around this? > > > > > > Thanks in advance for your help! > > > > > > Kind regards, > > > Mav > > > > > >
From: Andrew Lavinsky on 2 Oct 2009 05:16 Instead of filtering on Outline Level, you could swap that logic in the formula out with: [Summary]=Yes That will simply show you all of the Summary tasks instead of tasks at Level 1 or 2. That may work better. -A "Maver1ck666" wrote: > Sorry, forgot to mention the User Review and Next Review columns are both > date fields. > > "Andrew Lavinsky" wrote: > > > If I follow (and I am not entirely sure I do), have you tried: > > > > > 1) Is there a way I could have the 3 columns on the right only apply > > > to the outline level 2 entries? At the moment, the data appear for all > > > rows which is confusing as those columns only apply to the actual > > > system entry. > > > > > > > Filtering on the Outline Level field using an IIF statement? > > > > > > > 2) The [Next Review] column shows #ERROR if the [User Review] date has > > > not been changed from the default NA. Is there any way around this? > > > > IIf([Date3]<Date(),"True",IIf([Date3]=ProjDateValue("NA"),"True","False")) > > - assuming it's a text field. > > > > > > > > > I have a project which i am using as a schedule to monitor all the > > > systems I develop. > > > > > > The schedule looks like this: > > > > > > Project #1 (outline level 2) User Review > > > Next > > > Review Overdue > > > Change request #1 (outline level 3) 01/10/2009 > > > 01/01/2010 > > > False > > > Change request #2 > > > Documentation (outline level 4) > > > Planning > > > Development > > > Project #2 01/10/2009 > > > 01/01/2010 False > > > Project #3 01/06/2009 > > > 01/09/2009 True > > > [User Review] is set as a date field. > > > > > > [Next Review] has the formulae: > > > > > > IIf([UserReview]=Null,Null,dateadd("m",3,[UserReview])) > > > > > > [Overdue] has the formulae: > > > > > > IIf([Date3]<Date(),"True",IIf([Date3]="NA","False","False")) > > > > > > Right then, I have a number of problems with this layout/format im > > > hoping you can help with please. > > > > > > 1) Is there a way I could have the 3 columns on the right only apply > > > to the outline level 2 entries? At the moment, the data appear for all > > > rows which is confusing as those columns only apply to the actual > > > system entry. > > > > > > 2) The [Next Review] column shows #ERROR if the [User Review] date has > > > not been changed from the default NA. Is there any way around this? > > > > > > Thanks in advance for your help! > > > > > > Kind regards, > > > Mav > > > > > >
From: Andrew Lavinsky on 2 Oct 2009 09:31 Opened the client....and here's the first formula. This seems to work - although I didn't do extensive testing: IIf([Summary]=Yes,IIf([Date2]<>ProjDateValue("NA"),ProjDateAdd([Date2],ProjDurValue("3mon")),ProjDateValue("NA")),ProjDateValue("NA")) Note that this will only display for Summary tasks. -A > Instead of filtering on Outline Level, you could swap that logic in > the formula out with: > > [Summary]=Yes > > That will simply show you all of the Summary tasks instead of tasks at > Level 1 or 2. That may work better. > > -A > > "Maver1ck666" wrote: > >> Sorry, forgot to mention the User Review and Next Review columns are >> both date fields. >> >> "Andrew Lavinsky" wrote: >> >>> If I follow (and I am not entirely sure I do), have you tried: >>> >>>> 1) Is there a way I could have the 3 columns on the right only >>>> apply to the outline level 2 entries? At the moment, the data >>>> appear for all rows which is confusing as those columns only apply >>>> to the actual system entry. >>>> >>> Filtering on the Outline Level field using an IIF statement? >>> >>>> 2) The [Next Review] column shows #ERROR if the [User Review] date >>>> has not been changed from the default NA. Is there any way around >>>> this? >>>> >>> IIf([Date3]<Date(),"True",IIf([Date3]=ProjDateValue("NA"),"True","Fa >>> lse")) - assuming it's a text field. >>> >>>> I have a project which i am using as a schedule to monitor all the >>>> systems I develop. >>>> >>>> The schedule looks like this: >>>> >>>> Project #1 (outline level 2) User Review >>>> Next >>>> Review Overdue >>>> Change request #1 (outline level 3) 01/10/2009 >>>> 01/01/2010 >>>> False >>>> Change request #2 >>>> Documentation (outline level 4) >>>> Planning >>>> Development >>>> Project #2 >>>> 01/10/2009 >>>> 01/01/2010 False >>>> Project #3 >>>> 01/06/2009 >>>> 01/09/2009 True >>>> [User Review] is set as a date field. >>>> [Next Review] has the formulae: >>>> >>>> IIf([UserReview]=Null,Null,dateadd("m",3,[UserReview])) >>>> >>>> [Overdue] has the formulae: >>>> >>>> IIf([Date3]<Date(),"True",IIf([Date3]="NA","False","False")) >>>> >>>> Right then, I have a number of problems with this layout/format im >>>> hoping you can help with please. >>>> >>>> 1) Is there a way I could have the 3 columns on the right only >>>> apply to the outline level 2 entries? At the moment, the data >>>> appear for all rows which is confusing as those columns only apply >>>> to the actual system entry. >>>> >>>> 2) The [Next Review] column shows #ERROR if the [User Review] date >>>> has not been changed from the default NA. Is there any way around >>>> this? >>>> >>>> Thanks in advance for your help! >>>> >>>> Kind regards, >>>> Mav
First
|
Prev
|
Pages: 1 2 Prev: Expanding .IMG file: 60 Day trial Next: Sorting and renumbering resources |