locked
PWA schedule edits not working RRS feed

  • Question

  • We have a Project Server 2010 installation.  We have a situation where if we create a project via project pro (2010), we are able to do PWA schedule editing on that project.  But when the user imports a local .mpp file (not sure which version of Project Standard was used to create them?), then editing the schedule via the PWA is disfunctional -- gives the error message:  "Editing is not supported.  This project uses features that is not supported for editing."  I can find out the version of Project Standard that was used if it is relevant.  But is this even possible?  I.e. is it possible to import a local .mpp file to Project Server 2010 and have function schedule editing in the PWA?  Thanks, Tom.
    Thursday, August 29, 2013 12:31 PM

Answers

  • Tom --

    You have just run into the limitations of editing an enterprise project using the PWA interface.  I doubt that importing the MPP file is the cause of your problem.  Instead, does the imported project contain any of the following features:

    • Blank task rows
    • Fixed Work tasks
    • Task calendar applied as an override calendar on any tasks

    If your project includes any of the preceding, this means you cannot edit the project using the PWA interface.  Let us know and we will try to help.


    Dale A. Howard [MVP]

    • Marked as answer by Tom Stroud Thursday, August 29, 2013 3:24 PM
    Thursday, August 29, 2013 2:17 PM

All replies

  • Tom --

    You have just run into the limitations of editing an enterprise project using the PWA interface.  I doubt that importing the MPP file is the cause of your problem.  Instead, does the imported project contain any of the following features:

    • Blank task rows
    • Fixed Work tasks
    • Task calendar applied as an override calendar on any tasks

    If your project includes any of the preceding, this means you cannot edit the project using the PWA interface.  Let us know and we will try to help.


    Dale A. Howard [MVP]

    • Marked as answer by Tom Stroud Thursday, August 29, 2013 3:24 PM
    Thursday, August 29, 2013 2:17 PM
  • Dale,

      Thanks.  I can't confirm it directly, but I will contact the user and relay this information. 

    Tom

    Thursday, August 29, 2013 2:42 PM
  • Dale,

      It did turn out to be an issue with Calendars.

    Thanks Again,

    Tom

    Thursday, August 29, 2013 3:26 PM
  • Hi Tom --

    For a listing of scheduling features that are not allowed via the web (PWA) in Project Server 2010, download the "Web-Based Schedule Management Comparison" overview here:

    http://www.microsoft.com/project/en-us/project-server-2010-editions.aspx

    Every version of Project Server gets better, and some of the limitations that exist in Project Server 2010 have been removed in Project Server 2013. Here is an overview of some things that are new in 2013:

    http://office.microsoft.com/en-us/project-server-help/whats-new-in-microsoft-project-server-2013-HA102848108.aspx

    Here are some relevant points from the above page that pertain to project scheduling via PWA in 2013:

    • Schedule the entire project plan, instead of only the current task, without clicking Calculate or pressing F9.
    • Cost and material resources can be assigned to tasks.
    • Tasks can be assigned deadlines.
    • Formula custom fields are updated immediately while you work with them in Project Web App.
    • Tasks can be Fixed Work or Effort-Driven, with full functionality.
    • When you are editing a project, if no actions are taken for a set amount of time, the editing session will time out to preserve valuable memory. Timeouts are also necessary to be able to recover from things such as power, network, or disk failures.
    • A visual timeline of project tasks is included in the Schedule Web Part.

    Good luck!

    -- tz


    Tony Zink | Vice President, EPMA | http://www.epmainc.com | Blog: http://www.epmablog.com | Training: http://www.epmainstitute.com

    Thursday, August 29, 2013 4:53 PM