Logs tab on Import or sync HRMS data page is to show log records of every HRMS sync that happens automatically on daily job run in the system or the ones those are triggered manually.
More details about each column shown in the image above -
Action type - Whether it was an auto sync (that happens on daily job run by system) or manually triggered
Import from - Name of user from whose computer file was uploaded and triggered manually or was synced
Date - Date when sync took place
File name - File name from which system took data to be updated in UpRaise
File path - File path of the file that is processed to sync data
Total records - Total records available in the file
Successfully synced records - Number of Successfully synced records
Partially synced records - Number of partially synced records
Sync failed records - Number of sync failed records
Error Handling
Once you have imported the file, you might receive some errors due to which the user and team data import failed partially or completely. To avoid these errors please make sure you go through the below list and try to eliminate as many errors as possible in your data.
If you have still got any errors, feel free to reach out to us via our Service desk.
Error
Reason
id or name parameter is missing
Id or name parameter is missing in team or user record
description value is missing
Team disciption is missing
Invalid user
Jira user does not exist or user id is invalid
Manager not found.
No manager added for the user in user record
Value of user role parameter is invalid
This parameter is mandatory in case user-based access is turned on. Possible options are 'USER' & 'NO_ACCESS'
User role parameter accepts user role input only in capital letters. Check if you have entered user role in small letters for given user record
This is beacuse the cercular user dependency. Please check if the user is updated as their own direct or indirect manager
There is a mismatch between external id & email
User’s external id and email does not match. System alway check for the external id that was provided in first sync. Make sure, your HRMS tool sends the same id everytime.
team name should be unique, this team name is already linked with another external Id
The team name already exists in system that is associated with some ther external team id.