Use Optimized View Mode in Analytic Applications

You can enable optimized view mode in your analytic application to make the contents load faster at runtime.

Optimized view mode includes several usability improvements, and it can also reduce application loading times in certain scenarios. However, not all features are available within this mode.

Only the specifics for SAP Analytics Cloud, analytics designer are mentioned here.

Enable Optimized View Mode

Optimized view mode isn’t by default enabled. You need to go into each analytic application to enable it respectively.

Note

Optimized view mode only applies to runtime, while you can enable it only at design time.

  1. Save your analytic application.

  2. From File in the toolbar, do one of the following:

    • Select Start of the navigation path (Save) Next navigation step Enable Optimized View ModeEnd of the navigation path.

      1. Select Start of the navigation path (Edit Analytic Application) Next navigation step Analytic Application DetailsEnd of the navigation path.

      2. Under View Time Optimization in the right section of the popup, switch on Enable Optimized Mode.

      3. Select Save to save your changes.

You'll see a dialog notifying you that the analytic application is being optimized. The application will be saved and reloaded when you've successfully enabled optimized view mode.

If the application can't be optimized or some items can't be included, you'll see a warning message. Review the details and, if possible, resolve the issues.

Note

After you enable or disable Optimized View Mode for an analytic application that’s already been scheduled for a recurring publication, in Calendar the file settings for this publication are still from the previous mode. In such cases, we recommend deleting the scheduled publication and rescheduling one after the conversion.

Unsupported Features

Currently in SAP Analytics Cloud, analytics designer, the following features aren't yet supported in optimized view mode. For other restrictions that exist in both stories and analytic applications, refer to Optimized Story Experience Restrictions.

  • Data change insights

  • Geo map with point of interest layer or feature layer

  • Creating story from analytic application widget

Note

Undo or redo operations for planning workflows at runtime aren't yet supported.

Feature Restrictions

Note the following respective restrictions for features in SAP Analytics Cloud, analytics designer, which are different from classic view mode:

  • Data access language: Measure and dimension descriptions are based on the data access language used by the analytic application when it was optimized, but not when it’s opened.

  • Theme: Some theme settings might not be applied to these widgets: filter line, chart and input control.

  • Export: Exporting widgets to CSV or tables to XLSX only supports Point of View as scope, while All isn’t supported.

  • Filter line:

    • In group filter mode, dynamic time range filters don't align with the system time when it’s changed.
    • Filters in group filter mode aren't shown in the appendix of the PDF export triggered by the table’s context menu.

  • Data refresh: The onResultChanged event isn't triggered when the chart or table is invisible and set to Refresh Active Widgets Only. When the widget becomes visible, the necessary query is sent and onResultChanged event is triggered.

  • Table navigation panel: On the table navigation panel, which is triggered by openNavigationPanel() API, the option to deselect all account dimensions isn't available.

  • APIs:

    • When triggered by setVariableValue API, the variable dialog doesn’t display member description for charts and tables.

    • The following APIs might not work well for tables if the hierarchical dimensions used in the script haven’t been used as the dimensions in the tables: Table.getDataSource().setDimensionFilter(), Table.getDataSource().copyDimensionFilterFrom(), Table.getDataSource().getDimensionFilters(), Table.getDataSource().getHierarchy(), Table.getDataSource().setHierarchyLevel().

    • At runtime, setting multiple values on tables and R visualizations via API such as setDimensionFilter changes the selection mode of a filter even if it was set to Single Selection at design time.

  • Scripting: Value help for dimensions, measures and all their members aren’t supported for geo map related scripting, but you can manually input the parameters.

Unsupported APIs

Currently, the following APIs don’t work in optimized view mode:

Feature Unsupported APIs
Geo map (not with point of interest/feature layer)
  • APIs that work in classic view mode:
    • GeoMap.openInNewStory()
    • GeoMap.setContextMenuVisible()
    • GeoMap.setQuickActionsVisibility()
  • APIs that only work in optimized view mode but don’t work with data source associated with geo map layers:
    • GeoMap.getLayer().getDataSource().getMemberDisplayMode()
    • GeoMap.getLayer().getDataSource().setMemberDisplayMode()
    • GeoMap.getLayer().getDataSource().getDataExplorer()
    • GeoMap.getLayer().getDataSource().getDimensionProperties()
    • GeoMap.getLayer().getDataSource().setHierarchy()
    • GeoMap.getLayer().getDataSource().expandNode()
    • GeoMap.getLayer().getDataSource().collapseNode()
Explorer

Related APIs aren't supported.
Data blending

Related APIs aren't supported.
Search to insight

Related APIs aren't supported.
Input control getActiveSelectedMembers(), setSelectedMembers()
Creating story from analytic application widget openInNewStory()
Smart grouping Related APIs aren’t supported.
Time series chart forecast getForecast()
Smart discovery Related APIs aren’t supported.
Data change insights Related APIs aren’t supported.