SAPUI5 Smart Controls (SmartFilterBar, SmartList)
Smart Controls are UI5 controls that use OData metadata to dynamically configure themselves, reducing the amount of manual UI coding a developer must write. A developer uses them to automatically generate UI elements — such as table columns or form fields — based on the metadata exposed by an OData service, as demonstrated in the Smart Controls Tutorial. They also support create operations against OData services, enabling developers to build data-entry scenarios with minimal boilerplate configuration.
Tutorials that teach this
Docs explaining this concept
Prerequisites
- Concept OData Service Exposure via CAP The concept name provided is "undefined," which does not correspond to a recognizable SAP developer concept that can be grounded in the supplied source snippets. No definition can be responsibly written without a valid concept name and supporting source material.
- Concept SAPUI5 Application Development The concept name was not provided, so a precise definition cannot be produced from the available sources. The sources cover general SAPUI5 development topics — such as [developing SAPUI5 apps](https://ui5.sap.com/#/topic/3da5f4be63264db99f2e5b04c5e853db), tutorials, and UI development on SAP BTP — but do not supply enough detail to define an unnamed concept accurately. Please supply the concept name so a grounded definition can be written.
- Concept UI5 App Descriptor (manifest.json) The concept name was not provided (marked as "undefined"), and the supplied source snippets cover several distinct SAPUI5 topics — CORS, `resources.json`, the Component Controller, manifest model preload, and others — without a single shared concept that can be reliably identified and defined. A meaningful, source-grounded definition cannot be written without knowing which concept to define.
- Concept OData service consumption The provided sources do not contain sufficient information to write a grounded definition for an undefined concept. Please provide a valid concept name and relevant source snippets to generate an accurate definition.
- Concept UI5 Model Data Binding The concept name provided is "undefined," which does not correspond to a defined SAP developer concept. Based on the available sources, no coherent or supported definition can be constructed for a concept literally named "undefined." Please provide a valid concept name so that an accurate, source-grounded definition can be written.
- Concept OData V2 Protocol The concept provided is `undefined`, and the supplied sources cover the [OData V4 Tutorial](https://ui5.sap.com/#/topic/bcdbde6911bd4fc68fd435cf8e306ed0) and the Fiori Reuse Library for Change Document Solution — neither of which defines a concept named `undefined`. There is insufficient information in the provided sources to write a grounded reference definition for this concept.
- Concept OData V2 Service Integration The concept name is missing or undefined, so a precise definition cannot be produced from the provided sources. Based on the available source snippets — which cover topics such as consuming OData services, SAP Cloud Integration, SAPUI5 user interfaces, and SAP Business Accelerator Hub APIs — the concept appears to relate to **OData service consumption** in SAP development contexts. Developers use OData services to read and write structured business data (such as sales orders or product listings) from SAP and third-party backends, as demonstrated in tutorials like [consuming an OData service with create option](https://developers.sap.com) and [using OData metadata to dynamically create UI columns](https://developers.sap.com). Please provide the specific concept name for a more accurate definition.
- Concept SAPUI5 Data Binding The concept name provided is "undefined," which does not correspond to a valid or identifiable SAP developer concept based on the supplied sources. The sources cover topics such as [data binding in SAPUI5](https://ui5.sap.com/#/topic/e5310932a71f42daa41f3a6143efca9c) and [models in the Model View Controller pattern](https://ui5.sap.com/#/topic/e1b625940c104b558e52f47afe5ddb4f), but none of them define or describe a concept called "undefined." A valid concept name is required to produce an accurate and source-grounded reference definition.
- Concept SAPUI5 MVC Architecture The concept name provided is "undefined," which does not correspond to a defined SAP developer concept. Based on the available sources, a **Model** in SAPUI5 is a core component of the Model View Controller (MVC) pattern that holds data and provides methods to retrieve and modify it, while a [Controller](https://ui5.sap.com/#/topic/121b8e6337d147af9819129e428f1f75) contains methods that define how [models](https://ui5.sap.com/#/topic/e1b625940c104b558e52f47afe5ddb4f) and views interact. If you intended to define one of these concepts, please clarify the concept name so an accurate definition can be provided.
- Concept XML View in MVC An XML View is a declarative UI definition file used in the SAP UI5 Model-View-Controller (MVC) pattern, where developers describe the structure and layout of a page using XML markup. Developers use it to define UI controls and their properties — such as tiles, timelines, and detail page content — in a readable, structured format that is separate from application logic. For example, XML Views are used to compose pages with controls like `GenericTile` in line mode or timeline components, as shown in the [UI5 walkthrough tutorials](https://ui5.sap.com/#/topic/10fa7fd7f0d54f6384b3b31c65ac78f5).
- Concept SAP Build Work Zone configuration The provided sources do not contain enough information to define this concept, as the concept name is listed as "undefined" and the source snippets do not converge on a single, clearly identifiable SAP developer concept. Please provide a valid concept name or additional source content to generate an accurate definition.