FAQ

What happens if a record is flagged as both a duplicate and a child type at the same time? What is the priority of attributes?

The recommended order of events for Kernel's Cleaning action (outlined in Actioning) is to first Merge, then Associate , but users don't need to follow the recommendations in order.

Some customers prefer to use the hierarchy data first due to its non-destructive nature. The user can use hierarchy data to fill in the blanks of existing Parent Account fields, overwrite existing, or use a separate custom field, e.g., the one provided by Kernel in Custom fields.

Merge operations are destructive and may require further calibration, which means customers prefer to do this last.