SAP C_FIORD_2502 Dumps Questions Answers

SAPUI5 supports differentbinding types:

Property binding: binds individual attributes (e.g., text="{/name}").

Aggregation binding: binds lists or tables (e.g., items="{/products}").

Element binding: binds a control and its children to a specific path (bindElement("/product")).

SAPUI5 Developer Guide:

“Supported binding types include Property, Aggregation, and Element binding.”

Structure/Combination are not valid SAPUI5 binding categories.

SAP offersmultiple extension mechanisms:

Adaptation Project: customizes standard apps without copying code.

View Extensions: via manifest.json to inject custom UI at extension points.

Controller Hooks and Property Overridesfor fine-grained control.

SAP Fiori Extensibility Guide:

“Adaptation projects allow for UI and logic customization using SAP Business Application Studio.”

Changing runtime libraries or merging data at runtime are neither recommended nor supported directly.

Responsive tables(sap.m.Table) in SAPUI5 use demandPopin, popinDisplay, and screen width qualifiers to optimize mobile display. Correct settings include:

maxScreenWidth="mobile"ensures pop-in on small devices.

demandPopin="true"triggers field reformatting into pop-ins.

popinDisplay="Inline"keeps visual alignment.

SAPUI5 SDK – Responsive Table Control:

“Use demandPopin with maxScreenWidth and popinDisplay to handle narrow screen layouts.”

Options with minScreenWidth do not apply to mobile-focused pop-in logic.