RX_TAGS_AND_GROUNDS_ARCHIVE

Field Name

Description

TAG_AND_GROUND_ID

A unique identifier for a tag or ground. This field corresponds to the ID field in the RX_TAGS_AND_GROUNDS table.

TAG_ID_1

ID of the tag.

TAG_ID_2

ID of the tag.

TAG_ID_3

ID of the tag.

FCID

Feature class ID of the feature associated with the tag.

OID

Object ID of the feature associated with the tag.

SUBID

The unique ID of each segment of a complex edge.

X

The x-coordinate of the incident device.

Y

The y-coordinate of the incident device.

TAG_TYPE

Indicates the type of tag (e.g., Information, Do Not Operate, Do Not Close).

PHASES

Indicates which phases are affected.

GROUND

Indicates whether the step is a ground (yes/no).

FACILITY_ID

The Facility ID of the incident device as defined in the geodatabase.

REGION

The region in which the tag or ground is located. This field uses the REGION domain.

OWNER

The tag owner (who placed the tag).

TIME_PLACED

Time that the tag was placed.

TIME_REMOVED

Time that the tag was removed.

REMARKS

Remarks associated with the tag.

USER_CREATED

The name of the user who created the record. This field is populated automatically by Responder.

USER_UPDATED

The name of the user who updated the record. This field is populated automatically by Responder.

CHANGE_DATE

The time and date an operation was performed on the record.

OPERATION

The operation (e.g., insert, delete, update) performed on the record.

USER_UPDATED_ARCH

This field is not currently used by Responder. You may customize Responder to populate this field with the name of the user who updated the record.

ORIGINATION

Indicates where the tag was originated (i.e., manual or switching order). Any tags originated within a switching order may not be deleted in the Tags window.

SUMMARY

The summary text provided on the tag.

OWNER_NAME

The name of the tag's owner.

TAG_GUID

The GUID assigned to the tag.

FEATURE_CLASS_NAME

The name of the Feature Class on which the incident occurred, as it was configured/named when the Incident was archived.

QR code for this page

Was this helpful?