Attribute Rules & Contingent Values in ArcGIS Pro
What They Do, Why You Want Them, and the One Thing That Will Ruin Your Day
Attribute Rules automate calculations, prevent bad edits, and validate existing data. Contingent Values stop users from picking nonsense combinations across fields. Also: once you enable either one, ArcMap is out of the picture.
The Problem We’re Actually Solving: “Creative” Data Entry
If you’ve ever opened a feature class and discovered three spellings of the same material (“PVC,” “P.V.C.,” and the fan-favorite “pcv”), you already know the villain of today’s story: attribute chaos.
Domains and subtypes help. But when you need your geodatabase to behave more like a system of record (and less like a suggestion box), you need the next level tools: Attribute Rules and Contingent Values.
First: What Are These Things?
Attribute Rules can automatically calculate values, restrict invalid edits during editing, and run QA checks. They complement domains and subtypes rather than replacing them.
Calculate Values Example
Field: Mapped_Acreage = Shape Area/43560
Contingent Values make values in one field dependent on values in another—using domains (and optionally subtypes) to control which combinations are allowed.
Example Contingent Values:
The Fine Print (a.k.a. the part people ignore)
Once you apply Attribute Rules or Contingent Values to a dataset, you won’t be editing that data in ArcMap anymore. Older apps may also be affected. This is not a drill.
Attribute Rules: The Three Flavors of Control
Attribute Rules come in three types. Pick the one that matches the job.
1) Calculation Rules (Increase efficiency, reduce typing)
These auto-populate values into the field using an Arcade expression. Common use cases include:
- calculating area in acres
- building a full address from multiple fields
- setting next inspection date to be today’s date + 12 months
They can run immediately (based on triggers) or in batch when you use Evaluate Rules / Error Inspector.
2) Constrain Rules (Stop bad edits at the door)
Constrain rules return a user-defined error message when a value fails your requirements. Examples include ALL CAPS, specific length, pole height ranges, or limiting pipe material based on pressure.
Constrain rules are great for preventing new bad data. If you want to hunt down bad stuff that already exists… you need Validation rules.
3) Validation Rules (Find the bad stuff that’s already there)
Validation rules evaluate existing features for attribute or geometry requirements and run when you use tools like Evaluate Rules or Error Inspector. In enterprise geodatabases, validation rules are supported only with Branch Versioning.
Triggers (a.k.a. “When does this thing actually run?“
Triggers apply to Calculation and Constrain rules: Insert, Update, and Delete. Triggers work with trigger fields so you can control what changes cause the rule to fire.
How to Add Attribute Rules (Pick Your Favorite Path)
ArcGIS Pro gives you multiple ways to add rules: from the Contents pane + ribbon, the Catalog pane (Data Design → Attribute Rules), or via geoprocessing tools (which means ModelBuilder/Python workflows too).
Configuration is basically: select rule type → add rule → fill out metadata → configure the expression, triggers, and behavior.
Contingent Values: Where “It Depends” Becomes a Feature
Contingent values exist for one reason: some fields should not be free-range. You define dependencies so selecting one value limits allowed values in another. This extends domains and subtypes and improves both editing efficiency and data integrity.
What’s required (don’t skip this list)
To use Contingent Values, you need: a geodatabase (not shapefiles), domains assigned to the dependent fields, field groups (collections of dependent fields), and (optionally) subtypes. Also: not compatible with ArcMap.
Enabling Contingent Values (The short version)
Workflow: determine dependent fields → verify domains/subtypes → create field groups → enter allowed value combinations → save changes.
What People Think vs. What Actually Happens
What actually happens: Domains control valid values in a single field. Contingent values control valid combinations across fields—which are where most real-world data entry mistakes are born. By limiting even the values that can be selected in a domain based on the value entered in another field you greatly reduce the chances of mistakes and errors.
The Moral of the Story
Attribute Rules and Contingent Values are two of the best ways to stop your geodatabase from slowly becoming a crime scene.
Use Attribute Rules to calculate, constrain, or validate data. Use Contingent Values to enforce dependent choices across fields using domains/subtypes + field groups. And remember: ArcMap will not be coming with you on this journey.
If you would like to learn more about attribute rules and contingent values, Cultivate Geospatial Solutions can provide you with training and support for these topics and a host of others. Feel free to contact us at training@cultivategeospatial.com
Tripp Corbin MCP / GISP
About CGS
Cultivate Geospatial Solutions, LLC is a leading provider of geospatial and asset management solutions, specializing in delivering innovative software products and strategies to help organizations harness the power of spatial data. With a team of experienced professionals and a passion for excellence, Cultivate Geospatial Solutions empowers clients to make informed decisions and achieve their goals.