2546923 - Performance Management OData API returns COE_ENTITY_NOT_FOUND error

• When running any of the Performance Form or 360 Multirater OData API entities, you get the following result:

{
    "error": {
        "code": "COE_ENTITY_NOT_FOUND",
        "message": {
            "lang": "en-US",
            "value": "[COE0007]invalid entity (or function) name: FormHeader "
        }
    }
}

• SuccessFactors Performance Management & 360 OData API

• In this example, we are running the OData for FormHeader entity:

• The reason why the system would return a COE_ENTITY_NOT_FOUND error is that the Entity "FormHeader " cannot be found within the system. Note that there is an extra space after the FormHeader which caused the error.

• Please ensure that there are no extra spaces before, after, and in between the entities that is being selected or else the system will not be able to fetch the correct entity and will return COE_ENTITY_NOT_FOUND_ERROR.
• In addition, sometimes your system/browser might automatically added "%20" in place of space (e.g. odata/v2/FormHeader%20?$format=json). Please ensure that there are no %20 within your call as %20 corresponds to space character in HTML5.

COE_ENTITY_NOT_FOUND, COE007, [COE007]invalid entity, Performance Managment OData API, PM OData API, %20, PM Form OData API, PMv12A OData API. , KBA , LOD-SF-PM-API , Webservices, OData APIs , Problem