2992487 - ToDoEntryV2 entity retrieving effectiveDate as chinese format

When you trigger a TodoEntryV2 call, the effective date field come with simplified Chinese format:

Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental.

SuccessFactors HXM Suite

• OData API

1. Trigger a TodoEntryV2 call, such as: TodoEntryV2?$select=wfRequestNav/wfRequestId,wfRequestNav/wfRequestUINav/subjectUserId,wfRequestNav/wfRequestUINav/operateUserId,wfRequestNav/wfRequestUINav/eventReason,wfRequestNav/wfRequestUINav/objectType,wfRequestNav/wfRequestUINav/subjectUserName,wfRequestNav/wfRequestUINav/effectiveDate,wfRequestNav/wfRequestUINav/operateDate&$expand=userNav,wfRequestNav/wfRequestStepNav,wfRequestNav/wfRequestUINav&$filter=status eq '2' and categoryId in '14' ,'17'&$format=json&$fileLocale=en_US
2. Verify that the response comes with the field effectiveDate with a Chinese date format 

The API User calling the query has its language as Chinese at the BizX.

You can change the User that is currently triggering the call language for English, at Settings > Change language (exemplified at KBA 2567011 - How to change SuccessFactors BizX language - User language). After changing it to English, the date format will come as English date format, as shown below:

2567011 - How to change SuccessFactors BizX language - User language

SAP SuccessFactors Employee Central OData API: Reference Guide

Todoentry2 chinese effectivedated date format fileLocale english language locale api odata  , KBA , LOD-SF-INT-ODATA , OData API Framework , Problem