Get project custom fields (Project Server)

Question

I am trying to access, in a project detail page, the project context via Javascript to retrieve the data of the custom fields.

But my problem is that, when I try to access all the data it only shows me three fields, and there are at least 20.

My code:

<script type="text/javascript">

var contexto;
var proyecto;   
var fields; 


    function init() {       

        contexto = PS.ProjectContext.get_current();
        proyecto = contexto.get_projects().getByGuid(PDP_projUid);
        fields = proyecto.get_customFields(); 
        contexto.load(fields);
        contexto.executeQueryAsync(Function.createDelegate(this, this.Exito), Function.createDelegate(this, this.Error));

    }

    init(); 

    function Exito() {

        console.log('Exito');

        console.log(fields);
        console.log(fields.get_count()); 

        for(i = 0; i < fields.get_count(); i++) 
        {
            console.log(fields.get_item(i));            
            console.log(fields.get_item(i).get_name());
            console.log(fields.get_item(i).get_description());
        }

    }

    function Error() {
        alert('Error'); 
    }

</script>

All the fields, are controlled by the workflow, even the three that are successfully shown.

Any idea why this happens?

Answer 1

Fields by default are not loaded in CSOM, you need to specify what field you would like to load. Here is an example on how to do it.

projectContext.Load(projectContext.Projects,
    c =>
        c.Where(p => p.Id == new Guid(id))
            .IncludeWithDefaultProperties(f => f.Description,
                f => f.FinishDate, f => f.PercentComplete, f => f.StartDate, f => f.Id, f => f.Name,
                f => f.CreatedDate, f => f.Owner.UserId, f => f.CustomFields));

projectContext.ExecuteQuery();

Answer 2

From your replies I assume you have defined about 20 enterprise custom fields for the project entity, but to the project you are working with only 3 of these fields were applied explicitly. Custom fields not set on an entity (project, task or resource) will be not included in the result as you request the custom fields for the given entity (either via REST via the client OM, or via PSI).

You can verify, if the fields were assigned to the project and saved with a value via the following database query as well (should be executed on the project database):

SELECT F.MD_PROP_Name,
      FV.TEXT_VALUE      
  FROM pub.MSP_PROJ_CUSTOM_FIELD_VALUES FV
  INNER JOIN pub.MSP_CUSTOM_FIELDS F ON FV.MD_PROP_ID = F.MD_PROP_ID
  WHERE PROJ_UID = 'd152c2ba-047a-e411-9568-005056b45654'

In the query I assume the custom field is a text field (see FV.TEXT_VALUE) and the Guid in the WHERE clause is the id of your project.

You can set the custom fields on the project using the following code (as long as you know the ID of the project as well the internal name of your custom field):

var url = @"http://YourProjectServer/pwa"
var projectContext = new ProjectContext(url);

var projId = new Guid("98138ffd-d0fa-e311-83c6-005056b45654");
var cfInternalName = "Custom_b278fdf35d16e4119568005056b45654";
object cfValue = "Some value";

var proj = projectContext.Projects.GetByGuid(projId);
var draftProj = proj.CheckOut();
draftProj.SetCustomFieldValue(cfInternalName, cfValue);
var cfsX = proj.CustomFields;
draftProj.Publish(true);

projectContext.ExecuteQuery();

You can find the complete code (including resolving the project ID and internal name for the field) here.