3552089 - No data for Custom Generic Objects configured under Talent Pool Additional Details - [COE0021]Invalid property names: cust_xxx/nameTranslationNav - Recruiting Management

• Custom Generic Object configured under Talent Pool Additional Details are not showing any data.
• Error in browser console: Request failed with status code 400: GET cust_xxx?$skip=0&$top=20&$select=externalCode%2cexternalName&$expand=nameTranslationNav&$inlinecount=allpages - [{"code":"COE_PROPERTY_NOT_FOUND","message":"[COE0021]Invalid property names: cust_xxx/nameTranslationNav. Please check the property name in Admin Center > OData API Data Dictionary or entity metadata. Ensure there were no data model changes that removed this field, and please execute a refresh metadata to ensure the cache is not corrupted.","persistent":false,"targets":["/cust_xxx"],"type":"Error"}]

SAP SuccessFactors Recruiting Management

1. Go to Recruiting > Candidates > Talent Pool.
2. Click create talent pool.
3. Click on the square icon for the custom object field.
4. No values appear.

Troubleshooting steps:

1. Press F12 or right-click on the page and select Inspect.
2. It opens the browser developer tool.
3. Select the Console tab.
4. Reproduce the issue.
5. Observe the error: "[COE0021]Invalid property names: cust_xxx/nameTranslationNav".

To use custom objects for Talent Pool, the externalName of the custom object must be configured as "Translatable" instead of "String".

Please refer to the following steps to change the type of the externalName to "Translatable".

It is recommended to backup the custom object data before proceeding, as the externalName values associated with the old data type will need to be deleted.

Step 1 - Change the data type of externalName to "Translatable"

1. Go to Configure Object Definitions.
2. In the first dropdown, select "Object Definition".
3. In the second dropdown, select the custom object name.
4. Click Take Action > Make Correction.
5. Locate externalName and change the Data Type to "Translatable".
   
6. Click Save.
7. A message will pop up "Are you sure you want to change data type of the following fields: externalName? If data exists, all data associated with the above fields will be deleted."
8. Click Yes to proceed.

This will delete the externalName data associated with the old data type. Other data, such as the externalCode, will not be affected.

Step 2 - Refresh the OData API metadata

1. Go to OData API Metadata Refresh and Export to refresh the metadata.
2. Log out and log in again.

It is also recommended to run the "MDF Object Definition to DB Sync" job to prevent inconsistencies. For more details, refer to the KBA 2534674 - How To Schedule MDF Object Definition to DB Sync and Fix Inconsistencies In Metadata Framework.

Step 3 - Maintain the externalName values for the custom object

Use Manage Data or Import and Export Data to maintain the externalName values. This KBA provides the steps for using Manage Data. For more details, refer to the KBA 2506062 - How to Add Translations for Generic Objects.

1. Go to Manage Data
2. In the first dropdown, select the custom object name.
3. In the second dropdown, select the entry to edit.
4. Click Take Action > Make Correction.
5. Fill in externalName.
6. Click the globe icon to maintain translations.
7. Save the changes.

• KBA 2506062 - How to Add Translations for Generic Objects
• KBA 2534674 - How To Schedule MDF Object Definition to DB Sync and Fix Inconsistencies In Metadata Framework

RCM, CRM, Candidate, Talent Pool, GO, object, Invalid property names, nameTranslationNav , KBA , LOD-SF-RCM-CRM , Candidate Relationship Management , Problem