You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
2 biometric devices are used to send different check in/ check out records to same instance of ERPNext
there are multiple records with same User ID in both device ID 1 & 2
logs folder is deleted or either one of the device is unreachable.
For example, there are 2 employees in 2 different locations/ devices with same User ID. John Doe in Location/ Device ID 1 with User ID 29. Sarah Doe in Location/ Device ID 2 with same User ID 29.
Now, if we add another device config to the JSON array in local_config.py with a different IP address:
Running erpnext_sync.py will also push new record of Sarah Doe with device id 2.
Expected Behavior:
device id 1 records should have been checked against the new records of device id 2 for same User ID.
User ID should be checked against all Device ID before pushing to ERPNext.
Actual Behavior:
old records from device id 1 are pushed again to ERPNext as new records with device id 2 with same User ID.
Possible Discussion
A sample of attendance_success_log_2.log:
{"uid": 1235, "user_id": "29", "timestamp": "2023-04-12 16:30:48", "status": 2, "punch": 1}
For status: 2 is presumably device_id: 2, could we check for duplicate user_id against all status and reject those to get pushed to ERPNext.
The text was updated successfully, but these errors were encountered:
Scenario:
1
&2
logs
folder is deleted or either one of the device is unreachable.For example, there are 2 employees in 2 different locations/ devices with same User ID.
John Doe
in Location/ Device ID1
with User ID29
.Sarah Doe
in Location/ Device ID2
with same User ID29
.Now, if we add another device config to the JSON array in
local_config.py
with a different IP address:Running
erpnext_sync.py
will also push new record ofSarah Doe
with device id2
.Expected Behavior:
device id
1
records should have been checked against the new records of device id2
for same User ID.User ID should be checked against all Device ID before pushing to ERPNext.
Actual Behavior:
old records from device id
1
are pushed again to ERPNext as new records with device id2
with same User ID.Possible Discussion
A sample of
attendance_success_log_2.log
:{"uid": 1235, "user_id": "29", "timestamp": "2023-04-12 16:30:48", "status": 2, "punch": 1}
For
status: 2
is presumablydevice_id: 2
, could we check for duplicateuser_id
against allstatus
and reject those to get pushed to ERPNext.The text was updated successfully, but these errors were encountered: