idea Add functionality to work with non-spatial tables in Attribute Rules Ideas

Add functionality to work with non-spatial tables

cordtsra — Mon, 26 Feb 2024 15:35:34 GMT

I am currently working on converting RBJs to Attribute Rules. One issue I noticed is that I can't run a standalone check, or a composite check with a non-spatial table. I can create attribute rules for the non-spatial table, but there is no way to run those rules as you cannot add error layers for that table. Also, if I want to reference the non-spatial table in another feature class's attribute rules it doesn't appear in the drop down.

Re: Add functionality to work with non-spatial tables

JayCary — Mon, 26 Feb 2024 16:43:36 GMT

@cordtsra wrote:
I am currently working on converting RBJs to Attribute Rules. One issue I noticed is that I can't run a standalone check, or a composite check with a non-spatial table. I can create attribute rules for the non-spatial table, but there is no way to run those rules as you cannot add error layers for that table. Also, if I want to reference the non-spatial table in another feature class's attribute rules it doesn't appear in the drop down.

For clarification, which Data Reviewer check(s) are you trying to use with your table?

Re: Add functionality to work with non-spatial tables

cordtsra — Mon, 26 Feb 2024 17:43:37 GMT

@JayCary I am using the Table to Table Attribute check.

Re: Add functionality to work with non-spatial tables

JayCary — Mon, 26 Feb 2024 18:45:38 GMT

@cordtsraThanks for the clarification.

The Table to Table Attribute check requires that the data source referenced by the Features/Rows to Compare parameter must include a global ID field. Can you confirm that your table include a global ID?

Re: Add functionality to work with non-spatial tables

cordtsra — Thu, 29 Feb 2024 15:15:01 GMT

@JayCary I can confirm that the table includes the global ID field.

I can create the attribute rules for the non-spatial table, but I cannot add the error layers for it. I added error layers for a feature class and then tried running to see if the attribute rules for the non-spatial table would work and I didn't have any luck. Just to verify that the rules I created were working as intended, I added arbitrary points to the table (0,0) and ran the same attribute rules on the newly created feature class. I was able to generate calls there, but not on the non-spatial table.