You are performing an SFAPI call operation in User entity to update the employee's timezone information and the below error appears:
Invalid request message! Error: Invalid SFObject! Error: String length exceed the limit(actual=17, limit=16) of field timezone at [SFObject #1,field #1]!
Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental.
- SAP SuccessFactors HCM Suite
Reproducing the Issue
This can be seen when the below update request is used (This is an example)
This error occurs because the value provided exceeded the maxlength allowed for the "timezone" field.
From the SOAP Request, you can see that the field "timezone" has 17 characters. The error message indicates 16 characters is the limit.
You can fix this issue by increasing the maxlength of the field timezone from 16 to 64.
You can make this change in two different ways:
- Manually through your instance's data model
- Through BCUI, if your instance has it enabled
Making the change through BCUI
- Go to Admin Center
- Search for "Manage Business Configuration" and access it
- In the left side menu, go to Employee Profile > Standard > timeZone
- Change the value of the "Maximum Lenght" field to 64 and save
Making the change through your instance's data model
Note that, as a customer, you do not have access to Provisioning and, hence, you will not be able to make changes in the data model. To complete tasks in Provisioning, contact your Implementation Partner. If you are no longer working with an Implementation Partner, contact SAP Cloud Support. The KBA below can be helpful:
If you have access to the instance's provisioning:
- Export the data model file
- Locate the timezone field
- Change the "max-length" property to 64
- Import the new changed data model file into the provisioning.
Maxlength exceed, String length exceed the limit ,Timezone field error, user entity, successfactors, success factors, api, sfapi, soap, call, upsert, insert, update , KBA , LOD-SF-INT , Integrations , LOD-SF-INT-PRV , Provisioning Changes , Problem