smartfilterbar/SmartFilterBar SAP The SmartFilterBar control uses the OData metadata of an entity in order to create a FilterBar. Whether a field is visible on the FilterBar, supports type-ahead and value help, for example, is automatically determined. When you use control configurations and group configurations it is possible to configure the FilterBar and adapt it according to your needs. Note: Most of the attributes/properties are not dynamic and cannot be changed once the control has been initialized. sap.ui.comp/filterbar/FilterBar The OData entity type whose metadata is used to create the SmartFilterBar. Note: Changing this value after the SmartFilterBar is initialized (<code>initialise</code> event was fired) has no effect. Use <code>entitySet</code> property instead of this one, to enable V4 annotation support The OData entity set whose metadata is used to create the SmartFilterBar. Note: Changing this value after the SmartFilterBar is initialized (<code>initialise</code> event was fired) has no effect. Optional. The OData service URL. If it is not specified, the service URL from the OData model (this.getModel()) will be used. Note: Changing this value after the SmartFilterBar is initialized (initialise event was fired) has no effect. Set an ODataModel as the main model on your control/view instead Name of the field that is the focus of the basic search. Enables the basic search field. The entered value can be accessed with {@link sap.ui.comp.smartfilterbar.SmartFilterBar#getParameters}. Note: When the SmartFilterBar control is used with a {@link sap.ui.comp.smarttable.SmartTable} control the parameters are handled automatically. Therefore, this must only be enabled for OData service entities that support basic search. If set the search will be automatically triggered, when a filter value was set via the change event. Note: The liveMode only operates on non-mobile scenarios. Additionally, if liveMode is set, the following applies: <ul> <li>The error messagebox is not displayed, and the <code>showMessages</code> property is ignored.</li> <li>The search is triggered after a variant has been selected.</li> <li>Execute on Select for <code>VariantManagement</code> is not shown and not taken into account</li> </ul> If set to <code>false</code> eventual errors during the search, will not be displayed in a messagebox. Indicates if the analytical parameters (SelectionVariant) must be taken into consideration. This property is NOT stable yet. Use at your own risk. If set to <code>true</code> all date fields with filter restriction <code>interval</code> will be treated as <code>DateTimeRange</code> filters. The <code>useDateRangeType</code> can be set only once during initialization. Note: If this property is set to <code>true</code> and any date filters with filter restriction <code>interval</code> were stored as part of a variant, the values of these filters cannot be applied. If this property is set to <code>false</code>, any previously stored filters which were treated as type <code>DateTimeRange</code> based on the former setting, cannot be converted back to the standard date interval. If set to <code>true</code> all search requests will be ignored. This functionality is only intended to be used internally to enable an optimal solution when the filter bar is controlled by the smart templates. NOTE: As long as this property is set to <code>true</code>, all search requests will be neglected. This property is NOT stable yet. Use at your own risk. Indicates if the annotation <code>com.sap.vocabularies.UI.v1.SelectionVariant</code> is taken into account. Determines one specific variant that is based on the <code>com.sap.vocabularies.UI.v1.SelectionVariant</code> annotation, which is then used as the default variant. This property is only relevant in case <code>considerSelectionVariants</code> is set to <code>true</code> and will only be applied if there is no user-defined default variant specified. If set to <code>true</code>, only the navigation properties mentioned in property {@link sap.ui.comp.smartfilterbar.SmartFilterBarl#getNavigationProperties} are checked for further filters. This property is only evaluated if the property {@link sap.ui.comp.smartfilterbar.SmartFilterBar#getUseProvidedNavigationProperties} is set to <code>true</code>. It contains a comma-separated list of navigation property names which are checked for filters. This event is fired after the pending state of the <code>FilterBar</code> control changes. Using control configurations you can add additional configuration to filter fields, for example set custom labels, change the order of fields, or change the filter field control type. Note: Changing the values here after the SmartFilter is initialized (<code>initialise</code> event was fired) has no effect. Provides the possibility to add additional configuration to groups. Groups are used to show fields in the advanced area of the SmartFilterBar. With additional configuration, you can for example set custom labels or change the order of groups. Note: Changing the values here after the SmartFilter is initialized (<code>initialise</code> event was fired) has no effect. Identifies the SmartVariant control which should be used for the personalization. Applies the current variant as opposed to <code>fetchVariant</code>. The variant is retrieved via the flex layer. The variant that must be applied. oVariant must contain a valid JSON object. Retrieves the currently visible filters and the values for storing them as variants. The result will be passed on as a JSON object to the callee smart variant control.