Fiori app changes not reflecting even after clearing Fiori and Gateway caches can be confusing and time-consuming to troubleshoot. This blog explains how the ICM HTTP Server Cache (SMICM) can silently serve stale SAPUI5 resources and why it plays a critical role in Fiori app updates. Through a real-world scenario, the blog highlights how HTTP-level caching impacts Fiori behavior and shares the exact steps required to resolve the issue.
Dynamic Cross-App Navigation in Fiori Elements: Navigate to Different Apps from the Same Column
In many Fiori Elements apps, a single column can contain different types of business objects — for example, a Reference Document field showing Purchase Orders, Contracts, or Sales Orders. Standard annotations only support static intent-based navigation, which means all rows navigate to the same app. In this blog, we show how to extend the Object Page with a controller extension, access the inner SmartToggle → Link, and enable dynamic cross-app navigation so each row opens the correct target app.
Extending Legacy SAP Fiori Apps: A Case Study with Clear Incoming Payments (F0773)
Extending modern SAP Fiori apps is usually straightforward with extension points. But when working with classical Fiori apps built on libraries, things get tricky. These apps often lack Component.js and extension points, making reuse and customization painful. This blog shares how to extend such legacy apps by replacing fragments and views.
Extension Projects in BAS: Handling Legacy SAP Fiori Apps
While Adaptation Projects are the recommended way to extend modern Fiori apps, some legacy apps built with synchronous views—like Clear Incoming Payments (F0773)—still require the classic Extension Project approach. This blog explains why, how BAS detects these apps, and step-by-step guidance to create extensions safely.
Refreshing Dynamic HTML Content in SAPUI5: Handling Updates and Rerendering Issues
Refreshing dynamic HTML content in SAPUI5 can be tricky, especially when using the HTML control to embed iframes or external content. Deprecated methods like rerender() often fail, leaving scripts unexecuted or DOM elements stale. A reliable solution is to toggle visibility before and after setContent(), forcing SAPUI5 to fully redraw the control. This approach ensures updated content loads correctly, with event handlers and scripts functioning as expected.