Special considerations when converting field attributes

When you convert Field Attributes to Attributes, there may be some differences between the original Field Attribute and the converted Attribute.

• If the Field Attribute "Bad.Condition" was extended (for example, by adding historization), it will send alarm notifications after conversion, even if alarming was not enabled.

• Prior to conversion, the Field Attribute description is Analog_001.Desc. After conversion, this changes to Analog_001.Description.

• Prior to conversion the History Extension description points to Analog_001.Desc. After conversion, the History Feature points to Analog_001.Hist.DescAttrName.

• If a Field Attribute has "Generate event upon change" enabled, then the Log change feature (LogDataChangeEvent) will be added to the converted attribute.

• When the Field Attribute I/O option, "Output destination differs from input source," is selected and left unlocked, but Output destination is locked, the converted Attribute will have the following locking properties:

  • "Write to" will be locked. This is the same as the original Field Attribute property.

  • "Output destination differs from source" will be locked. This differs from the original Field Attribute property.

    Note: Default names for Field Attributes begin with either "Discrete" or "Analog." The conversion process preserves this part of the Field Attribute name, even though this division does not apply to the converted Attributes.