Available with Standard or Advanced license.
When an error is marked as an exception, only the error feature is modified. If an error is marked as an exception in the child version, it remains an exception after reconciliation. Here are some implications of this behavior:
- If an error is created as the result of updates to features in the child version, then marked as an exception in the child version, the resulting dirty area created on reconcile will span the features created, modified, deleted, or validated to create the error. By definition, this dirty area will also contain the exception.
- If the error is created as a result of validating a preexisting dirty area that existed when the child version was created, the resulting dirty area will be the original dirty area and will, therefore, contain the exception.
- If a preexisting error was marked as an exception when the child version was created, a dirty area is created that contains only the exception.
Learn more about how errors and exceptions work with versioned topological feature classes.
Feedback on this topic?