topic Re: Create an attribute rule that uses background layers to calculate an ID in Attribute Rules Questions

Create an attribute rule that uses background layers to calculate an ID

JoseSanchez — Mon, 17 Nov 2025 13:06:29 GMT

Good morning,

When creating an attribute rule for a point or line feature class, how can I calculate the ID value of a new feature if the code includes, for example, the municipality code or the commission district code of the polygon in which it is digitized?

Additionally, if a line intersects multiple municipalities, how can we determine which one to use for the ID. Should we select the first, the longest intersected, or apply another criteria?

Re: Create an attribute rule that uses background layers to calculate an ID

MikeMillerGIS — Mon, 17 Nov 2025 13:20:56 GMT

Take a look at the templated rule - Generate ID. It has a option "Sequence by lookup" that could use an unique seq for grid. The templated rule writes the arcade, which you could modify to also get an ID field from the intersected layer.

https://pro.arcgis.com/en/pro-app/latest/tool-reference/data-management/generate-id-attribute-rule.htm#LI_A9FBB4CFF1C5407D9F9A092ABDF2FC3A

Re: Create an attribute rule that uses background layers to calculate an ID

RPGIS — Mon, 17 Nov 2025 14:02:07 GMT

The other thing to add, depending on if you are using an enterprise sde database, is the NextSequenceValue. This is first generated by running the generate sequence tool that, once created, will autoincrement a new numerical number. If you are looking make that id alphanumeric, then you can concatenate the next sequential number with any string characters you want.

Re: Create an attribute rule that uses background layers to calculate an ID

JoseSanchez — Tue, 18 Nov 2025 02:44:25 GMT

Hello,

Does it work when the Municipality, Commission District or Grid layer is in another SDE database.?

Re: Create an attribute rule that uses background layers to calculate an ID

MikeMillerGIS — Tue, 18 Nov 2025 12:02:36 GMT

Attribute Rules can only access tables in their own database. But there is a trick - https://support.esri.com/en-us/knowledge-base/creating-attribute-rules-to-access-feature-classes-in-a-000032146