Concept card

SAP BusinessObjects Design Studio

As of 2026-09-27

Edited by Cédric-Olivier Mâry, sole editor and publication director — 27 years in the SAP ecosystem. How these pages are produced, and where automation is used.

What is SAP BusinessObjects Design Studio?

The BI application design tool that let developers script and extend dashboards with custom SDK components. Renamed into Lumira Designer, and succeeded by SAC Analytic Applications — but the custom components are what does not travel.

What it is

Design Studio was SAP's answer to a specific frustration: dashboards that could not be programmed. Where earlier tools offered configuration, Design Studio offered a scripting language, an event model, and — decisively — an SDK through which developers could write their own components. That opened the door to a genuine ecosystem: custom charts, navigation panels, input controls and integrations that no product roadmap had anticipated, built by partners and by customers' own developers.

The naming history matters for anyone reading old material. Design Studio was folded into the Lumira brand and continued as Lumira Designer; the same artefacts, the same SDK, a different product name. A large body of community documentation still says "Design Studio" while the installed software says "Lumira Designer", and treating those as two separate migration subjects is a common and expensive mistake.

The SDK is both the reason it was adopted and the reason it is hard to leave. A Design Studio application that only uses standard components has a reasonably direct expression as an SAC Analytic Application: the paradigm of a scripted, event-driven analytic app carried across. An application built on custom SDK components does not, because those components are code written against a runtime that the target does not provide. They are rebuilt — in SAC as custom widgets where the requirement still holds, or dropped where the requirement turns out to have been a workaround for a gap the target has since closed.

Why it matters

Custom SDK components are code written against a runtime the target does not provide. They are rebuilds, and their authors are frequently a partner engagement that ended years ago.

Key points

The BI application design tool: scripting language, event model, and an SDK for custom components.
🔴 Design Studio and Lumira Designer are the same subject under two names — the written record and the installed software disagree.
Standard-component applications carry across to SAC Analytic Applications reasonably directly.
Custom SDK components do not: they are rebuilt as SAC custom widgets, or dropped when the requirement was a workaround.
Scope by component usage — standard · script-heavy · custom SDK — and ask who wrote the custom ones.
The decision is per application: carry across on standard components, rebuild with custom widgets, or retire.
Before paying to rebuild an SDK component, establish what it was working around — the target may cover it with a standard feature today.

Terms used on this page

SDK component: A custom Design Studio / Lumira Designer component written by a partner or customer against the product's extension SDK.
Analytic Application: The SAC artefact that plays the scripted, event-driven role Design Studio applications played.
Custom widget: The SAC extension mechanism through which a rebuilt SDK component is expressed.
Scripting: The Design Studio event-driven language that made applications programmable rather than merely configurable.
Event model: The Design Studio mechanism binding script to user actions (on click, on select, on startup). It is the part of an application that has no configuration equivalent and therefore has to be re-authored.
Application catalogue: The inventory of Design Studio applications with their components and owners. It is the artefact that makes a rebuild estimable, and it rarely exists before someone asks for it.

Sources

Full card available to members. What the full card adds: the full decision framework · the SAP vs Snowflake / Databricks / Fabric comparison · the common pitfalls and their fix · the cheat sheet · the architecture schemas · the code blocks · the facts worth quoting.

Open in the app →