Skip to content

Latest commit

 

History

History
108 lines (57 loc) · 6.72 KB

multiple-views-c62b82e.md

File metadata and controls

108 lines (57 loc) · 6.72 KB

Multiple Views

You can configure your List Report to display one or more additional tables and charts next to the main List Report table in separate views. The user of your application can switch between views using an icon tab bar. The tables in the views can be based on any entity in your service. The charts can be based on any entity as long as it contains aggregable and groupable properties.

Note:

Groupable and aggregable properties are defined on the service level with@Aggregation.ApplySupported. If it is not provided, you cannot generate chart views with Page Editor. If you want to use custom aggregations for chart measures, your service should also have properties aggregated with @Aggregation.CustomAggregate.

If you want to use the transformation aggregations, make sure your app runs with SAPUI5 version 1.106 or higher to ensure transformation aggregation with @Analytics.AggregatedProperty is supported. Transformation aggregation with @Analytics.AggregatedProperties isn't supported as this annotation is deprecated in favor of @Analytics.AggregatedProperty, see OData Analytics.

Note:

You cannot configure multiple views if your List Report is configured to display an Analytical Chart above or as alternative to the main List Report table. For more information, see Analytical Chart. You can delete an Analytical Chart to enable adding views.

Adding a Table or Chart View

  1. In the Page Editor for the List Report page, click the ➕ (Add) icon on the Views node.

  2. In the popup menu, click Add Table View or Add Chart View. A popup dialog allows to choose an Entity from the OData Service. If you chose to Add Chart View, you are also prompted for the minimum required data to generate a chart: chart type, a dimension, and a measure.

    A measure can be specified by selecting one of the following:

    • Use existing measure
    • Create new measure

    If you choose to use an existing measure, select one of the available measures defined with custom or transformation aggregations in the Name field.

    If you choose to create new measure, choose the aggregable property and one of the supported aggregation methods.

    This allows you to create a new dynamic measure and use it in the chart.

    Note:

    The technical name and the label are generated automatically . You can then adjust the generated label in the Property Panel.

    Note:

    Create new measure only works with transformation aggregations so it should be used for apps run with SAPUI5 version 1.106 or higher. If all the possible measures based on all the aggregable properties and supported aggregation methods are already defined in the project, you cannot create a new measure. Use an existing measure instead.

  3. Click Add in the dialog. In the Page Editor, a new subnode is appended to the Views node with generated view label.

    Note:

    The table is added with no columns. You can add columns using the ➕ (Add) icon for the Columns subnode.

The following changes take place in the annotation file:

  • UI.LineItem or UI.Chart annotation with qualifier is generated targeting the EntityType referenced by the selected EntitySet.
  • If you chose to create a new measure, @Analytics.AggregatedProperty is applied to the selected aggregable property with your chosen aggregation method.
  • Views/Paths section in manifest.json is generated or appended with an entry pointing to the generated UI.SelectionPresentationVariant. If different from the main EntitySet of the, List Report the chosen EntitySet is added to the paths entry.

Note:

If the Views/Paths section in the manifest.json file did not exist before, a second entry is created with the table or chart view, with the first entry representing the original table.

Moving Table or Chart View

All table or chart views are represented as subnodes of the views node. Drag and drop them or use the corresponding (Move Up) or (Move Down) icons to change the view sequence in the List Report page.

Nodes example for List Report

Deleting Table or Chart View

To remove a table or chart view, click the 🗑️ (Delete) icon on the corresponding views node.

Note:

It's not possible to remove the last table view that is based on the main entity set of the List Report.

If all views except the last table view are deleted, the List Report is implicitly converted into a plain List Report:

  • Views/Paths section in the manifest.json file is removed.
  • If needed: defaultTemplateAnnotationPath in the manifest.json file is created to point to an UI.SelectionPresentationVariant.
  • Views do not display any subnodes: details of the List Report, such as columns and actions, can be maintained in the Table node.

Table or Chart View Properties

View Label

View label is a text used to indicate a view on an icon tab bar above the table or chart. It is auto-generated when you add a view. You can change the generated label by entering the text that is meaningful in your application context.

Note:

The view label can be prepared for translation. For more information, see Internationalization (i18n).

Presentation Variant

The Presentation Variant property lets you define the representation of the table or chart data such as sorting.

The Presentation Variant property lets you sort the table data and is maintained the same way as in the standard List Report table. For more information, see Table.

The Presentation Variant for the chart view is maintained the same way as in the Analytical Chart.

Note:

As different views in the List Report are not necessary based on the same entity, you cannot reuse the same Presentation Variant for different views. For this reason, the options From Chart or From Table are not provided. To have the same representation of different views, just define the same options for each related view.