Specifies if a detailed message is displayed during data load processing.

• On — Detailed loading messages are hidden and a simplified message Loading... is displayed instead.

• Off — Detailed loading messages are displayed.

Default: Off

Edition: Professional and Enterprise

Specifies the path of the dashboard page that's displayed by default when users sign in to Oracle Analytics. For example, /shared/<folder>/_portal/<name>.

You can specify a single path for all users and multiple paths by user role, for example {"application role 1":"catalog dashboard path 1","application role 2":"catalog dashboard path 2","default":"catalog dashboard path 3"}.

This setting applies to all users, but users can override it after they've signed in.

You can enter a maximum of 5,000 characters in this field.

Edition: Enterprise only

Specifies if sub-requests to source databases are executed separately as standalone queries or executed together. By default, sub-requests are shipped separately which can improve performance if you execute complex reports with a large group of sub-requests, that is, you prefer to ship the sub-requests separately in multiple simplified queries rather than ship a large single complicated query all at once.

In Oracle BI Enterprise Edition, the default is set to NO. If you used Oracle BI Enterprise Edition and want to retain the previous default behavior, set this property to NO to continue executing database sub-requests together.

• Default — Database sub-requests are shipped separately. This is the same as the value YES.
• YES — Database sub-requests are shipped separately.
• NO — Database sub-requests are shipped together, all at once.

Default: Default

Edition: Professional and Enterprise

Applies to content migrated from Oracle BI Enterprise Edition.

After you migrate content from your Oracle BI Enterprise Edition environment to Oracle Analytics, you may experience different sorting behaviors in analyses.

For example, if you look at a migrated analysis in Polish, the upper case and lower case letters might sort based on the Oracle Analytics default locale, not the original Oracle BI Enterprise Edition locale. To preserve the Oracle BI Enterprise Edition sort behavior in Oracle Analytics, change this setting to Polish.

Edition: Professional and Enterprise

Applies to content migrated from Oracle BI Enterprise Edition.

After you migrate content from your Oracle BI Enterprise Edition environment to Oracle Analytics, you may see a different language in messages, dates, or currencies within analyses.

For example, if you look at a migrated analysis in Polish, the currencies or dates might display based on the Oracle Analytics default locale, not the original Oracle BI Enterprise Edition locale. To preserve the Oracle BI Enterprise Edition currencies and dates in Oracle Analytics, change this setting to Polish.

Edition: Professional and Enterprise

Determines whether action links that users add to analyses and dashboards can invoke any URL or only URLs that administrators specify in the safe domains list.

• On — Don't allow actions to invoke any URL that's not in the safe domain list.

• Off — Allow actions to invoke any URL, even if the URL isn't listed as a safe domain.

Default: On for a brand new service and Off for an existing service.

Apply Change Required : No

Edition: Enterprise only

Specifies whether to enforce strict recursive data type checking for comparisons between identical data types (for example, integer to integer) or non-compatible data types (for example, integer to short integer) on all data sources or with all datasets.

• On — Enforces strict recursive checking for identical or non-compatible data types on all data sources or datasets.

• Off — Relaxes strict recursive checking for date and time data types on all data sources or datasets. However, if there are too many data type inconsistencies, you may want to change the data types to be compatible or use constants of the correct data type when comparing a column to a value. For example, after you migrate content from Oracle BI Enterprise Edition to Oracle Analytics, you might start seeing this type of check error in your reports because eary versions of Oracle BI Enterprise Edition didn't enforce strict checks:

  [nQSError: 22024] A comparison is being carried out between non-compatible types <type1> and <type2>.

Default: On

Edition: Professional and Enterprise

Specifies whether cells that span rows and cells that span columns are repeated when exporting tables and pivot tables to Excel.

• On — If switched on, cells that span rows and cells that span columns are repeated, regardless of the Value Suppression setting in the Analysis editor.
• Off — If switched off, the Value Suppression setting in the Analysis editor is honored and cells that span rows and cells that span columns don't repeat when exporting tables and pivot tables to Excel.

Default: Off

Edition: Enterprise only

Specifies whether to sort NULL values before other values (On) or after (Off). Select the value that matches your database. If this setting doesn't match your database setting, then the database setting takes precedence.

• On — Sorts NULL values before other values.
• Off — Sorts NULL values after other values.

Default: Off

Edition: Professional and Enterprise

Specifies whether the automatic removal of trailing spaces from varchar columns is enabled (Off) or disabled (On). For example, when this property is enabled (Off), when a user starts entering values in a field, the filter dialog automatically trims any trailing spaces.

• On — Preserves trailing whitespaces in varchar columns. If you primarily use Oracle Database sources, you might want to keep the default Oracle Database behavior of preserving trailing whitespaces rather than removing them. When you toggle this property on, you avoid the overhead of trimming spaces, and this can improve performance.

  If you disable this property (set it to On) and you construct a filter such as PRODUCT_DESCRIPTION = 'My Product '), you must make sure the amount of trailing whitespace used exactly matches the varchar column value. If you don't, the filter won't correctly match the data values.

• Off — Trims trailing whitespaces in varchar columns when processing queries. This is the default for Oracle Analytics. For example, if a user enters the text 'My Product ', it trims it to 'My Product'.

Default: Off

Edition: Professional and Enterprise

Specifies the Oracle Analytics Cloud URL format that's used to share links to workbook visualizations in scheduled emails. If your organization set up a vanity URL for your system, enter the existing vanity URL that you want to use in the format: https://myvanity.com/ui/

Alternatively, leave the setting blank to use the standard URL format in emails. See Share Visualizations Using Workbook Email Schedules.

Edition: Professional and Enterprise