3291874 - Warning Message when Changing the Data Type of a Custom String Field

In the 2H 2022 Release a new validation was introduced when changing the Data Type of a Custom String Field. 

Examples of the warnings can be seen below: 

• Field custom-string1: “Type of Reference Object” has been changed from “No Selection” to “CUSTOM_PICKLIST”. As this field includes existing data, it can lead to corruption of data and regression in API.
• custom-string1 is a deleted field. Adding this field to the configuration again can lead to corruption of data and regression in API, because this field includes existing data. 

SAP SuccessFactors: Employee Central 

1. Navigate to Manage Business Configuration 
2. Select an HRIS Element, such as jobInfo 
3. Change the Data Type of a custom string field or enable a custom string field which was previously used where you change the data type of the field. 
4. Save changes 
5. Warning Message is shown

This is an intended validation from the system.

The validation is highlighting that there can be existing data in this field and by changing the Data Type of the field, you may now be creating data issues in your system. 

If you are changing the Data Type of a field which has existing data, you should either: 

• Use a different custom string field, which has not previously been used, where possible. 
• Delete all existing data from this field. This would require you to run reports to see which users have existing data in this field and delete it before changing the Data Type of the field. 

If you do not do one of the above and choose to ignore the Warning message, no data will be deleted. If there is existing data for the original field configuration you may run into one of the below issues, please note this not an extensive list:

• Data on users profiles show unexpected behaviour:
  • Data does not show in the field in the users profile 
  • Random numbers show in the field in the users profile instead of a object/picklist label 
  • Data shows on view of the profile, but when editing the record the field shows no data
• Errors occur with integrating data for this field
• Reports show unexpected behaviour:
  • Unexpected values show in reports for some users 
  • Errors occur when trying to preview/generate reports

If you accidentally ignore the warning validation or have made this type of change prior to the 2H 2022 Release, we recommend that you run reports to highlight users who have incorrect data (data from the pervious configuration of the field) and correct this as soon as possible. 

ECT-201431, ECT-203183, ECT-204032, Type of Reference Object”, has been changed from “No Selection” to “CUSTOM_PICKLIST”. As this field includes existing data, it can lead to corruption of data and regression in API, custom-string1 is a deleted field, Adding this field to the configuration again can lead to corruption of data and regression in API, because this field includes existing data, error, change, field, bci, data type, business configuration, unable, to, save, property, source, data,  , KBA , LOD-SF-EC-BCI , Manage Business Configuration (BCUI) & Data Models (XML) , How To