I administer a survey that has gone from about 2k records annually to about 20k records entered annually in the past 5 years. Data cleanup (QA/QC) has become a significant burden for our organization, and I am trying to improve my survey by reducing the amount of bad data being entered. One of the main issues we are having is erroneously duplicated confirmation numbers (conf_no) . However, there are instances where a duplicated confirmation number is legitimate so setting that field to unique in AGO isn't an ideal solution. Is there a way to configure the survey so that when a confirmation number is entered into the conf_no field a warning message would display to alert the user and ask them to double-check that they have the right confirmation number? Thanks in advance for any help! @Anonymous User @ZacharySutherby @JamesTedrick