SAP Knowledge Base Article - Public

2705962 - Missing field on OData Entity from Metadata

Symptom

Error Code 500 related to an Invalid property name(s)

Environment

  • SuccessFactors
  • Provisioning

Reproducing the Issue

Error message:

[EXCEPTION] ODATA Execution Error Code: 500-ServerErrorException Internal Server Error-Invalid property name(s): XXXXXX/YYYYYY

Subtitle:

XXXXXX = Entity name

YYYYYY = Field name

Cause

Missing an OData field from an Entity in Odata Metadata

Resolution

You need to work with your Partner or Consultants to add the missing field at your Metadata.

On Provisioning, your Partner/Consultant will check the below steps:

1 - Succession Management Section;

2 - Click on Import/Export Data Model;

3 - Select Import File and Load the xml data model file with the missing field.

4 - Submit;

 

Then, access your SucessFactors Instance and perform a OData Medatata Refresh as below steps:

1 - Admin Center > OData API Metadata Refresh and Export

2 - Refresh

You can also follow the steps from this KBA:

2171588 - SuccessFactors: OData API Metadata Refresh and Export

See Also

Frequently asked questions (FAQ):

Q: Can SF Integration support team perform this correction via Provisioning ?

A: No, SF Integration support team cannot change customer´s data in Production and non-Production, even with customer´s approval.

2298334 - Provisioning Access for Customers

Keywords

Error code 500; Exception Odata; Invalid Property Name; API Data Dictionary; Metadata; , KBA , LOD-SF-INT-ODATA , OData API Framework , LOD-SF-INT , SF Integrations - EC Payroll, Boomi/ HCI, API , How To

Product

SAP SuccessFactors HCM Core 1808