Skip to main content

first bug of #Project2013 #sp1

Interesting - Setting Baseline0  adds values to ALL baselines.  Then editing Baseline0 costs changes all baseline costs

Repro:

  • Create task of 1d
  • Add a cost resource
  • Set Task Usage at bottom window
  • Add Baseline 0 Cost, Baseline 10 cost, baseline 4 cost (or some others too)
  • Add some Timephased costs into Cost timephased field
  • Set baseline
  • All baselines are set with a value
  • Edit Baseline0 Cost TImephased entry
  • All Baseline Values change
  • Scream and bang head on table
** UPDATE **

 Having looked further into this it appears that this only impacts baseline cost timephased values.  However this is a MASSIVE impact as it could increase file sizes fairly significantly as the Baseline Cost Timephased Values for Baselines >=1 are no longer independent values.  Put simply, BAseline 1-10 Cost Timephased will equal Baseline0Cost, and cannot be set independently.

Here is an updated repro
Prep:
- Firstly create split view with task usage on the bottom and gantt at the top
- add Cost, baseline Cost, Baseline1 cost, other baseline cost fields to the Task Usage Timephased section
Repro:
1) Create a task (any duration)
2) assign a resource to the task that has a standard rate so we see costs timephased in task usage pane
3) Now set Baseline0
BUG:  See that Baseline 1-10 Cost values in timephased data now all have a value, not just the baseline0cost value
4) Now edit an element of the timephased baseline0 cost data
BUG:  All Baseline Cost Values change in that time segment to the value you edited
5) Now try edit a timephased segement for basline 1 cost
BUG:  Notice the edit wont set
6) now try settings Baseline 1 (or another >0)
BUG:  Timephased BaselineX Cost Values NOT Created


here's what a plan can look like when baseline0 is set.  In the bottom pane I have added Basline0 Cost, Baseline1 Cost and Baseline10 Cost but the same issue applies for all of them.




Note;  baseline work values do not show this issue

Labels:

Comments

Post a Comment

Popular posts from this blog

SP2 released

Office Project Server 2007 Sp2 has now been released.  see the details here - http://blogs.msdn.com/chrisfie/archive/2009/04/28/announcing-service-pack-2-sp2-for-microsoft-project-2007-and-microsoft-project-server-2007.aspx .  see teh webcast here http://blogs.msdn.com/brismith/archive/2009/04/28/project-server-2007-service-pack-2-sp2-is-now-available.aspx Blogged with the Flock Browser
Post a Comment
Read more

TPG Apps Highlights - Risk Matrix #projectonline #projectserver #risk

This post is the first of a series to highlight the apps available for Project Server and Project Online from the SharePoint store  ( https://store.office.com/search.aspx?productgroup=SharePoint&qu=tpg ) and direct via your local TPG office. The first of this series will look at the s imple plug-and-play apps that all users of Project Online can make use of quickly and easily.   T hese are: Risk Matrix  Milestone Trend Analysis (MTA) WBS Chart viewer Next we will focus on the challenge of  Resource Request Supply and Demand by demonstrating our more recent TeamLink and TeamManager apps. Team Manager App is a Resource Manager/Owner app for allocating resource supply to Projects and BAU activities and monitoring demands against commitments Team Link App is a PM tool for monitoring Project demands vs the supply provided by the Resource Managers  Finally I will highlight some of the benefits of our integration tools when used i...
Post a Comment
Read more

Reporting from Project Server 2016 - multiple sites and userviews

Just a quickie... I've been interested in how MS have handled the "multiple PWA sites in a Content DB" thing since I read that this was their new approach.  Most of my reporting is via SSRS so i am reliant (still... in 2016) on DB queries rather than OData feeds (tsk) and this "querying a PWA DB with more than one PWA site in it is unsupported" quote was worrying me. So it looks like what is happening is this. When you create the first PWA site in a Content DB it hard-codes the SiteID into the _Userview view design elements.  This means that your first PWA Site is the default.  All the data for subsequent sites are still held in the tables against separate SiteID's but you cannot utilise the OOTB _Userview components (see below) SELECT        ProjectFields.... FROM            pjrep.MSP_TVF_EpmProject('FF19B767-CA6D-4C4C-B123-C0B5AE5354D6') AS MSP_EpmProject  LEFT OUTER JOIN         ...
Post a Comment
Read more