Project Pro Spreads Baseline but data not in the reporting database RRS feed

  • Question

  • We have Project Server 2010 SR1 June 2012 CU. The Project Client is the December 2011 CU.

    Consider the following:

    • A user has a task that spans 5/2/2013 to 5/2/2014.
    • In the Project Client, Task Usage View, set for Year, the user EDITS the Baseline Cost to be $50,000 for 2013 and $50,000 for 2014.
    • The user Publishes the project.
    • The MSP_EpmTaskBaselineByDay view only shows baseline costs between 5/2/2013 and 5/2/2014, totaling $31,034 for 2013 and $16,858 for 2014
    • When expanding the timescale in Project Pro to Days, the Baseline Costs (entered by the user as $50,000 for the year) are spread between 1/1/2013 and 12/31/2013 at $191.57 per working day (and similarly $50,000 spread between 1/1/2014 and 12/31/2014).
    • thus, the baseline costs outside the task date range are not present in the reporting data

    Our users want to be able to override the Baseline Cost at a task level, so we need the data represented in the Project Client to be reflected in the reporting data.

    Thank you.


    Wednesday, December 5, 2012 3:23 PM

All replies

  • Jim, I suggest you use a cost resource assigned to your year long task. Enter cost information in the task usage view time phased section and then use the regular baseline procedure. Entering baseline information directly will throw anomalies such as the one you observe.


    Wednesday, December 5, 2012 4:57 PM
  • Jim,

    I would also suggest patching the Pro client to the same level as the server or you may get "unexpected results".

    Treb Gatte | Twitter |

    Thursday, December 6, 2012 6:29 AM
  • The last time I played with this, I found some wackiness with forcing the
    baseline data to save.  Depending on the situation you may need to populate
    scalar data (the stuff on the left) or baseline work for the system to recognize
    that the baseline has been edited.
    This might help...

    Andrew Lavinsky [MVP] Blog: Twitter: @alavinsky
    Friday, December 7, 2012 3:51 AM