Example: Merge Records
This example database demonstrates how to identify all parent records with matching names and allows merging those records into a single one, including related child records, with a button click.
Description
The "Parents" table holds the main entities that are subject to de-duplication. Each record represents a parent entity (e.g., a customer, company, or account) and includes metadata such as the number of detected duplicates, a reference to the duplicate records, and the ID of the master record that will remain after merging. It also includes a field for capturing all related child records before the merge process. This table is the central point for identifying and resolving duplicate entries.
The "Childs" table stores records that are related to entries in the Parents table. Each child is linked to a parent record, which may be affected during the merging process. These records need to be reassigned to the correct master parent when duplicates are merged. This ensures data relationships remain intact and that no child record is lost or incorrectly linked.
Screenshots
To help you make the system work for your needs, we have developed the following service program:
- Discuss your needs with our staff.
- We’ll determine and confirm the workflow logic of your database.
- We’ll create a ready-to-use database to fit your exact business model.
- You’ll get a solution designed especially for your needs.
Any support materials, such as spreadsheets and real-life work samples would be very helpful as they would help us better understand your business process.
We offer free system configuration assistance
(up to 4 hours of consulting work).
If you decide that our database is not exactly what you need - you owe nothing.