That is, a person goes to work, and the clock in
Posted: Sun Jan 19, 2025 4:24 am
And it seems that not everything was foreseen in it. Integration with 1C allows you to collect data on employees' working hours for further accounting in 1C:ZUP. There are two possible configuration options: Lists of employees, their positions, departments are exported from 1C to Timex, and here they are assigned access levels, work areas and work schedules. Employee lists are imported from Timex and assignments are made in 1C.
Timex then collects event data and transfers north korea company email list the information back to the accounting system. On the one hand, the ability to directly enter employees into the Timex database gives it autonomy, on the other hand, it creates situations that we will now discuss. How the problem manifested itself When synchronizing 1C:ZUP–Timex, errors began to occur in certain cases: Associated with duplication of employees and positions.Timex is empty, as if he did not 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 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).
Timex then collects event data and transfers north korea company email list the information back to the accounting system. On the one hand, the ability to directly enter employees into the Timex database gives it autonomy, on the other hand, it creates situations that we will now discuss. How the problem manifested itself When synchronizing 1C:ZUP–Timex, errors began to occur in certain cases: Associated with duplication of employees and positions.Timex is empty, as if he did not 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 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).