Duplicate detection with aggregation results config

Hi @Mel! If you’ve configured a ONE Desktop plan (i.e. post-processing plan) to export the invalid records to a database, you can add a Representative Creator or Group Aggregator step to group based on the two attributes to ensure one instance for each duplicate record. For example, if I’m grouping on code + id I will add those columns under the Group By section of the Representative Creator. The out_merged stream will include the new grouped records.

For more information on how the Representative Creator or Group Aggregator works, select the magnifying glass icon (top right) & type in “Representative Creator” to search through the ONE Desktop documentation. 

If you’re not using a plan to export the invalid results to a database, please elaborate more on how you’re exporting to the database. Let me know if you have any questions!