ALTER FEATURES

ALTER FEATURES changes registry properties without replacing feature formulas. The singular form also supports field metadata.

Syntax

ALTER FEATURES [IF EXISTS] feature_name [, feature_name ...]
    property_action [property_action ...]

ALTER FEATURE [IF EXISTS] feature_name
    [FIELD field | FIELDS field [, ...]]
    property_action [property_action ...]

property_action ::=
    SET property = value [, ...]
  | ADD property = value [, ...]
  | REMOVE property [, ...]

FIELD and FIELDS are available only with singular ALTER FEATURE. Plural ALTER FEATURES always targets whole-feature properties and requires explicit feature names; it does not accept WHERE or LIKE.

Property actions

  • SET writes the supplied values.
  • ADD adds values according to the property’s merge semantics.
  • REMOVE deletes the named properties.
  • Multiple actions may be written in one statement and are applied atomically.

Property assignments accept = or :=. Values are expressions or DEFAULT.

Position is a dedicated property shape:

ALTER FEATURE FM.SALES.NET_REVENUE
SET POSITION AFTER FM.SALES.GROSS_REVENUE;

The available position values are HIDE, FIRST, LAST, BEFORE feature, AFTER feature, or an integer.

Other common properties include DESCRIPTION, custom string attributes, display format, and lifecycle STATUS. Units and entity annotations belong to the feature type and cannot be changed as arbitrary metadata properties.

Field metadata

ALTER FEATURE FM.SALES.ORDER_SUMMARY FIELD amount
SET DESCRIPTION = 'Net amount after refunds';

Use FIELDS to apply the same actions to several fields of one typed ROW feature.

Conditional form

IF EXISTS suppresses the missing-feature error.

See Feature metadata for property definitions and Feature lifecycle for status transitions.

Last update at: 2026/10/13 08:32:21