Symptom
- Loading data to Job Profiles (e.g., longDescriptions, shortDescriptions, header) fails with one of the following error codes:
- 1. Invalid content of field [???JOBPROFILE_LOCALIZED_DATA_desc???]: The entity name must immediately follow the '&' in the entity reference. => line[#], col[#]
- 1. Invalid content of field [???JOBPROFILE_LOCALIZED_DATA_desc???]: The content of elements must consist of well-formed character data or markup. => line[#], col[#]
- 1. You can't save the sections ([???JOBPROFILE_LOCALIZED_DATA_desc???]) because they contain non-alphanumeric text. The use of non-alphanumeric text may create potential vulnerabilities for cross-site scripting (XSS) attacks. Update each of the sections to use only alphanumeric text.
- You cannot save the sections ([???JOBPROFILE_LOCALIZED_DATA_desc???]) because they contain non-alphanumeric text. The use of non-alphanumeric text may create potential vulnerabilities for cross-site scripting (XSS) attacks. Update each of the sections to use only alphanumeric text. with the index 0
- No requests are visible in the ODATA API log monitor when the failure occurs.
- httpCode 500 is observed for failed ODATA requests.
- Manual creation of content works in the UI
Environment
- SAP SuccessFactors Job Profile Builder
- SAP SuccessFactors Metadata Framework
Reproducing the Issue
- Attempt to create a Job Profile via ODATA upsert using the integration.
- Observe that some runs succeed while others fail.
- Check the OData API log monitor and observe that no request is logged when the failure happens.
OR
- Attempt to create Job Profile data using Manage Job Profile Content Import/Export
- Review job in Scheduled Job Manager
- Error is present in details
Cause
- Job profile Content contains unsupported character codes
- Job Profile content contains line break tags with invalid HTML/XHTML syntax (for example, without a proper termination).
Resolution
- Review the content for Job Profile descriptions (Short Description and Long Description) across all locales.
- Ensure every tag is properly closed. For example <br> should be <br></br>.
- Escape special characters in description text where needed (for example, replace & with &). Reference Implementing and Managing Job Profile Builder - Troubleshooting Tips Using Manage Job Profile Content Import/Export.
- If adjusting via the UI, open Manage Data, update Short Description and Long Description for all locales in one save to let the rich text editor normalize markup.
See Also
Keywords
JPB, MDF, Import, special characters, Invalid content of field, ampersand, character, odata upsert, job profile, job profile builder, short description, long description, localized data, non-alphanumeric text, xss, httpcode 500, JOBPROFILE_LOCALIZED_DATA_desc, html syntax, self-closing tag, intermittent failure, odata api , KBA , LOD-SF-TIH-JPB , Job Profile Builder , LOD-SF-MDF-IMP , Import and Export Issues , LOD-SF-MDF-API , OData APIs & Integrations , Problem
Product
SAP SuccessFactors Platform all versions
SAP Knowledge Base Article - Public