Skip to main content
Question

detecting duplicate records upon import


  • Data Voyager

re: Duplicate record checking upon inputting new records into RDM-Web

I know about setting up the uniqueness check and validations on the data once. I have users in the Web portal potentially entering duplicate values, can we set up uniqueness checks BEFORE they publish records. So, any record that is deemed duplicate (on 1 or more columns) would not be publishable. 

If this question has already been submitted/answered, please direct me there.

Thanks,

Hi ​@AH5 , 

Thank you for your question!
 

Unique key validation ensures that the attribute or a combination of attributes unequivocally identifies a record in the reference data. Any violation of this is immediately reported when the key appears as a duplicate in the data or when you create a new record in the web application. 
Firstly, the user entering the duplicated value will get a ‘uniqueness violation’ warning.
Secondly, if the user still decides to ignore it, they will get asked whether they would like to save such values regardless of the warning

On top of that, once that value is entered, 2 duplicated records will have ‘Valid’ state as false. 
And in the end, of course, this record will be rejected to be published, even if the user with the high permissions wanted to do that.

Will this work for you like this, please? 
If you have any questions, please let me know!

Kind regards,
Ekaterina


  • Data Voyager
  • June 13, 2025

This answer works well. We’ve looked at the on-the-fly and manual validations for the records in the table model. Thanks,


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings