Use Optimized View Mode in Analytic Applications

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

1. Save your analytic application.

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

   • Select (Save)  Enable Optimized View Mode.

   • 1. Select (Edit Analytic Application)  Analytic Application Details.

     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.

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

• scheduling

• data change insights

• geo map with point of interest layer or feature layer

• linked analysis among widgets including chart, table, geo map and R visualization

  Creating linked analysis from input control is supported.

• range filter on table

• creating story from analytic application widget

Note the following respective restrictions for features in SAP Analytics Cloud, analytics designer, which might be different from non-optimized 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 won’t align with the system time if it’s changed.
  • Filters in group filter mode won’t be shown in the appendix of the PDF export triggered by the table’s context menu.
  • In individual widget filter mode, you can’t add range filters to tables.

• Data Refresh:

  When an invisible chart is set to Refresh Active Widgets Only, the onResultSetChanged event won't be triggered unless the following APIs are called: getData(), getResultMember(), getDataSelection(), getResultSet(), isResultEmpty().

• APIs:

  • When triggered by setVariableValue API, the variable dialog won’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 might change 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.

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