fiori-table-maintenance

The CAP service and freestyle UI5 app behind Simple Table Maintenance in SAP Fiori Using UI5 Smart ControlsSimple Table Maintenance in SAP Fiori Using UI5 Smart ControlsblogStarts from SM30 and the table maintenance dialog it generated with almost no code, then asks what the equivalent is now. That framing is the value: a maintenance screen for a custom table was a solved problem in SAP GUI and is not an obviously solved one on Fiori, and the post works through what smart controls give you towards it.published 2025-02-11, where a SmartTable edits rows in place rather than through a draft.

SM30 generated a maintenance screen for a custom table with almost no code, and this works out what the same screen costs on Fiori, where nothing generates it. Two CDS entities, StarWarsFighter and FighterStatus, are served as OData V2 through @cap-js-community/odata-v2-adapter@cap-js-community/odata-v2-adaptercds-pluginExposes a CAP service as OData V2 for clients that cannot move to V4.community org, cap, and one XML view puts a SmartFilterBar and a SmartTable over them with editable and editTogglable set, variant management and export. The columns and the read-only fields are Fiori annotationsFiori annotationscapabilityDescribing a service so a Fiori client can render it without hand-written UI code — titles, value helps, hierarchies and visibility expressed as model annotations rather than screen logic.SAP and community, unassessed in app/annotations.cds, so the controller holds little more than onFieldChange calling model.submitChanges() as a field is left. It stops at one table and one app: the view names its entity set, the annotations name its fields, and a second table means writing both again.

Who is behind it

Marian ZeisMarian ZeisPersonMaintains this
In the atlas: maintains 35, contributes to 86, wrote 25@marianfoomaintainer