Hi,
I'm having a bit of an odd issue in that a PWA security group has Edit Project Summary Fieldsbut not Save Project to Project Server. When members of this group try to save edits to custom fields on a PDP, they receive an error stating:You need to have permissions to create a new project. Please ask the project Web App administrator for permissions. What does happen is that the value is changed for draft version of the field, but not the published version (i.e. once the project is checked in, the edit "disappears" until checked out again).
What is confusing is that with the same permission configuration in 2010, members of the group are able to edit the custom fields just fine.
I've tried various combinations of other permissions, but the Save to... is the magic one. Of course, this creates the issue that people are able to edit project schedules when they should not have that ability.
This is an on-premises installation of Project Server 2013 running the February 2015 CU. I've also tested this on another system and get the same behaviour so I am led to believe it is by design. Microsoft's documentation states:
Allows a user to edit only the enterprise project fields shown in the new project fields Web Part. If you do not have this permission, but have "Save Project to Project Server" you can still edit project-level fields/custom fields in the project field Web Part.
Am I missing something?
Chris