Latest Contributions by JaimieChhu1

Hi, I'm working with data on an enterprise database.  My organizations authoritative data is stored and managed on an SDE and versioning is enabled.  As part of our workflow, any required edits to the SDE (e.g., additions, updates or deletions of the data) are performed through a version of the SDE (child of the parent SDE) and QCed before it is pushed up and posted to the SDE.  We are implementing Data Reviewer batch checks as part of our QC.  Often, we encounter errors that are exceptions and are marked as such.  Because of the time spent on investigating the errors, we would like for Data Reviewer not to reflag the same errors that we have already marked as an exception (i.e., filter out duplicates).  This does not appear to be a problem if we are working in same version that the error was produced under, but if I post my version edits to the SDE (the parent), and rerun the same batch checks in the parent version, the same error that was marked as an exception under the child version will flag again into the Reviewer table.  I understand this is because the duplicate filtering is based on several fields that include the Parameter field, which stores the database version the checks were run on.  How would I be able to exclude the version name in the parameters field or to exclude the parameters field all together in the filtering of duplicates so that the error doesn't again flag in either child or parent version. ... View more