none
Problems Baseline Protected RRS feed

  • Question

  • Hello,

    I am going through a difficulty with the permission of baseline protected category I turned off this option so that project managers could not save or clear the baseline 0-5 as example and it worked correctly.

    However if I insert the column baseline in the view, I can manually change the dates and still save and publish using the menu File - Save / Publish is there any way to block this action within the program or through permissions.


    Hezequias Vasconcelos

    Tuesday, April 3, 2012 11:28 AM

Answers

  • Hezequias --
     
    What you are seeing is the default behavior of Microsoft Project 2010, regardless of whether you are connected to Project Server or not.  The permission to save a Protected Baseline only affects the use of the Set Baseline dialog.  In your situation, when you disabled this permission, the prevent your users from saving a Baseline in the Baseline through Baseline 5 sets of fields using the Set Baseline dialog.
     
    As you have noted correctly, Microsoft Project 2010 does allow a user to insert a Baseline field, such as the Baseline Start field, and then to manually edit data in that field.  I believe that manually editing Baseline information constitutes tampering, and should not be tolerated.  Unfortunately, there is no way that you can prevent this.  Instead, I would recommend you use a training and performance process to tell your PMs not to tamper with Baseline data.  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, April 3, 2012 12:28 PM
    Moderator

All replies

  • Hi Hezequias,

    Seems you are working in Project Server integrated mode. In MS Project standalone you cannot enforce that when a user sets a baseline or overwrite an existing baseline.  The client will just alert you about the overwrite of a baseline, but won't stop.

    Project Server however have the concept of protected baselines, it has a category permissions allowing access to 'Save a Protected Baseline'. Through this permission you can limit who can save to baselines 0-5, so only suitable PM/Admin(s) will save.

    Refer to : http://technet.microsoft.com/en-us/library/cc197622.aspx

    There is a similiar thread also : http://qa.social.technet.microsoft.com/Forums/en-US/projserv2010setup/thread/bfa244f9-f33a-432d-b53c-edf87d390a70

    And this thread confirms the issue you are facing : http://social.technet.microsoft.com/Forums/en-US/projectprofessional2010general/thread/746e6d9f-01ab-4547-b8ca-4f33422a1441/


    Sapna S


    Tuesday, April 3, 2012 11:49 AM
    Moderator
  • HiSapna

    Thanks for the reply,actuallyworkingwith ProjectProfessional 2010ProjectServer 2010integrated with,perfectyour analysis.

    My questionboils downexactlyto the secondpoint that youcommentedEvendefiningthe categorypermissionSave Baselineprotectedand choosingthe people whomay or may notsave thebaseline inthe first instanceworks andapplyfor permission.Howeverif thissame usercan not savethe baselineto insert the columnfrom baselinein the viewfrom ProjectProfessional 2010which containsthe datesalready storedin it,he canedit and modify thesedatesand worst of allif heuse theFile menuand thenSaveFilepublishit storesthe changes madein the projectwhich I thinkis notafunctioningcorreto.Queroa way to correctthis difficultyis that possible?

    Hezequias Vasconcelos

    Tuesday, April 3, 2012 12:08 PM
  • Hezequias --
     
    What you are seeing is the default behavior of Microsoft Project 2010, regardless of whether you are connected to Project Server or not.  The permission to save a Protected Baseline only affects the use of the Set Baseline dialog.  In your situation, when you disabled this permission, the prevent your users from saving a Baseline in the Baseline through Baseline 5 sets of fields using the Set Baseline dialog.
     
    As you have noted correctly, Microsoft Project 2010 does allow a user to insert a Baseline field, such as the Baseline Start field, and then to manually edit data in that field.  I believe that manually editing Baseline information constitutes tampering, and should not be tolerated.  Unfortunately, there is no way that you can prevent this.  Instead, I would recommend you use a training and performance process to tell your PMs not to tamper with Baseline data.  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, April 3, 2012 12:28 PM
    Moderator
  • I agree with Dale, this is definately a training need. It cann't be controlled through tool, only training and process notifications can keep the users updated on this.

    Sapna S

    Tuesday, April 3, 2012 12:41 PM
    Moderator
  • While notthe answerI expectedthanksDale.

    Hezequias Vasconcelos

    Tuesday, April 3, 2012 12:44 PM
  • Hezequias --
     
    You are more than welcome for the help, my friend!  :)
     

    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, April 3, 2012 12:47 PM
    Moderator