Symptom
- In the OData API dictionary, an unexpected duplicate field with the suffix "_1" is appearing.
- The appearance of these fields raises questions about their origin, impact, and potential effects on interfaces.
Environment
SAP SuccessFactors Recruiting Management
Reproducing the Issue
Navigate to the OData API dictionary in the SAP SuccessFactors Recruiting module.
Cause
The appearance of the new field with the suffix "_1" is due to a previous change in the field type, which was later reverted. This action resulted in a new field being recorded in the database with the same ID, causing the system to automatically add "_1" to the field ID.
Resolution
The new ...._1 property will appear whenever the customer configures the same field in two or more Job Offer XML templates and do not provide the same field attributes values, for example, if the field is defined in one template as required=TRUE and in another template as required=FALSE, a separate property will be created, as the system cannot keep one property with different attributes.
If you try to revert the change, or make the field attributes equal in all templates, the property will NOT be removed. This is expected behavior.
Keywords
SAP, SuccessFactors, Recruiting, RCM, OData, API, JobOffer, fieldname, fieldname_1, duplicate, fields, field, attributes, XML templates, recruiting , KBA , LOD-SF-RCM-API , Webservices & APIs , Problem