nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

When would you use the "Delete" trigger for attribute rules?

MDB_GIS

I have recently started studying and implementing a few attribute rules in our data but I don't quite understand the purpose of the "Delete" trigger as it seems superfluous. If a feature is being deleted, then why would you need to update the attributes on it? What are the use cases for it? I'm assuming it is more useful on the constraint and validation rules? I haven't dove into those yet so I'm having a hard time envisioning how to use the delete Trigger.

Trouver plus de publications taguées avec

Geodatabase

Desktop

Accepted answers

Robert LeClair

Here's a few good examples of a delete trigger:

Delete feature using attribute rules? (esri.com)
Attribute Rule Delete Trigger to Update Another Fe... - Esri Community
Solved: Lessons Learned — Attribute Rules - Esri Community

All comments

MDB_GIS

Great examples and very interesting use cases. Thank you both!

Robert LeClair

ZachBodenner

Attribute rules can also be used to update other features than the one the rule is actually written on. As an example, say you have a feature that has a related table that tracks maintenance. You could write an attribute rule that could end edits to a maintenance record when the parent feature is deleted.

I'm sure there are many more examples, so I'm curious to see what others post about.

Rejoindre la conversation

Les membres connectés peuvent publier, suivre les mises à jour, et plus encore. Nouveau ici ? Inscrivez-vous gratuitement.

Liens rapides

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.