ลงชื่อเข้าใช้
Microsoft.com
 
Microsoft
 
 
 
Microsoft >
> 
> 
Grouping by Custom Outline Codes Options

คำตอบ Grouping by Custom Outline Codes Options

  • 11 พฤษภาคม 2553 13:02
     
     
    ลงชื่อเข้าใช้เพื่อโหวต
    0

    Hello,

    I am quite a newbie with Project and this forum. I run Project 2007 (12.0.4518.10.14) MSO (12.0.6529.5000).

    I'am trying to group tasks by Custom Outline Codes using their level as a first criteria. I configured options in the Define Group Interval Dialog Box to do so.

    The matter is Project doesn't find any value for outline code using outline code level as criteria. If I use outline code value, I get somes results but I want to use outline code indenture to group !

    To be clear (I hope so):

    I want a recapitulative task 1 regrouping 1.1 and 1.2, a recapitulative task 2 and a recapitulative task 3 if my admissibles values are 1.1, 1.2, 2 and 3 for the outline code.

    Thanks

     

ตอบทั้งหมด

  • 11 พฤษภาคม 2553 13:14
    ผู้ดูแล
     
     คำตอบ
    ลงชื่อเข้าใช้เพื่อโหวต
    0
    You have a couple of options.
     
    Option #1: Perhaps the issue is that you're not using the Outline Level field
    in your grouping? I created a custom outline field, added tasks, then grouped
    by value (not by level) and got pretty close to what it sounds like you are
    doing. If that is not working for you, consider first grouping by outline
    code, then perhaps grouping by the Outline Level field?
     
    Option #2: Use formulas to extract various elements of your outline code
    for ease of grouping. See similar guidance and formulas here: http://blogs.catapultsystems.com/epm/archive/2010/03/03/using-intelligent-wbs-codes-in-microsoft-project.aspx
     
     
    - Andrew Lavinsky
    Blog: http://blogs.catapultsystems.com/epm
     
     
     
    • ทำเครื่องหมายเป็นคำตอบโดย Michael Wharton, MVPMVP 5 สิงหาคม 2553 18:14
    •  
     
  • 11 พฤษภาคม 2553 15:59
     
     
    ลงชื่อเข้าใช้เพื่อโหวต
    0

    Thank Andrew for your options.

    About Option #1, I think I forgot to tell you some details about my project : in fact, the matter is I have already some tasks already defined but without a common hierarchy...My job is to get a new view of these tasks with a common hierarchy.

    If I take examples from the link you gave me, let's say that you have 2 locations in Middeltown (with same tasks) and that you denote them under Middeltown. As a result, you can't anymore use the outline level field (nor WBS field) because task with the same "meaning" have different outline level value.

    PROJ1:MID.GRADE (level 2) for location 1 becomes PROJ1:MID-1.GRADE (level 3) which is not consistent with PROJ1:HAR.GRADE (level 2)...

    In your test, I agree with "pretty close" but I need the task regrouping the lower level ones. And if I first group by outline code,then, I can't (or don't know how) have this recapitulative task.

    That's why I am very interested in using outline code level cause I think it covers this point of view.

    I thinked about Option #2 before asking my question but I didn't find the formula editor friendly...

    If you have some other options, it will be a pleasure !

     
  • 11 พฤษภาคม 2553 22:18
    ผู้ดูแล
     
     
    ลงชื่อเข้าใช้เพื่อโหวต
    0

    Hi Topaxe1,

    Pardon me for bumping in.  I would first ensure you have service pack 2 installed from your comment:

    "I run Project 2007 (12.0.4518.10.14) MSO (12.0.6529.5000)"

    You do not have SP-2 installed.

    I'd start there and then see if you have better luck.

    I hope this helps.

    Julie

     
  • 13 พฤษภาคม 2553 15:49
    ผู้ดูแล
     
     
    ลงชื่อเข้าใช้เพื่อโหวต
    0
    I am still not sure I follow entirely.  Are you sure that outline codes are the way to go?  Perhaps you might want to try using multiple Text fields to code each task as needed, then use grouping to create the hierarchy?
     
  • 14 พฤษภาคม 2553 6:35
     
     
    ลงชื่อเข้าใช้เพื่อโหวต
    0

    Here is my thinking :

    If you create an outline code from your exemple with this hierarchy : Location.Activity

    As for WBS field, you have one field providing more than one "attribute" for a task. You can make formula to extract them.

    What I understood from here (http://office.microsoft.com/en-us/project/HP453319271033.aspx §4) is that you can, without any formulas, group by Location (Level 1 of the outline code) or Activity (Level 2 of the outline code) or Activity and then Location.

    If this works as described, that's what I need ! Otherwise, I need an explanation...

    Thanks

     
  • 14 พฤษภาคม 2553 6:42
     
     
    ลงชื่อเข้าใช้เพื่อโหวต
    0

    Hi Julie,

    Thanks for bumping in !

    As I have some KB update installed, I wondered if they cover SP-2.

    As I understand, I should ask support to install SP-2.

    Thanks

    PS : I realised that I'm in a Project 2010 forum. Sorry for that.

     
  • 14 พฤษภาคม 2553 11:20
    ผู้ดูแล
     
     
    ลงชื่อเข้าใช้เพื่อโหวต
    0
    That how to article works fine in my 2007 SP2 environment. So you've tried
    to follow exactly those instructions, and the grouping does not work - or
    are you trying to do something slightly different?
     
    I must admit that I'm still unsure as to why you wish to accomplish this
    through Outline Codes and not through straight task coding.
     
     
    - Andrew Lavinsky
    Blog: http://blogs.catapultsystems.com/epm
     
     
     
     
  • 14 พฤษภาคม 2553 12:21
    ผู้ดูแล
     
     คำตอบที่เสนอ
    ลงชื่อเข้าใช้เพื่อโหวต
    0

    Hi Topaxe1,

    From you posting of the identification, it doesn't appear that you have any service pack applied.  For example, Help > About Microsoft Office Project in my installation shows:

    Microsoft Office Project 2007 (12.0.6423.1000) SP2 MSO (12.0.6425.1000)

    Double check to see if you have "SP2" showing.

    Also, don't worry about the project 2010 forum.  Very shortly, this will be the Project forum -- encompassing all releases.

     

    Best,

    Julie

     
  • 14 พฤษภาคม 2553 12:58
    ผู้ดูแล
     
     
    ลงชื่อเข้าใช้เพื่อโหวต
    0
    Ah - just tried it in a 2007 SP1 environment and was able to replicate what
    I believe is your issue - where the outline levels do not aggregate on grouping.
    Follow Julie's suggestions, patch to SP2, and it looks like the error is
    resolved.
     
    - Andrew Lavinsky
    Blog: http://blogs.catapultsystems.com/epm
     
     
     
    • ทำเครื่องหมายเป็นคำตอบโดย Topaxe1 14 พฤษภาคม 2553 14:14
    • ยกเลิกการทำเครื่องหมายเป็นคำตอบโดย Topaxe1 18 พฤษภาคม 2553 9:59
    •  
     
  • 14 พฤษภาคม 2553 14:32
     
     
    ลงชื่อเข้าใช้เพื่อโหวต
    0

    Thanks both of you for helping me.
    I am now waiting after support installing SP-2 ...

    Andrew, I did formulas to extract other fields from the outline code in order to be sure that it was what I need. But I found it tedious and it uses as many fields as you need levels in your outline code.

    Considering I use few outline codes to provide all the needed views ant that I am "lazy", I prefer using out of the box functions from Project.

    best regards

     
  • 14 พฤษภาคม 2553 15:26
    ผู้ดูแล
     
     
    ลงชื่อเข้าใช้เพื่อโหวต
    0

    Great Topaxe.  I'm glad Andrew was able to confirm that SP-2 fixes the issue.  General rule of thumb -- make sure your systems are at the most recent service pack :-)

    Julie

     
  • 18 พฤษภาคม 2553 10:20
     
     
    ลงชื่อเข้าใช้เพื่อโหวต
    0

    Hi again,

    I've just got SP2 installed on my computer.

    There is improvement but it still doesn't solve my matter. Perhaps, I am really misunderstanding the outline code and Andrew is right when telling me to do it with Text fields.

    Here my explanation:

    If you take one recapitulative task (1) with 2 subtasks (1.1 and 1.2) and 2 others tasks (2 and 3).  If you define an outline Code with theses values (A.1;A.2;B).

    Then, assign task 1.1 with A.1, 1.2 with B, 2 with A.2 and 3 with B.

    What I expect by regrouping by first level of outline code  is to have a "A group" with tasks 1.1 and 2 and a "B group" with tasks 1.2 and 3.

    Result in Project 2007 with SP2 is : one "A group" with task 1.1, one "B group" with tasks 1.2, another "A group" with task 2 and another "B group" with tasks 3.

    Is this the expected behaviour ? Cause, it means there is a link between task's level and outline code level...

    I am bit lost.

    Thanks for helping !

     
  • 18 พฤษภาคม 2553 11:33
    ผู้ดูแล
     
     
    ลงชื่อเข้าใช้เพื่อโหวต
    0

    Hi Topaxe,

    The only way I could accomplish what you are seeking is to add a text field and use the Left function in the field to pull the "a" and "b" from the outline code and then group by the text field.

    I hope this helps.

    Julie

     
  • 18 พฤษภาคม 2553 11:47
     
     
    ลงชื่อเข้าใช้เพื่อโหวต
    0

    Hi Julie,

    It is my point of view too.

    What I find very strange is that Project make different groups at first level with the same value !

    Is it a bug or is it normal ?

    I will use some Text fields and formulas as a workaround...

    Andrew, as you told me to do that way from start, that's what you were thinking about ?

    Thanks

     
  • 18 พฤษภาคม 2553 12:39
    ผู้ดูแล
     
     
    ลงชื่อเข้าใช้เพื่อโหวต
    0
    I can't recall what I had for breakfast, much less what I recommended last
    week. I'll be happy to take partial credit though.
     
    Let us know if it works.
     
    - Andrew Lavinsky
    Blog: http://blogs.catapultsystems.com/epm
     
     
     
     
  • 18 พฤษภาคม 2553 13:57
     
     
    ลงชื่อเข้าใช้เพื่อโหวต
    0

    Yes, it works because I did it waiting after SP2 as a workaround...

    I am now afraid I will have to use Text fields and formulas.

    I just wonder if this behaviour is normal to improve my knowledge about Project.

    Because I don't find interest in outline code anymore whereas I thought it's powerful.

    For instance, if you want to use it as a cost center, it is mandatory to have the same hierarchy between tasks and cost centers... Strange ?

    Thanks

     
  • 18 พฤษภาคม 2553 14:08
    ผู้ดูแล
     
     
    ลงชื่อเข้าใช้เพื่อโหวต
    0
    Typically, the way I've seen cost centers is that they map to the WBS at
    a specific level - called the control account. So say, I have a CBS code,
    at the lowest level of the CBS code, I map it to all of my WBS level 3 tasks
    or something like that.
     
    Then I would export my CBS Codes to Excel or Visio and roll them up there
    - although I could accomplish much the same thing with grouping in MS Project
    - as you're finding out.
     
    Other options would be to use something like cost resources, or to map cost
    centers to specific resources - and then manage cost breakdown in the Resource
    Sheet.
     
     
    - Andrew Lavinsky
    Blog: http://blogs.catapultsystems.com/epm
     
     
     
     
  • 19 พฤษภาคม 2553 23:30
    ผู้ดูแล
     
     
    ลงชื่อเข้าใช้เพื่อโหวต
    0

    Hi Topaxe,

    I'm not sure why you selected outline codes to start.  You can create the same value list drop-downs in other fields.  The Level option in Outlne codes does seem counter intuitive to the grouping functions as it counts each entry as a level.

    Julie