Delete Action

The Delete button is enabled by default if DeleteRestrictions is not provided. Note that if you want to specify conditions for deletion (using the deletable-path annotation), you must ensure that the setting sap:deletable has not been made.

Inline Deletion of Rows in Tables

You can enable inline deletion in a table of list report and object page. This can be enabled by setting the inlineDelete property to true for tableSettings as shown below:

"tableSettings": {
     "inlineDelete": true
}

After you enable this setting, a Delete button is displayed at the end of the row in the table.

Show or Hide the Create Button

You can control the visibility of the Create button depending on the UI.CreateHidden annotation. The annotation can be a Boolean value or can point to a path. In your annotation, set the path to point to a particular property (either true or false) of the parent object. If the value of the property is true, then the Create button is hidden; if it is false, it is visible.

The code sample below shows you how to hide or show the Create button, depending on the isCreateHidden property of the parent entity.

<Annotations Target="com.c_salesordermanage_sd.EntityContainer/HeaderPartner"> 
   <Annotation Term="UI.CreateHidden" Path="owner/isCreateHidden"/> 
</Annotations> 

Annotate com.c_salesordermanage_sd.HeaderPartner with @( UI.CreateHidden: owner.isCreateHidden);

Show or Hide the Delete Button

You can control the visibility of the Delete button depending on the UI.DeleteHidden annotation. The annotation can be a Boolean value or can point to a path. In your annotation, set the path to point to a particular property (either true or false) of the parent object. If the value of the property is true, then the Delete button is hidden; if it is false, it is visible.

The code sample below shows you how to hide or show the Delete button, depending on the isDeleteHidden property of the parent entity.

<Annotations Target="com.c_salesordermanage_sd.EntityContainer/HeaderPartner"> 
   <Annotation Term="UI.DeleteHidden" Path="owner/isDeleteHidden"/> 
</Annotations> 

annotate com.c_salesordermanage_sd.SalesOrderManage with @( UI.DeleteHidden: owner.isDeleteHidden);

Enable the Update or Delete Feature for the Table

Application developers can control the editability of table fields using UpdateRestrictions.

<Annotations Target="com.c_salesordermanage_sd.EntityContainer/Material">
    <Annotation Term="Capabilities.UpdateRestrictions">
        <Record Type="Capabilities.UpdateRestrictionsType">
            <PropertyValue Property="Updatable" Path="owner.isUpdatable"/>
        </Record>
    </Annotation>
</Annotations>

Application developers can control the Delete functionality of tables by using DeleteRestrictions.

<Annotations Target="com.c_salesordermanage_sd.EntityContainer/Material">
    <Annotation Term="Capabilities.DeleteRestrictions">
        <Record Type="Capabilities.DeleteRestrictionsType">
            <PropertyValue Property="Deletable" Path="owner.isDeletable"/>
        </Record>
    </Annotation>
</Annotations>

The system gives priority to the Org.OData.Capabilities.V1.NavigationRestrictions of the parent entity set. Depending on the value of the Deletable property of DeleteRestrictions, the related Delete button is shown or not.

• If NavigationRestrictions has the setting Deletable=false, the Delete button for the child entity table is never visible.

• If NavigationRestrictions has the setting Deletable=true or a path, the visibility of the Delete button for the child entity table depends on the value of UI.DeleteHidden of the child entity (that is, the table entity).

<Annotations Target="STTA_PROD_MAN.STTA_PROD_MAN_Entities/STTA_C_MP_Product">
  <Annotation Term="Capabilities.NavigationRestrictions">
    <Record>
        <PropertyValue Property="RestrictedProperties">
          <Collection>
            <Record>
               <PropertyValue Property="NavigationProperty" NavigationPropertyPath="to_ProductText"/>
               <PropertyValue Property="DeleteRestrictions">
                  <Record>
                     <PropertyValue Property="Deletable" Bool="false"/>
                  </Record>
               </PropertyValue>
           </Record>
        </Collection>
        </PropertyValue>
    </Record>
  </Annotation>
</Annotation>

The following table shows the visibility of the Delete button and the enabled/disabled state, based on the navigation restrictions:

Bound and Unbound Actions

Actions can either be classified as bound or unbound. Bound actions are those that need a context from the underlying control. Such actions cannot be invoked without passing a context (usually selected by user actions, such as selecting a row from a table). In the metadata, these actions are marked with the IsBound property.

<Action Name="REUNION" IsBound="true"> <!-- Bound action having a parameter -->
   <Parameter Name="_it" Type="com.sap.gateway.srvd.sadl_gw_appmusicro_definition.v0001.ArtistsType" Nullable="false" />
   <ReturnType Type="com.sap.gateway.srvd.sadl_gw_appmusicro_definition.v0001.ArtistsType" Nullable="false" />
</Action>

Enabling Single Selection for a Bound Action

Applications can control the number of table records that need to be selected for the action to be enabled. By default, for a bound action, this is 1 or more applicable records (that is, 1 or more records for which OperationAvailable evaluates to true). However, applications can change this configuration so that the action is enabled only when a single applicable record is selected. If more records are selected, then the action is disabled again. They can do this by specifying the enableOnSelect property in the manifest:

"@com.sap.vocabularies.UI.v1.LineItem": {
    "actions": {
        "DataFieldForAction::com.c_salesordermanage_sd.CreateWithSalesOrderType": {
            "enableOnSelect": "single” // Possible values: "single", "multi" (default)
        }
    }
}

"@com.sap.vocabularies.UI.v1.Chart": {
    "actions": {
        "DataFieldForAction::com.c_salesordermanage_sd.CreateWithSalesOrderType": {
            "enableOnSelect": "single” // Possible values: "single", "multi" (default)
        }
    }
}

Handling of Non-Computed Key Fields and Immutable Fields

When you create new table records using the POST mechanism, that is, not using NewAction, and provided that the entity set on which the create is being performed has visible non-computed key fields, then these fields are brought up in a dialog so that users can enter values before the create is performed. Since the key fields are immutable, that is, not changeable after the initial create, the dialog is the only chance for users to enter values. This is also true for the other non-key immutable fields (non-hidden and non-computed) in the main entity set.