-
Notifications
You must be signed in to change notification settings - Fork 215
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ISSUE IMPORTING EMPLOYEE FROM TEMPLATE #439
Comments
Hi @wwwardany , Were you able to try it out with a fresh database? With Regards, |
I did, I tried 6 different samples with different same issue. Further more the information gets added successfully in the backend, but does not reflect on Horilla |
Hello @horilla-opensource One more thing to note, once added I cannot delete it from PGadmin |
Any update about this issue? is there anything I can provide to show the problem? @horilla-opensource |
I am experiencing the same issue. So the template only updates employee name and phone number. nothing else gets updated. is there a code we can amend to fix this challenge? |
Hello @horilla-opensource team,
This was a previously created ticket that was closed by the issue creator two weeks ago. It was very well written, so I decided to reopen it since I am facing the same issue. I can confirm that the below is indeed happening.
Currently I am facing an issue, where it shows error :
User ID Error
User with the email ID already exists while importing the excel file
example user email : [email protected]
Though the employee [email protected] does not exist, it show the above error. But when I try to create new employee with gmail [email protected] from GUI itself, it works!!
I tried accessing the database, the user is not present inside the employee_employe table, but the user exists in auth_user table. Is there any key reference which might affect the workflow?
Also I created another test user inside auth_user to ensure if it was the cause of issue and try importing the employee again using excel under employee dashboard so make sure if duplicate error was from the auth_user table, but the user was imported successfully, but not other real users. What could be the possible solution for this?
The text was updated successfully, but these errors were encountered: