Hello,
I have a question about the 'Always run on full database' option that you can choose in a Data reviewer check. In one my batch jobs I have a geometry on geometry check that will find line features that do not share a boundary (****T****) with other line features of the same feature class. So I have the same feature class in Feature class 1 and 2. I have checked the option 'Always run on full database' for Feature class 2.
I would like to run this batch job on data with a certain definition query (on last edited date and user). (I can't use an SQL filter in the check itself, because I want to be able to use several mxd's with different definition querys)
So when I run the batch job, I choose the Features to validate option 'Definition query'. But now some line features are wrongly marked as an error. It seems like the check does not honour the 'Always run on full database' option and also for feature class 2 only uses the features that satisfy the definition query.
There's also one other check, which finds point features that do not touch line features. In this case, when I check the option 'Always run on full database' and choose the 'Definition query' option, everything seems to work fine. There are no 'wrong' errors.
Does anyone know what could be the cause of this problem? Could it be that the 'Always run on full database' option does not work when you have the same feature class in FC 1 and FC2?
For your information, I work with ArcMap 10.7.1
Bests,
Djurra