Timex is empty, as if he did not
Posted: Thu Feb 13, 2025 3:24 am
How the problem manifested itself When synchronizing 1C:ZUP–Timex, errors began to occur in certain cases: Associated with duplication of employees and positions. That is, a person goes to work, and the clock in check in at the checkpoint.
After analyzing the situation, it became clear that the error is caused by the fact that in 1C:ZUP the employee is linked to an incorrect Timex employee due to the presence of duplicates in the latter.
This is due to the ability to enter an employee peru mobile database directly in Timex. For example, an employee can be entered into the control system twice: unloading from 1C in the position of “Chief Specialist” (correctly, in accordance with the staffing schedule); directly to the Timex database in the position of “Leading Specialist” (incorrect).
If an employee in 1C:ZUP is linked to the "Leading Specialist" in Timex, then his timesheet in 1C will be empty. Timex has a standard option to redefine the EmployeeLink–ID_Timex connection, but the scheme is complex and duplicates must be searched for manually, i.
e. wait until an error occurs in the timesheet and correct it immediately. Related to an incorrect code in the timesheet. The error occurred when an employee left maternity leave early (code OZ).
After analyzing the situation, it became clear that the error is caused by the fact that in 1C:ZUP the employee is linked to an incorrect Timex employee due to the presence of duplicates in the latter.
This is due to the ability to enter an employee peru mobile database directly in Timex. For example, an employee can be entered into the control system twice: unloading from 1C in the position of “Chief Specialist” (correctly, in accordance with the staffing schedule); directly to the Timex database in the position of “Leading Specialist” (incorrect).
If an employee in 1C:ZUP is linked to the "Leading Specialist" in Timex, then his timesheet in 1C will be empty. Timex has a standard option to redefine the EmployeeLink–ID_Timex connection, but the scheme is complex and duplicates must be searched for manually, i.
e. wait until an error occurs in the timesheet and correct it immediately. Related to an incorrect code in the timesheet. The error occurred when an employee left maternity leave early (code OZ).