Type message limitations

All types have the following limitations:

• Only one version of a type can exist at a time. If a type with the specified id already exists, but it does not match the contents of the message, it will be rejected.

Static and Dynamic Type Limitations

Static and dynamic type messages have the following limitations:

• If the static or dynamic type is in use by a static data instance or a container, it cannot be deleted.

• Property nullability support can vary depending on the specifics of your type. For more information, see Nullability.

Unsupported Data Types

The following types and formats are currently not supported for type messages:

Enum Type Limitations

Enum type messages have the following limitations:

• If the enumeration type is in use by a static or dynamic type property of reftypeid, it cannot be deleted.

When an enumeration type is created, it creates an Enumeration Set in AF, and potentially a Digital State Set in DA. In order for the Digital State Set to be created, the following must be true:

• The enumeration values must start at 0.

• The enumeration values must be continuous.

• The id of the enumeration must be less than 80 characters long.

• The name of each enumeration value must be less than 80 characters long.

• The format of the enumeration must be either int16 or int32.