none
Project Server 2010 custom fields not appearing to select in cube build RRS feed

  • Question

  • Hello, I downloaded the Microsoft Hyper V of Project Server integrated with TFS. My inquiry is strictly about Project Server. When I create a custom field, it is not available for me to select when addiing it to the cube build.

    Specifically, when I go to Server Settings >>> OLAP Database Management >>> Configure (for the selected cube), there's the option to select custom fields created for adding them to the build. Only one or two custom fields are avialable, but the 7 or 8 others are not. There's nothing special about the custom fields that I created. There's no formula, no menu selection just a plain Project/Text or Task/Text field.

    What could be going on? Not sure how big of a deal it is to re-install Analysis Services. Any ideas is greatly appreciated!!

    Tuesday, February 5, 2013 9:32 PM

Answers

  • dovendaven1 --
     
    I am glad my solution worked for you.  Since I do not work for Microsoft, I do not know why the OLAP cube is limited to custom fields attached to Lookup Tables.  I suspect that a Lookup Table is a way to keep a standard list of values on which reporting is possible.  That has been a fact of life for a long time and I have neither questioned it or resisted it!  :)  Hope this helps.
     

    Dale A. Howard [MVP]
    VP of Educational Services
    msProjectExperts
    http://www.msprojectexperts.com
    http://www.projectserverexperts.com
    "We write the books on Project Server"

    • Marked as answer by dovendaven1 Wednesday, February 6, 2013 3:55 PM
    Wednesday, February 6, 2013 12:14 AM
    Moderator

All replies

  • dovendaven1 --
     
    By chance are the custom fields you DO see custom fields with a Lookup Table?  If so, this should tell you that you can only add custom fields with a Lookup Table to your OLAP cubes.  Hope this helps.
     

    Dale A. Howard [MVP]
    VP of Educational Services
    msProjectExperts
    http://www.msprojectexperts.com
    http://www.projectserverexperts.com
    "We write the books on Project Server"

    Tuesday, February 5, 2013 10:15 PM
    Moderator
  • Dale, thx for your response. For some reason, your reply is not showing, though the thread list indicates a response. I'm going to resubmit and see what happens.
    • Edited by dovendaven1 Wednesday, February 6, 2013 12:06 AM
    Tuesday, February 5, 2013 11:09 PM
  • Disregard my previous message as your response displayed after I responded. So here's my REAL response:

    WOW!!! It worked when I created a field that had a lookup BUT....why would the OLAP build only be limited to only fields that have a lookup table? For example lets say a comments field or project code or a cost code that is not determined with field is not created.

    Tuesday, February 5, 2013 11:22 PM
  • dovendaven1 --
     
    I am glad my solution worked for you.  Since I do not work for Microsoft, I do not know why the OLAP cube is limited to custom fields attached to Lookup Tables.  I suspect that a Lookup Table is a way to keep a standard list of values on which reporting is possible.  That has been a fact of life for a long time and I have neither questioned it or resisted it!  :)  Hope this helps.
     

    Dale A. Howard [MVP]
    VP of Educational Services
    msProjectExperts
    http://www.msprojectexperts.com
    http://www.projectserverexperts.com
    "We write the books on Project Server"

    • Marked as answer by dovendaven1 Wednesday, February 6, 2013 3:55 PM
    Wednesday, February 6, 2013 12:14 AM
    Moderator
  • Totally understand Dale! I also understand the intent to validate data and reduce it for reporting performance. 

    Just to ramble about it and no response needed. Let's say I needed to enter cost codes, which could be hundreds in a larger org, then enter it in in a lookup table (if it even support the amount) and then select it in the schedule would be tedious.

    Wednesday, February 6, 2013 3:55 PM
  • dovendaven1 --
     
    I am remiss for failing to mention that you can also add custom Cost, Number, and Duration fields to the OLAP cubes using the Cube Measures section of the Database Configuration page.  Keep in mind, however, that the these Cost, Number, and Duration fields MUST NOT contain a formula or a Lookup Table.  Given the example you just shared, you would want to add the custom Cost field to the Cube Measures section of the page, thus adding it to the OLAP cube.  Hope this helps.
     

    Dale A. Howard [MVP]
    VP of Educational Services
    msProjectExperts
    http://www.msprojectexperts.com
    http://www.projectserverexperts.com
    "We write the books on Project Server"

    Wednesday, February 6, 2013 5:18 PM
    Moderator