3755445 - Rich Text field mapping to reportable custom field incorrectly rejected - Recruiting Management

This article describes a known issue wherein a user maps a template field of type “richText” to a reportable custom field column, the system rejects the mapping as “not permitted” and returns a 400 BadRequestException — even when the mapping should be valid. 

SAP SuccessFactors Recruiting Management

1. As an Admin, go to Admin Center > Manage Reportable Custom Fields.
2. Add a field with type “richText”. Save and Sync. 
3. Observe that the system returns “not permitted” and throws a 400 BadRequestException.

This is a known code issue. This will be patched in 2605p6 (Preview: 26-May-2026 | Production: 28-May-2026). Click on star to bookmark this article in order to receive updates about this issue. 

richText, Rich Text, reportable custom field, mapping not permitted, 400 BadRequestException, ReportableCustomFieldsValidator, isDifferentTypePermitted, type validation, template field type, manage reportable custom fields, error, RCM, Recruiting, KI1H2026, 2605 , KBA , LOD-SF-RCM-ADM , Admin Center, RBP, Permissions and Settings , Known Error