SAP BusinessObjects Design Studio
As of 2026-08-14T00:00:00Z
What is SAP BusinessObjects Design Studio?
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.
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.
How to scope it. Inventory applications, then classify by component usage: standard-only, standard plus configuration-heavy scripting, and custom SDK. Then ask who wrote the custom components, because the answer is frequently a partner engagement that ended years ago and left no source repository.
For consultants, Design Studio and Lumira Designer estates are a reliable source of migration work precisely because the residue is code — and code that nobody owns is the part a customer cannot assess without help.
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.
Common pitfalls
- Treating Design Studio and Lumira Designer as two subjects — Signal: Two workstreams in the plan, one estate on the ground Fix: Same artefacts, same SDK, different product name. Merge the workstreams.
- Assuming custom components have owners — Signal: "The partner will provide the source" Fix: Verify the repository exists before scoping the rebuild. Frequently it does not.
- Rebuilding every custom component — Signal: A one-to-one widget backlog Fix: Check each requirement against current SAC features first — some were workarounds for gaps that have since closed.
Decision framework
| Decision | Option A | Choose A when | Option B | Choose B when |
|---|---|---|---|---|
| What to do with a custom SDK component | Rebuild as a SAC custom widget | The requirement is still real and no standard SAC feature covers it | Drop it | It was a workaround for a gap the target has since closed — verify before rebuilding |
| How to sequence applications | Standard-component apps first | They convert with predictable effort and build migration confidence | Custom-SDK apps first | Only when one of them blocks a business process and the rebuild is on the critical path |