We’ve just moved two key Project Server Enterprise Custom Fields (ECFs) from Project Server 2013 to SharePoint 2013 (i.e. To a specific Project Site SharePoint List). This has resulted in the inability to sort/group Projects data in the standard Project Server views, as SharePoint field information cannot be leveraged in Project Server (one of my ongoing gripes with EPM, one product - right?!)
Does anyone know how to automatically or programmatically update a single Project Server ECF (e.g. ‘Status’) with a SharePoint field containing the same set of ‘Status’ lookup values?
Ideally this would keep both fields aligned at all times and ensure the SharePoint field value could be used to configure Project Server Views.
Options are…SharePoint Workflow? Jscript? Other?
Many thanks in advance.
So is the requirement to set a project custom field value for Project A with the value set on an SP list for Project A? Or do you have a choice site column that contains a list of Statuses and you want that list of options to sync to the lookup table definition for the Project Level custom field Statuses then you set the value manually from the custom field for Project A?
Many thanks for the reply. The latter is the scenario we're working to,
i.e. Project A (ECF: 'Project Status' Lookup Values: Approved, Pending, Closed)
Project Site A (Site Column: 'Project Status' Lookup Values: Approved, Pending, Closed)
The client wants to use SharePoint as the repository (or control point) for this value but also wants this value to appear in the Project Server 'side of the world', i.e. They want this field to be an option when sorting, grouping etc in Project Server Views. So they want these two fields to always be aligned.
Does that make sense?