Sign in
Microsoft.com
 
Microsoft
 
 
 
Microsoft >
> 
> 
Project Server 2010 - Date fields are editable for group that has READ ONLY rights

שאלה Project Server 2010 - Date fields are editable for group that has READ ONLY rights

  • 2012. május 29. 22:17
     
     
    Bejelentkezés a szavazáshoz
    0

    In PWA, we are using the schedule and Project Information detail pages. Based on requirements, we have locked down the Project Information page (project summary fields) so that only directors can edit the fields (Contribute) there while Project Managers can have READ ONLY permissions to that page and still be able to update the actual schedule.

    This is working fine except for date fields. If a PM opens the Project Information page, all of the fields are either greyed out or will not accept any text, including the date fields (e.g if a PM tries to enter 5/29/2012, nothing is entered). However, if they use the date picker feature, they are able to select a date, populate the field, and save that change.

    This appears to be a bug but if anyone has any ideas, I would appreciate any info provided.

    Thanks.

    Jeff

     

Az összes válasz

  • 2012. május 31. 4:27
    Moderátor
     
     
    Bejelentkezés a szavazáshoz
    0

    How did you lock down the page?  Have you locked down edit rights for the PMs within Project Server security?

    Andrew Lavinsky [MVP] Blog: http://azlav.umtblog.com Twitter: @alavinsky

     
  • 2012. június 7. 21:08
     
     
    Bejelentkezés a szavazáshoz
    0

    Yes, locked down that page to read only for PMs with Project Server Security. They have edit rights for the Schedule page but not the Project Information page.

    Jeff

     
  • 2012. június 7. 21:37
    Moderátor
     
     
    Bejelentkezés a szavazáshoz
    0

    I last played with that about a year ago, so admittedly, the behavior may have been changed by a more recent CU.  That being said, I've found that locking down PDP with SharePoint security just doesn't work in most circumstances.

    The only way it works is if you want to hide certain pages or fields from specific users.  That can be done, but other than that, there's no real way of implemetning field/user level security.

    Here's one way: http://azlav.umtblog.com/2011/06/15/applying-security-to-a-pdp-redux/

    I've also found adding filtered InfoPath or SSRS forms to a PDP also can create a read only experience.

    Andrew Lavinsky [MVP] Blog: http://azlav.umtblog.com Twitter: @alavinsky