Skip to main content

Project Server 2013 and manually entered baselines not saving to database

**Quick publish article.  Further tests follow**
**Update:  Only appears to apply to on-premise installs.  Project Online is unaffected**

Issue:  When manually editing Baseline(0-10) timephased data via task usage in MS Project Client, data is not saved to database.

Tested on:  SEPT 2015 PU (Server and Client)

Prep:
-------------------------------------------------------
Create a project with one task on it.  
add a resource from pool and assign to the task at 100%
Set Baseline (0)
Publish plan

Test:  Query DB and see timephased data populated correctly



Issue 1 Repro
-------------------------------------------------------
Edit Baseline Work values in Task Usage view
Save and Publish

Test:  Query DB and see timephased data is not changed



Issue 2 Repro
-------------------------------------------------------
Add Baseline 10 to task usage view
Manually enter values into timephased cells for Baseline10
Save and Publish

Test:  Query DB and see timephased data is not changed




Issue 3 Repro
-------------------------------------------------------
Close MSP file
Remove from Cache
open file

Test:  See that previously edited values in Baseline 0 and Baseline 10 are missing.  Original Baseline data (set using Set Baseline) is displayed


Summary findings
-------------------------------------------------------
It looks like manually edited baseline values are not moving from Cache to Database on Save and therefore the reporting db isnt being updated.




SQL Script for test:
-------------------------------------------------------

--Baseline 0
SELECT         b.TimeByDay, b.AssignmentBaselineWork
FROM (SELECT * FROM MSP_EpmProject WHERE ProjectName = 't1bltest') P
INNER JOIN MSP_EpmAssignment A 
         on           p.projectuid = a.projectuid
INNER JOIN MSP_EpmAssignmentBaselineByDay B 
         on           a.AssignmentUID = b.AssignmentUID
WHERE          b.BaselineNumber = 0

--Baseline 10:
SELECT         b.TimeByDay, b.AssignmentBaselineWork
FROM (SELECT * FROM MSP_EpmProject WHERE ProjectName = 't1bltest') P
INNER JOIN MSP_EpmAssignment A 
         on           p.projectuid = a.projectuid
INNER JOIN MSP_EpmAssignmentBaselineByDay B 
         on           a.AssignmentUID = b.AssignmentUID
WHERE          b.BaselineNumber = 10

Comments

  1. I think this is an issue I've run into before. You need to change the scalar value, i.e. the total work or some field for the baseline in question. That's what triggers MPP to see that the baseline has changed and will then cause it to save the timephased values. See if that works.... (http://azlav.umtblog.com/2012/01/10/capturing-custom-timescaled-data-in-project-professional-part-i/)

    ReplyDelete

Post a Comment

Popular posts from this blog

Restoring PWA Site to another Web App in the same Farm

The scenario is this: SharePoint 2016 Farm with Project Server Two Web Apps Development UAT One PWA on Development Web App. I want to copy the PWA Site on Development web app to UAT to support a testing cycle. As far as I knew there were two options: 1) Content Database Restore and Attach Process would be backup your Dev Content Database, Restore to a new Content Database for QA, then mount the database on the appropriate web app and your off.... Problem:  Although you can do this with the -AssignNewDatabaseID switch in Powershell (to avoid two content db's having the same database id) the Site Collection (PWA) in the db still retains its SiteID which means there is a duplicate SiteID in the Configuration Database.  This stops the PWA site being created and alllocated correctly and becomes essentially orphaned. This method is only any good for MOVING not COPYING Back to the drawing board... 2) Backup-SPSite / Restore-SPSite I didn't believe this ...

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

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         ...