How to extract the value of RBS in Enterprise Resource in Project Server 2019?

Custom_000039b78bbe4ceb82c4fa8c0c400284 is indeed the correct internal name for the RBS field. You can verify the exact internal name in the Project Server's Enterprise Custom Fields section.

RBS is typically a hierarchical field with lookup table values, ensure that you're correctly fetching and parsing these values.

There might be cases where the custom field has no value. Add checks to handle such cases.

Revised code for improve reliability:

// Retrieve the Enterprise Resource by ID
var specificRes = projectContext.EnterpriseResources.GetById(new Guid("46914ae8-3c55-488d-a045-4d1a5aaf1e74"));

// Load relevant properties
projectContext.Load(specificRes, r => r.Name, r => r.CustomFields, r => r.CustomFields.IncludeWithDefaultProperties(cf => cf.LookupTable, cf => cf.LookupEntries));
projectContext.ExecuteQuery();

// Locate the RBS custom field by its internal name
var rbsField = specificRes.CustomFields.FirstOrDefault(cf => cf.InternalName == "Custom_000039b78bbe4ceb82c4fa8c0c400284");

// Ensure the field exists and contains lookup entries
if (rbsField != null && rbsField.LookupEntries.Any())
{
    // Retrieve the full hierarchical path for RBS
    var rbsValue = string.Join(" > ", rbsField.LookupEntries.Select(le => le.FullValue));
    Console.WriteLine($"RBS for Resource '{specificRes.Name}': {rbsValue}");
}
else
{
    Console.WriteLine($"RBS field is not set or has no lookup entries for Resource '{specificRes.Name}'.");
}


=========================

string.Join = This code concatenates all LookupEntries to show the hierarchical path if there are multiple levels in RBS. Each LookupEntry represents a level in the RBS hierarchy, and FullValue provides the hierarchical value for that level.

the code check if rbsField is null and if LookupEntries contains any data before attempting to retrieve and display it

ExecuteQuery  = is called after loading the resource data, and not again after loading cusField. This reduces the chance of unnecessary network calls and potential misalignments in data fetching

Also ensure that the user or application context has the correct permissions to access custom fields, especially hierarchical fields like RBS.

Test your code with resources where you know the expected RBS values to verify if they are being retrieved correctly.


I hope this will fix your issue, but if the RBS field still returns unexpected values, verify that there are no issues with the lookup table configuration on the server side.