3136419 - explanation of lastModified field issue in User entity vs Data Subject Information report

You are checking the Admin center > "Data Subject Information" looking for the lastModified and comparing with the response of OData.User query under lastModified field.

Other possibility to check OData.User query under lastModified field is doing queries under Integration Center > User entity > lastModified field.

The values of the field lastModified don't match between the different places and you want to know the reason.

SAP SuccessFactors HXM Suite - ODATA and SFAPI - User entity

The last modified value you are looking into is only from Table_User_Sysinfo.

However, the table is not the only place for user changes. the last modified property will contain all the user related tables there. It is possible something changed in another user table for example Table_Users_info or Table_sm_user_info.

The data last modified parameter cannot be compared between the user table and the data subject table as the last modified in the data subject table can be read from multiple location and is not a reliable resource for comparison.

Going forward the parameter will have to be treated as individual entities and cannot be used for comparison purposes.

lastModified, Data Subject Information, Admin center, comparison, values don't match, OData.User entity, User,, Integration center query, SAP SuccessFactors HXM Suite , KBA , LOD-SF-INT-ODATA , OData API Framework , LOD-SF-INT , Integrations , LOD-SF-INT-API , API & Adhoc API Framework , How To

SAP SuccessFactors HCM Core all versions ; SAP SuccessFactors HCM suite all versions