Skip to content

Files

Latest commit

 

History

History
204 lines (119 loc) · 6.17 KB

basic-fields-2953503.md

File metadata and controls

204 lines (119 loc) · 6.17 KB

Basic Fields

Adding Basic Fields

To add a new field to an existing section, perform the following steps:

  1. Expand the required section and navigate your pointer to the field layer.
  2. Click the ➕ (Add to open the Add Fields pop-up window.
  3. In the Add Fields pop-up window, search for or select one or several fields from the drop-down menu.
  4. Click Add to add new fields to the Form section.

Note:

The following entity properties are excluded from the fields dialog creation process:

  • Properties of the type Edm.Guid.

  • Draft-specific properties, such as IsActiveEntity, HasActiveEntity, and HasDraftEntity.

  • Draft-specific navigation properties such as SiblingEntity, DraftAdministrativeData.

  • The properties already referenced in this or other sections.

Note:

You cannot add the field twice to the same section.

Moving Basic Fields

To move a field within a section or to a different section in the application, use one of the following functionalities:

  • Drag-and-drop

    By using the drag-and-drop functionality, drag the required field and place it in a different position within its section or in a different section once the field is highlighted in green.

  • Arrow buttons

    By using the (Move Up) or (Move Down) icons next to the field name, you can move the field either within its section or to the different section.

Move Fields to Another Section

To move a field to another section, drag and drop to a desired section.

Note:

Fields can be moved to a different section if the FieldGroup or Identification annotation are applied to the same entity as the originating section.

Move Multiple Fields

To move the multiple fields to another position, perform the following steps:

  1. Use the [Ctrl] + [Click] combination to select more than one field.
  2. Drag the selected fields to a different position with your pointer/mouse.

Note:

You can't move the field to the section if the same field is already part of it.

Deleting Basic Fields

To delete the fields, perform the following steps:

  1. Expand the required section and navigate your pointer to the field layer.

  2. Click the 🗑️ (Delete) icon to open the Delete Confirmation popup window.

  3. Click Delete to confirm the action.

    Note:

    During deletion of the field, UI.DataField record is removed from the UI.FieldGroup annotation. The annotations applied to the entity properties aren't deleted.

Maintaining Basic Field Properties

Field properties are associated with fields in the Field section and the application with the help of annotations. The following field properties can be edited:

For more information, see Appendix.

Label

To change the section label, perform the following steps:

  1. Select the required section and navigate to the properties pane area.

  2. Enter a new name in the Label text box. This field defines the text to be displayed at a section label.

    As a result, the section is renamed both in the Page Editor and in the application preview.

See Label Maintenance for more information.

Note:

See Internationalization (i18n) for translation if not yet there.

Restrictions

Define whether the field input in create/edit mode is mandatory, optional, or read-only. Use the Restrictions field to control the state of a property.

The following options are displayed in the restriction value drop-down menu:

Option

Description

None

No annotations are applied. Therefore, this field by default is considered optional.

Optional

This field can be left empty. No obligatory data input is required.

Mandatory

This field value must be provided. It cannot be empty.

ReadOnly

This field is displayed as read-only data with no editing allowed.

Note:

When the Object Page entity is not draft enabled (read-only), Display Type and Restrictions fields are not available in the property panel as the fields are not editable and are only used for displaying the value.

Note:

If restriction value is defined in the lower layer (e.g. in the service), the respective option is displayed with the suffix (base layer) and option None is not available. If the back-end restriction value cannot be resolved because unsupported annotation complexity, then the base layer value is displayed as a Complex (base layer).