SAP Fiori · Creating & Extending Fact Sheet Apps

In a modification-free fact sheet project, which file do you edit for your design changes — and why must you NOT touch Original.xsl?

Answer locked. Get the free KnowCard app to reveal it — plus spaced-repetition review so it actually sticks.

This is one card from the KnowCard library — thousands more across SAP, Linux, Python and more. In the app you get the answer, AI explanations, and cards that come back right before you would forget them. Free to start on iOS, Android or the web.

More in Creating & Extending Fact Sheet Apps

You hand a fact sheet extension to a functional consultant who can't write code. Which editor, and will they be limited to a subset of fields?

You need an embedded map the fact sheet editor can't add. You can edit the delivered annotation file directly or write an XSLT alongside the untouched original. Which survives an SAP upgrade, and why?

A Fiori UI developer offers to extend a fact sheet's search model in the search and analytics modeler. Why is that the wrong person for the job?

A user reports a fact sheet field is invisible on their phone but their colleague sees it on a desktop. Before touching the model, what Field Priority value explains this?

You're adding a Risk Category attribute to a search model. What's the easy-to-skip first step before Request Attributes, and what does the system auto-generate afterward?

In a standard fact sheet extension project, which of the three files do you actually edit for the extension, and which one only configures preview?

Start learning today

Free to start — download the app or use it in your browser.