Problem
When pulling bedboards from KIPU, the initial import shows the correct number of records. However, duplicate bedboard records are created on every subsequent cron sync, causing the total record count to grow with each update cycle.
Possible Causes
The bed name field is misconfigured in the KIPU bedboard field mapping settings. When the system cannot correctly identify an existing record by its bed name during a sync, it creates a new record instead of updating the existing one — resulting in duplicates on every cron run.
Solution
Contact Dazos Support. This issue requires backend access to clear existing records and correct the field mapping. Reach out to the Dazos Support team and describe the duplication behavior, including how many records are affected and when the duplicates began appearing.
Clear all existing bedboard records. Dazos Support will remove all current bedboard records to eliminate the duplicates and provide a clean starting point before re-syncing.
Correct the bed name field mapping. The Dazos Support team will identify and fix the misconfigured bed name field in the KIPU bedboard mapping settings to ensure the system can properly match records during future syncs.
Re-pull the bedboards from KIPU. After the mapping is corrected, bedboards are re-imported directly from KIPU. The records should now sync cleanly, with bed names and numbers displaying correctly and no duplicates created on subsequent cron updates.
Verify the result. Confirm that the total number of bedboard records is correct and matches your KIPU bedboard, that bed names and numbers are displaying accurately, and that no new duplicates appear after the next cron sync runs.
Still Need Help?
Contact Dazos Support if:
Duplicates continue to appear after the field mapping has been corrected and records have been re-pulled.
The total record count does not match your KIPU bedboard after the fix.
Bed names or numbers are displaying incorrectly after the re-import.
You are unsure whether the issue is caused by a field mapping problem or another integration setting.
💡 Tip: When contacting support, provide details such as the total number of duplicate records, a screen recording or screenshots showing the duplication, and the approximate time the issue began.