|
-`longtextURL`\*
+`longtextUrl`\*
+
+`@Common.longtextUrl`\*
|
-`descriptionURL`
+`descriptionUrl`
|
@@ -270,6 +272,8 @@ There are three different channels for transporting messages to the client:
Only transition messages are transported in the error response. The messages may be bound or unbound. Error messages are always reported in the error response in JSON format, as described in the OData JSON Format Version 4.0 in Section *19 Error Response*, with the following additions:
+- If more than one message should be returned, the outer message needs to be any of the error messages. All other messages are provided as detail messages. All messages, both the outer and the detail messages, are reported to the message model.
+
- The instance annotation `com.sap.vocabularies.Common.v1.longtextUrl` can be used to provide a long text URL, which can be a relative or an absolute path. Relative paths are treated as relative to the request URL. Absolute paths are treated as relative to the server.
- `target` is relative to the requested resource.
diff --git a/docs/04_Essentials/setting-themes-e9fc648.md b/docs/04_Essentials/setting-themes-e9fc648.md
index eecaf7ad..1e202141 100644
--- a/docs/04_Essentials/setting-themes-e9fc648.md
+++ b/docs/04_Essentials/setting-themes-e9fc648.md
@@ -25,7 +25,7 @@ You define which theme is used by your app either by using the `theme` configura
> http://myserver.com/sap/myapp/?sap-ui-theme=my_custom_theme@/sap/public/bc/themes/~client-111
> ```
>
- > Although a full URL can be specified, the framework will only use the path information of the URL to prevent CSS-based attacks that would otherwise be possible by referencing CSS from a malicious server, unless the origin has been added to `sap-allowed-theme-origin`. For more information, see [Theme Origin Allowlist](setting-themes-e9fc648.md#loioe9fc648661d84ed89360bbec3ae02611__section_TOA). In a more complex landscape, for example, if the infrastructure of the UI theme designer is running on a separate server, a Web dispatcher can be used to combine both servers in one endpoint.
+ > Although a full URL can be specified, the framework will only use the path information of the URL to prevent CSS-based attacks that would otherwise be possible by referencing CSS from a malicious server, unless the origin has been added to `sap-allowed-theme-origins`. For more information, see [Theme Origin Allowlist](setting-themes-e9fc648.md#loioe9fc648661d84ed89360bbec3ae02611__section_TOA). In a more complex landscape, for example, if the infrastructure of the UI theme designer is running on a separate server, a Web dispatcher can be used to combine both servers in one endpoint.
> ### Note:
> The UI theme designer infrastructure stores themes for multiple technologies in the same location, each in its own subdirectory \(`UI5/` for SAPUI5\). Other SAP products \(such as SAP Enterprise Portal\) append only the common root URL to the `theme` parameter. SAPUI5 therefore appends folder `UI5/` to any given path that is defined in the `theme` parameter.
@@ -83,7 +83,7 @@ To load an external custom theme, you can either declare it statically on the pa
When configuring a theme with a `themeRoot` URL via the `theme` parameter, security restrictions apply. Absolute URLs to an origin other than the current page are cut off by default. The path segment will be resolved relative to the current page origin.
-In order to allow other origins to be used via the URL parameter, the `sap-allowed-theme-origin` configuration option can be used:
+In order to allow other origins to be used via the URL parameter, the `sap-allowed-theme-origins` configuration option can be used:
``
diff --git a/docs/04_Essentials/spreadsheet-export-2691788.md b/docs/04_Essentials/spreadsheet-export-2691788.md
index c7a1dcd3..ac4e7971 100644
--- a/docs/04_Essentials/spreadsheet-export-2691788.md
+++ b/docs/04_Essentials/spreadsheet-export-2691788.md
@@ -15,7 +15,10 @@ The spreadsheet export allows you to export your data to an Office Open XML docu
If you use the `SmartTable` control to export data, you can also use different types of exports, the client export or the SAP Gateway export.
> ### Tip:
-> The `SmartTable` control offers you all the preconfigured content you need for the export. You can either simply use it without having to define any configuration yourself, or you can adapt the content to make it fit your own specific requirements. For other entitities, you have to define the configuration manually as described below.
+> The `sap.ui.comp.smarttable.SmartTable` and `sap.ui.mdc.Table` controls offer you all the preconfigured content you need for the export. You can either simply use it without having to define any configuration yourself, or you can adapt the content to make it fit your own specific requirements. For other entitities, you have to define the configuration manually as described below.
+
+> ### Tip:
+> If the export takes more than 5 minutes, we recommend to cancel the process and apply additional filter settings to reduce the amount of data that has to be exported.
@@ -23,7 +26,7 @@ If you use the `SmartTable` control to export data, you can also use different t
## Prerequisites
-If you want to export data manually, without `SmartTable`, you have to perform the following steps:
+If you want to export data manually, without `SmartTable` or `Table` \(`sap.ui.mdc`\), you have to perform the following steps:
1. Load the `sap.ui.export.Spreadsheet` library within your controller coding.
@@ -133,7 +136,7 @@ The following data types are supported:
> ### Note:
-> Currency values and numbers that cannot be represented in the standard format as defined by the *IEEE \(Institute of Electrical and Electronics Engineers\)* in the spreadsheet file because they are too large automatically use the `BigNumber` data type as a fallback option. The number is then stored as `string` and represented using the international format with a comma as a thousands separator and a period for the decimal point.
+> Currency values and numbers that cannot be represented in the standard format as defined by the *IEEE \(Institute of Electrical and Electronics Engineers\)* in the spreadsheet file because they are too large automatically use the `BigNumber` data type as a fallback option \(standard IEEE 754\). The number is then stored as `string` and represented using the international format with a comma as a thousands separator and a period for the decimal point.
For more information, see [Data Types for Spreadsheet Export](data-types-for-spreadsheet-export-283217d.md).
@@ -141,7 +144,7 @@ For more information, see [Data Types for Spreadsheet Export](data-types-for-spr
### Additional Settings on Export User Interface
-In addition to the regular `Export` dialog, the user can use the `Export As` dialog in the `SmartTable` control, which can be selected from a dropdown list next to the *Export to Spreadsheet* button, to define additional settings for the export.
+In addition to the regular `Export` dialog, the user can use the `Export As` dialog in the `SmartTable` or `Table` \(`sap.ui.mdc`\) control, which can be selected from a dropdown list next to the *Export Table* button, to define additional settings for the export.
The user can define the following for the exported file:
@@ -151,13 +154,13 @@ The user can define the following for the exported file:
The file format has been predefined.
-- Whether to show cells with more than one value in separate columns
+- Whether to show cells with more than one value in separate columns \(*Split cells with multiple values*\)
- This option is used for columns based on text arrangements, currencies, and units of measure. For example, if both the name and the ID of a customer are displayed in one column, the exported file will show the customer data in two separate columns. This might result in duplicate columns if the file already contains columns with the same header name.
+ This option is used for columns that are based on text arrangements, currencies, and units of measure. For example, if both the name and the ID of a customer are displayed in one column, the exported file will show the customer data in two separate columns. This might result in duplicate columns if the file already contains columns with the same header name.
- Whether to show any available filter settings
- If this option is selected, the exported file has an additional *Filter* sheet showing the filters that were set on the columns as well as in the `FilterBar` control. The filters shown in the exported file currently contain the technical property that has been extracted from the binding.
+ If this option is selected, the exported file has an additional *Filter* sheet showing the filters that were set on the columns as well as in the `FilterBar` control. The filters shown in the exported file are the column labels. They are shown by default. If there is no column label, the property name is shown.
The `beforeExport` event also provides the additional export settings defined by the user \(`userExportSettings` parameter\). This parameter is always available and contains the settings currently valid for the export, so the application developers can decide which settings to use.
@@ -174,5 +177,5 @@ The `beforeExport` event also provides the additional export settings defined by
[API Reference: `sap.ui.export.EdmType`](https://ui5.sap.com/#/api/sap.ui.export.EdmType)
-[Export Features](export-features-e7f52f4.md "The SmartTable control offers various types of exports. The SmartTable control supports features such as file compression, header row, localization, meta information, hierarchies, data types, and Read Access Logging (RAL) support.")
+[Spreadsheet Export Type Features](spreadsheet-export-type-features-e7f52f4.md "The SmartTable control offers different types of exports with various features.")
diff --git a/docs/04_Essentials/spreadsheet-export-configuration-7e12e6b.md b/docs/04_Essentials/spreadsheet-export-configuration-7e12e6b.md
index 3f236aad..dd918bd9 100644
--- a/docs/04_Essentials/spreadsheet-export-configuration-7e12e6b.md
+++ b/docs/04_Essentials/spreadsheet-export-configuration-7e12e6b.md
@@ -2,7 +2,7 @@
# Spreadsheet Export Configuration
-To perform a spreadsheet export for any content other than `SmartTable`, you have to set up the configuration for the columns and data sources, and you can configure some other additional properties.
+To perform a spreadsheet export for any content other than `SmartTable` or `sap.ui.mdc.Table`, you have to set up the configuration for the columns and data sources, and you can configure some other additional properties.
@@ -269,7 +269,7 @@ The `label` property is optional, and its value must be of type `string`. Its va
The optional `type` property defines the data type for this column and needs to match one of the values of the `sap.ui.export.EdmType` enumeration. If the `type` property has not been defined or the enumeration does not contain its value, the default type \(`sap.ui.export.EdmType.String`\) is used. For more information, see the [API Reference: `EdmType`](https://ui5.sap.com/#/api/sap.ui.export.EdmType).
-The optional `width` property defines the column width based on the number of characters that can be visible. The Office Open XML spreadsheet standard uses a width calculation that is not equivalent to the CSS sizes. Therefore, the calculation is handled by the library. If no `width` property has been provided, or if its value is greater than *1*, the default width is used. The default width is 10 characters. If the column header text has a length that is greater than the actual width, it will override the width with the length of the column header text.
+The optional `width` property defines the column width based on the number of characters that can be visible. The Office Open XML spreadsheet standard uses a width calculation that is not equivalent to the CSS sizes. Therefore, the calculation is handled by the library. If no `width` property has been provided, or if its value is smaller than *1*, the default width is used. The default width is 10 characters. If the column header text has a length that is greater than the actual width, it will override the width with the length of the column header text.
The optional `textAlign` property defines the horizontal text alignment. Its value must be of type `string` and either be `left`, `right`, or `center`. Other CSS alignments like `begin` or `end` are not supported. If no `textAlign` property has been provided or its value is empty or not supported, the default alignment is used. The default alignment is defined by the type of the column. This is done by the application using the scenario and the generated Office Open XML spreadsheet, for example, Microsoft Excel.
@@ -317,7 +317,7 @@ var exportConfiguration = {
### Data Source Configuration
-Apart from the column configuration, data source configuration is the most important configuration for the export process. Data source configuration is mandatory. It can be a JSON array containing all data, a JSON object, `sap.ui.model.ListBinding`, or `sap.ui.model.TreeBinding` with the following properties:
+Apart from the column configuration, data source configuration is the most important configuration for the export process. Data source configuration is mandatory. It can be a JSON array containing all data, a JSON object, `sap.ui.model.ListBinding`, or `sap.ui.model.TreeBinding`. If it is a JSON object, the following properties are required:
**Data Source Configuration Properties**
@@ -407,7 +407,7 @@ Request URL that is needed to request the data with all the filters and its orde
|
-URL of the data service that serves the entity which is requested by the `dataUrl`". It is usually a substring of `dataUrl`. The URL can either be relative or absolute. If `dataUrl` is relative, `serviceUrl` must not be absolute.
+URL of the data service that serves the entity which is requested by the `dataUrl`. It is usually a substring of `dataUrl`. The URL can either be relative or absolute. If `dataUrl` is relative, `serviceUrl` must not be absolute.
> ### Note:
> This property is required if OData batch requests are enabled.
@@ -655,6 +655,11 @@ We recommend to use this property because there are often several similar apps t
Identifies the application version through which a particular Office Open XML spreadsheet was created. This can be helpful for debugging because you can identify the version that caused the issues and compare it to previous builds. The more detailed your version information is, the easier it will be to identify your application changes within your source code management system.
+> ### Note:
+> You can only include the major and minor version in the version information. If you use more than one period as a separator, this can cause corrupt spreadsheet files in some system locales, which is also checked by the validation.
+
+
+
|