smarttable/SmartTable SAP SE The SmartTable control creates a table based on OData metadata and the configuration specified. The entitySet attribute must be specified to use the control. This attribute is used to fetch fields from OData metadata, from which columns will be generated; it can also be used to fetch the actual table data. Based on the tableType property, this control will render a standard, analytical, tree, or responsive table. Note: Most of the attributes/properties are not dynamic and cannot be changed once the control has been initialized. sap.m/VBox The entity set name from which to fetch data and generate the columns. Note that this is not a dynamic UI5 property ID of the corresponding SmartFilter control; When specified, the SmartTable searches for the SmartFilter (also in the closest parent View) and attaches to the relevant events of the SmartFilter; to fetch data, show overlay etc. CSV of fields that must be ignored in the OData metadata by the SmartTable control. Note: No validation is done. Please ensure that you do not add spaces or special characters. CSV of fields that must be shown initially in the SmartTable as visible columns and in the order specified. This property is mainly meant to be used when no LineItem annotation exists. If you have fields in the XMLView they are always shown first; then, the columns are added based on the LineItem annotation and finally based on this property. Note: If both this property and the LineItem annotation exist, the order of fields cannot be guaranteed to be as mentioned here. No validation is done. Please ensure that you do not add spaces or special characters. CSV of fields that must be always requested from the backend This property is mainly meant to be used when there is no PresentationVariant annotation. If both this property and the PresentationVariant annotation exist, the select request sent to the backend would be a combination of both. Note: For <code>AnalyticalTable</code> (supported since 1.54), the following restrictions apply: <ul> <li>The property name(s) must not point to a new dimension or a measure.</li> <li>The property name(s) must not point to a navigationProperty/association path, as this might not supported by analytical services.</li> </ul> No validation is done. Please ensure that you do not add spaces or special characters. CSV of fields that is not shown in the personalization dialog. Note: No validation is done. Please ensure that you do not add spaces or special characters. Specifies the type of table to be created in the SmartTable control. Note: If you add a table to the content of the SmartTable in the view, this property has no effect. The useVariantManagement attribute can be set to true or false depending on whether you want to use variants. As a prerequisite you need to specify the persistencyKey property. The showVariantManagement attribute can be set to true or false for controlling the visibility of VariantManagement button. Can be set to true or false depending on whether you want to export data to a spreadsheet application, for example Microsoft Excel. Note: If <code>exportType</code> is <code>sap.ui.comp.smarttable.ExportType.GW</code>, any $expand parameters are removed when sending the request to generate the spreadsheet. As of UI5 version 1.56: If <code>exportType</code> is <code>sap.ui.comp.smarttable.ExportType.UI5Client</code> and <code>TreeTable</code> is used, the <code>worksheet.hierarchyLevel</code> property (see {@link sap.ui.export.Spreadsheet}) is filled from the binding, if the relevant information is available there for exporting hierarchical data in the spreadsheet. Specifies the type of export to be used in the <code>SmartTable</code> control. The useTablePersonalisation attribute can be set to true or false depending on whether you want to define personalized table settings. If you want to persist the table personalization, you need to specify the persistencyKey property. The showTablePersonalisation attribute can be set to true or false for controlling the visibility of the TablePersonalisation button. If set to <code>true</code> (default), the number of rows is shown along with the header text. If set to <code>false</code>, the number of rows will not be shown on the user interface. Note: To avoid sending dedicated OData requests in order to improve your application's performance, you must configure the binding of the table as required. Specifies header text that is shown in table A style class which is defined for the toolbar of the table. Can be used to override the filter behavior. If set to true (default), instead of the filter input box a button is rendered. When pressing this button, the SmartTable control opens the filter panel directly in the table personalization dialog. After personalization dialog has been introduced in SmartTable the property <code>enableCustomFilter</code> does not make sense. When setting the property to <code>false</code>, the entered custom filter value will not be shown in personalization dialog and will also not be persisted in variant management. The custom filter will also be overwritten when rebindTable is called on the SmartTable. Key used to access personalization data. If set to true, the standard toolbar and custom toolbar will be merged into one toolbar. The combined toolbar will have a solid style. This property has no effect Specifies whether the <code>Toolbar</code> control of the <code>SmartTable</code> is placed inside the corresponding aggregation of the inner UI5 table control. Retrieves or sets the current variant. This attribute can be used to specify if the controls created by the SmartTable control are editable. (The automatic toggle of controls works only for the SmartField/SmartToggle scenario) When set to true, this enables automatic binding of the table using the tableBindingPath (if it exists) or entitySet property. This happens just after the <code>initialise</code> event has been fired. This attribute can be used to specify the path that is used during the binding of the table. If not specified, the entitySet attribute is used instead. (used only if binding is established internally/automatically - See enableAutoBinding) Specifies whether the editable property can be toggled via a button on the toolbar. (The automatic toggle of controls works only for the SmartField/SmartToggle scenario) The demandPopin attribute can be set to true or false depending on whether you want to display columns as popins on the responsive table Controls the visibility of the FullScreen button. The text shown initially before the control is bound and initialized. The special values <code>$FILTERBAR</code> or <code>$NO_FILTERBAR</code> can be specified to make the <code>SmartTable</code> control show the initial text as if the <code>SmartFilterBar</code> control were associated with it. If nothing is specified, the default behavior is to show the initial text based on whether the <code>SmartFilterBar</code> control is actually associated with the <code>SmartTable</code> control. Shows an info toolbar. Filters that are applied using the table personalization dialog are shown in the info toolbar. Note: <ul> <li>The default value for the property is <code>Auto</code>, which means that the info toolbar is shown by default if table type is <code>ResponsiveTable</code>.</li> <li>The info toolbar is hidden if the property is set to <code>Off</code>.</li> <li>The info toolbar is visible if the property is set to <code>On</code>. Currently the info toolbar is only available for the table type <code>ResponsiveTable</code>.</li> <li>If multiple filters are applied to the same column, then the info toolbar contains the column name only once.</li> <li>In case there is a custom info toolbar used for the responsive table control, then the property must be set to <code>Off</code>. Otherwise, an error is logged in the browser console.</li> </ul> This event is fired once the control has been initialized. This event is fired just before the binding is being done. This event is fired when display/edit button is clicked. This event is fired when data is requested after binding. The event is fired if the binding for the table is done by the SmartTable itself. Use <code>beforeRebindTable</code> event to attach/listen to the binding "events" directly This event is fired when data is received after binding. The event is fired if the binding for the table is done by the SmartTable itself. Use <code>beforeRebindTable</code> event to attach/listen to the binding "events" directly This event is fired after variant management in the SmartTable has been initialized. This event is fired after a variant has been saved. This event can be used to retrieve the ID of the saved variant. ID of the currently selected variant This event is fired after a variant has been applied. ID of the currently selected variant This event is fired just before the overlay is being shown. This event is fired when an editable field, created internally by the SmartTable control, is changed. This event is fired right after the full screen mode of the SmartTable control has been changed. If <code>true</code>, control is in full screen mode This event is fired just before export is triggered. Contains workbook.columns, dataSource and other export-related information Contains the export settings defined by the user This event is fired just before the paste event is triggered and can be used to prevent the default paste behavior. This API is experimental and subject to change Contains array of column info object as determined by the SmartTable This event is fired when paste is triggered. This API is experimental and subject to change Contains parsed/validated paste information returned by PasteHelper.parse API A toolbar that can be added by the user to define their own custom buttons, icons, etc. If this is specified, the SmartTable control does not create an additional toolbar, but makes use of this one. Note: The CSS class sapMTBHeader-CTX is applied on the given toolbar. The Semantic Object Controller allows the user to specify and overwrite functionality for semantic object navigation. The value for the noData aggregation can be either a string value or a control instance. The control is shown, in case there is no data for the Table available. In case of a string value this will simply replace the no data text. Currently the Responsive Table only supports string values. Allows users to specify an additional control that will be added to a VBox for the first semantic key field. Note: This property is not meant for public use. Identifies the SmartVariant control which should be used for the personalization. Will be ignored if the advanced mode is set.