Convert field attributes to attributes

You can choose which objects with Field Attributes to convert to Attributes, but only first-level derived objects can be selected. That is, you can only select templates and instances that are directly derived from the $UserDefined base template. Objects derived from first-level templates or individual Field Attributes cannot be individually selected for conversion.

When you start the conversion process, you are presented with a list of all first-level templates and instances that contain Field Attributes. First-level templates without Field Attributes, but that have derived objects with Field Attributes, are also listed. From this list, you will select which objects to convert.

The conversion process is hierarchical and cascades to all child templates and instances of the selected objects. All Field Attributes contained in a template’s hierarchy of derived objects are converted.

Note: Objects will be unavailable for selection (grayed out) if the object or any of its derived objects are deployed, checked out, or protected. See Protect objects on export for more information about protecting objects.

To convert field attributes to attributes

Before starting the conversion process, see Special considerations when converting field attributes for a discussion of potential differences in behavior between converted Attributes and the original Field Attributes.

1. Back up all UserDefined Objects (UDOs) before starting Field Attribute conversion.

2. Ensure that all UDOs that you want to convert are checked in and not deployed. You will not be able to convert Field Attributes for objects that are deployed, checked out, or protected.

3. From the ribbon, select Galaxy, then select Configure, Integrated Development Environment, Convert UDO.

4. A list of all first-level objects with Field Attributes is displayed. First-level templates that do not themselves include Field Attributes, but have child objects with Field Attributes, are also listed.

   

5. Select the objects you wish to convert and select next.

   Note: Objects will be grayed out and unavailable for selection if the object or any of its derived objects are deployed, checked out, or protected.

6. The next screen is informational, and shows that Field Attributes will be consolidated onto the Attributes page. Select next to proceed.

   

7. The screen that follows is informational as well, and lists the limitations that apply to script conversion. These are:

   • Only field references that begin with "me." are converted.

   • Field references outside the selected objects are not converted.

   • Field references in scripts that use indirect functions or string manipulations are not converted.

   • Field references within Industrial Graphics are not converted.

8. Select next to proceed.

9. To begin converting Field Attributes for the selected first-level objects and their child objects, select the Convert button ( ) at the lower right.

   WARNING! Once you start the conversion process, it cannot be cancelled. The time needed to convert Field Attributes depends on the number of objects with Field Attributes, the number of Field Attributes, and the depth and complexity of the object hierarchy. Field Attribute conversion requires at least as much time as Galaxy migration.

   • Select back if you need to make any changes.

   • To cancel, simply close the dialog.

   WARNING! While the conversion process is active, you cannot deploy or edit objects.

10. Each object is listed as its Field Attributes are converted. The status of the conversion process is also reported to the OCMC Logger.

    Important: In the event that Field Attribute conversion fails for an individual template, the template will remain checked out after the conversion process stops. Undo the checkout for the template, and then you can resume attribute conversion for any remaining objects. To find which template did not convert, check the OCMC Logger.

11. When all objects containing Field Attributes have been converted, select Close.