Error features and versioned feature classes

This topic applies to ArcEditor and ArcInfo only.

Error features and error features marked as exceptions have special behavior for how they are treated during the version reconcile process. Error features can only be updated by repairing the error (making an edit) or by marking an error as an exception.

The results of a reconciliation on errors and exceptions in the parent version is summarized in the following examples.

Any error created in the parent version, whether or not it is marked as an exception, will be brought into the child version as a result of the reconcile (as shown in Examples 1 and 2 below):

Example 1

Example 2

Any preexisting error marked as an exception in the parent version will be marked as an exception in the child version after the reconciliation.

Any error or exception that is deleted in the parent version (either by fixing the error or by the validation process) will be deleted from the child version as a result of the reconcilation.

The results of a reconcilation on errors and exceptions in the child version are summarized in the following examples.

Any error created in the child version will be deleted as a result of the reconciliation and, by definition, will be covered by a dirty area. The error can then be rediscovered by validating the dirty area.

Any error created in the child version and marked as an exception will remain an exception as a result of the reconciliation. By definition, it will be covered by a dirty area.

An error that existed in the parent version and is marked as an exception in the child version will remain an exception as a result of the reconciliation and will be covered by a dirty area. However, if the error was fixed in the parent version, then it will remain fixed in the child version (as illustrated in Examples 3 and 4 below):

Example 3

Example 4

An exception that existed in the parent version and is marked as an error in the child version will remain an error as a result of the reconcile and will be covered by a dirty area. However, if the exception was fixed in the parent version, it will remain fixed in the child version (as shown in Examples 5 and 6 below):

Example 5

Example 6

An error or exception that existed in the parent version and is fixed in the child version will remain fixed as a result of the reconcile as shown in Examples 7 and 8 below:

Example 7

Example 8

There are cases in which the same error can be created in both versions by validating a dirty area that existed in the parent version when the child version was created. If this error is marked as an exception in either the parent or child version, the reconcile will result in duplicate error features. In these cases, the error features will be covered by a dirty area and reduced to a single error or exception when the dirty area is validated. This is illustrated in the following two examples:

Example 9

Example 10