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

Issues update on #projectserver2013 - Timesheets and Publishing

Reporting Publish ** updated with links to other related discussions, and a VBA macro ** the following issue has been noted on publish since June 13 CU was applied: ReportingProjectChangeMessageFailed (24006) - Object reference not set to an instance of an object.. Details: id='24006' name='ReportingProjectChangeMessageFailed' uid='4d869e56-f625-e311-bb41-005056b90052' QueueMessageBody='Project UID='e3f49977-b2bc-e211-8559-005056b90052'. PublishType='ProjectPublish'' Error='Object reference not set to an instance of an object.'. I have seen this noted previously on a similar issue: http://nearbaseline.com/blog/2013/06/ms-reporting-project-publish-jobs-failed-after-aprilcu/comment-page-1/#comment-14741 This is  caused by Baselined Milestones having NULL Baseline Cost values Original bug note with potential workaround is here: http://blogs.msdn.com/b/brismith/archive/2012/05/23/project-server-2007-reporting-project-pu...

#projectserver2013 VIEW FAILURE: The view failed to load. Press OK to reload this view with the default settings. Press cancel to select another view.

** UPDATE ** includes notes relating to secondary bug where Timesheet is created without Administrative tasks. Does this ring any bells? This has been bugging me for months, but finally I have a repro for this: Issue Summary:  When a task is deleted from a plan that is approved into a previous or current timesheet - even when there are no actuals on the task - you can no longer view the timesheet The following repro has been proven: - Setup system with Single Entry Mode, with enforced Status Approval before Timesheet Approval - Create resource as own timesheet manager - Create new project - Create two tasks in the same week, starting monday with 5 days duration:  1) Task to assign actuals, 2) Task to delete post submission - Assign Resource to tasks - publish project - as Timesheet User, go to the appropriate timesheet period for the tasks created - Assign actual work to one task (task 1), leaving task 2 with no actual work - Submit timesheet - as Project ...

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