Known Restrictions in Analytics Designer

A popup whose size is larger than the main canvas will not display correctly. Therefore, we recommend you not to place that big a popup on the canvas.

We recommend you add at least two widgets to a popup as widgets are the visualization of the popup. If no widgets are added, you won't see the popup displayed when you trigger it while running the analytic application. If only one widget is added, the height and width you set for the popup won't take effect.

In the case when a table or chart in the canvas acts as the source widget of a filter line widget in a popup and you reopen or refresh the analytic application, you will find the filter line is not listed in the reference list of the table or chart widget after you choose Find Reference. This is because currently we don't initiate the filter line widget in the popup when you reloading an analytic application.

To solve this, for now we recommend you activate the popups by clicking on each of them. Then the reference list will display all relevant results.

Now calling the setTheme API in a popup does not affect the theme settings in the popup. To solve this problem, you can add a panel to a popup and include all widgets in it. Then when you trigger the set theme API in a popup, all widgets added to the panel will apply the new theme settings.

Sometimes when designing an application, if you apply a new theme to the application and directly run the application without clicking to preview the popups, the new theme settings won't apply to the popups during the application run time.

To solve this, for now we recommend you activate the theme settings for the popups by clicking on each of them when designing the application. Then the theme will be correctly applied to the popups.

When a Popup has more than one table that has the option Optimized Presentation checked, the enter and backspace keys on the keyboard don’t work on the other table.

Please follow this workaround: When a table is used on a Popup, don’t check the option Optimized Presentation for the table.

When you work with tables in a popup, some functions in planning applications aren’t available such as mass data entry, distribute values, value lock management and version history.

Therefore, we don’t recommend using planning-related functions in popups. Alternatively, you can place the table on your canvas or a panel widget and then use the setVisible API to mimic the effect of a popup.

When you use the Planning Model API createMembers() for other dimensions other than a generic dimension, such as a Date dimension, the operation will not be successful.

Calling the version management APIs is not supported for BPC writeback enabled versions. Please use the Version Management option and/or the Publish Data toolbar button instead.

The DataSource function setVariableValue is not validating the values specified (neither at runtime nor at design time). All values and value combinations which are accepted in the prompt dialog will be supported. All other combinations might lead to errors or to an inconsistent state.

When you apply a dimension filter with the DataSource function setDimensionFilter, then setting ranges on fiscal hierarchies isn’t supported.

After applying a dimension filter with the DataSource function setDimensionFilter, users can modify filters in a table using the <n> Filter link in the table’s title area, though the setting Allow viewers to modify selections is turned off for the filter in the filter panel.

When multiple values are set via API such as setDimensionFilter at runtime, if the filter was set to Single Selection mode at design time, it won’t switch to the multiple selection mode and the value selection change won’t be triggered. Even if you remove and then reconfigure a filter, its original selection mode will be kept.

For the smart discovery defined before version 2021.1, If you call SmartDiscovery API and set setSettingsPanelVisible to true, you need to first input value in the new field Entity before you can successfully run this smart discovery.

In the Styling panel of a chart widget, the section Quick Menus controls whether the options in the chart's quick menu bar is visible or not when running the analytic application. However currently if you set the options such as Filter/Exclude, Drill, Smart Insight to invisible and run the analytic application, in Explorer of the chart you can still access these option.

After you have modified styling options of a table widget or any contents in a table widget, the settings below won't take effect:

• In the styling panel, choose Restore to Theme Preference and the table won't be restored to theme preference.

• Set the theme of the table back to default theme and default theme won't be applied.

When working with the navigation panel API openNavigationPanel and thus displaying the navigation panel, the reorder of measures is not supported for SAP Analytics Cloud models connected to SAP HANA data sources.

R visualization widgets of HTML content are not supported in Safari on Mac when third party cookie is not allowed in Safari.

Currently in Safari on a mobile device, Request Desktop Website for an analytic application is not supported.

While you can embed web pages, stories and other analytic applications into your analytic application via the web page widget, embedding an analytic application into stories or digital boardroom isn't officially supported.

Currently, analytics designer only supports dimension member input controls and calculation input controls based on restricted measures. For more information, see Configure Input Controls in Analytic Applications.

When you work with dynamic forecast note that calculation input controls for controlling the version or the cut-over date for the forecast table layout are not supported in Analytics Designer.

If an input control is collapsed, with All Members as selected members, and shows hierarchy in flat presentation, after setSelectedMembers API is called, it always shows member ID. To show description on the input control as configured, expand it, or do not select All Members or flat presentation in design time settings.

When triggered by an Export to PDF scripting object using exportReport API or by the Export function from a table’s context menu with All for Scope in settings, the PDF generation may cause garbled codes in the table for some languages such as Chinese, Japanese, Korean, Russian and Arabic.

When exported to PDF, widgets might not keep all CSS styling settings, for example, text decoration and opacity.

Due to the restrictions of JavaScript library and JavaScript PDF generator library that custom widgets are based on, custom widgets might not be fully exported to PDF. For instance, the chart axes of a custom widget based on D3.js won’t be exported. Custom widgets with CSS settings might not keep all the styling when exported to PDF, either.

For panels, flow layout panels, tab strips and page books, only contained widgets that can be seen at once without scrolling will be exported to PDF via the exportView() API. The same applies to data in scrollable charts and tables.

Number format settings only controls the in-context chart measures, where measure selection doesn’t include tooltip measures. To make all measures’ scaling consistent, we recommend changing the tooltip measures to the form of calculated measures so that you can modify their format.

Similarly, number format APIs only apply to measures on axes, Feed.ValueAxis and Feed.ValueAxis2. Tooltip measures on axes, Feed.TooltipValueAxis, aren’t supported, for example.

For charts, addMeasure and removeMeasure APIs only support Feed.ValueAxis, Feed.ValueAxis2, Feed.Color and Feed.bubbleWidth. When the structure member is a measure, addMember API only supports these feeds as well.