topic Problems with DR checks and data that has relationships in ArcGIS Data Reviewer Questions https://community.esri.com/t5/arcgis-data-reviewer-questions/problems-with-dr-checks-and-data-that-has/m-p/437676#M655 <HTML><HEAD></HEAD><BODY><P>This is going to be a long story, because I have tried several things...</P><P>I am running ArcGIS Desktop with Data Reviewer for 10.3.1.</P><P>I am running a series of DR checks from a batch file.&nbsp; The data that's being checked is from a custom application that checks-out a local replica from an enterprise geodatabase via a geodata service.&nbsp; Upon check-out, the custom application adds relationship classes to the local file gdb and also performs some joins for map symbology purposes.&nbsp; The local replica is comprised of a couple feature classes; one point (DAMAGE_POINTS) and one poly (DAMAGE_AREAS) along with a separate table that holds attributes that describe these features (OBSERVATIONS).</P><P>I have several SQL checks that query for certain conditions in the OBSERVATIONS table, but of course, I want to be able to traverse from the Reviewer table to the actual features that are related to the OBSERVATIONS highlighted by the test.&nbsp; I quickly realized that something was wrong.&nbsp; First when I highlight a row in the Reviewer Table, right click and select "Selected Related Row", a new table view pops up for OBSERVATIONS with a highlighted row.&nbsp; This table view and highlighted row are somehow detached (for lack of a better word) from the "real" OBSERVATIONS table in that you can't see the unselected records or use "Related table" button to see the related features.&nbsp; So I'm dead in the water with using a simple SQL check on the OBSERVATIONS table to find the related features.</P><P>Next I tried a "Table to Table Attribute Check" to run the same query setting the Feature Class 1 to be DAMAGE_AREAS and Feature Class 2 to be the OBSERVATIONS table (with the SQL where clause for the condition I'm looking for), then I use the "Compare Attributes" section to set the fields in each table that form their relationship (Class1_ID = Class2_ID).&nbsp; This actually works and I can use the DR table to zoom to and highlight the offending feature.&nbsp; The problem is it takes a REALLY LONG time to process these table to table checks and my users are getting very frustrated and so am I.&nbsp; The same simple SQL table check is lightning fast.&nbsp;</P><P>So I guess my question is why doesn't the Reviewer table play nice with my OBSERVATIONS table and let me use the relationship classes to find the related features? And/or why does doing the"Table to Table Attribute Check" take so long to perform?&nbsp; For instance, I have 5 of these types of checks looking at tables that have about 10K records each and it took about 2 hours.&nbsp; The same simple SQL check takes less than a minute.</P><P>Any thoughts or help would be greatly appreciated!</P></BODY></HTML> Thu, 02 Feb 2017 18:19:19 GMT JeaninePaschke1 2017-02-02T18:19:19Z Problems with DR checks and data that has relationships https://community.esri.com/t5/arcgis-data-reviewer-questions/problems-with-dr-checks-and-data-that-has/m-p/437676#M655 <HTML><HEAD></HEAD><BODY><P>This is going to be a long story, because I have tried several things...</P><P>I am running ArcGIS Desktop with Data Reviewer for 10.3.1.</P><P>I am running a series of DR checks from a batch file.&nbsp; The data that's being checked is from a custom application that checks-out a local replica from an enterprise geodatabase via a geodata service.&nbsp; Upon check-out, the custom application adds relationship classes to the local file gdb and also performs some joins for map symbology purposes.&nbsp; The local replica is comprised of a couple feature classes; one point (DAMAGE_POINTS) and one poly (DAMAGE_AREAS) along with a separate table that holds attributes that describe these features (OBSERVATIONS).</P><P>I have several SQL checks that query for certain conditions in the OBSERVATIONS table, but of course, I want to be able to traverse from the Reviewer table to the actual features that are related to the OBSERVATIONS highlighted by the test.&nbsp; I quickly realized that something was wrong.&nbsp; First when I highlight a row in the Reviewer Table, right click and select "Selected Related Row", a new table view pops up for OBSERVATIONS with a highlighted row.&nbsp; This table view and highlighted row are somehow detached (for lack of a better word) from the "real" OBSERVATIONS table in that you can't see the unselected records or use "Related table" button to see the related features.&nbsp; So I'm dead in the water with using a simple SQL check on the OBSERVATIONS table to find the related features.</P><P>Next I tried a "Table to Table Attribute Check" to run the same query setting the Feature Class 1 to be DAMAGE_AREAS and Feature Class 2 to be the OBSERVATIONS table (with the SQL where clause for the condition I'm looking for), then I use the "Compare Attributes" section to set the fields in each table that form their relationship (Class1_ID = Class2_ID).&nbsp; This actually works and I can use the DR table to zoom to and highlight the offending feature.&nbsp; The problem is it takes a REALLY LONG time to process these table to table checks and my users are getting very frustrated and so am I.&nbsp; The same simple SQL table check is lightning fast.&nbsp;</P><P>So I guess my question is why doesn't the Reviewer table play nice with my OBSERVATIONS table and let me use the relationship classes to find the related features? And/or why does doing the"Table to Table Attribute Check" take so long to perform?&nbsp; For instance, I have 5 of these types of checks looking at tables that have about 10K records each and it took about 2 hours.&nbsp; The same simple SQL check takes less than a minute.</P><P>Any thoughts or help would be greatly appreciated!</P></BODY></HTML> Thu, 02 Feb 2017 18:19:19 GMT https://community.esri.com/t5/arcgis-data-reviewer-questions/problems-with-dr-checks-and-data-that-has/m-p/437676#M655 JeaninePaschke1 2017-02-02T18:19:19Z