From Warehouse to Widget in One Afternoon — Practical Notes addresses a problem most SAP landscapes know too well: Spreadsheet culture returns when self-service lacks governance.
BI Objects, Models, Views, Flows, and Reports share one admin console — AI-assisted design, filter sharing, export, and cache refresh jobs included.
BI Portal combines SAP (iDataView/API), SQL Server, PostgreSQL, files, and Microsoft Fabric into widget-based pages with live/offline modes, publish flows, and role-based visibility.
Capabilities you use in iDataEngine
- BI Views: widgets, live/offline pages, publish
- BI Admin and folder assignment
- BI Objects: sources, columns, variants, cache jobs
- Data from SAP, SQL, Fabric on one page
- Filter share and public links with expiry
- BI Role Management: auth fields, role values
Recommended workflow
- Save and capture the generated URL, job ID, or snapshot reference in your change record.
- Run Test (iDataView Test, SQL First Row, API Test Service, or AG scan) before scheduling or publishing.
- Open the relevant cockpit (iDataView Explorer, SQL Project, API Service Detail, or AccessGuard).
- Extend the same definition to the next channel (API, SQL, MF, BI) without redesigning from scratch.
Real-world scenario (2026)
Regional managers see margin widgets filtered by plant — live SAP on Monday, cached Fabric for trend lines — one page, role-scoped.
Why it matters
Self-service fails when IT cannot enforce row-level rules. BI Portal delivers speed for business users and auth fields for compliance — the combination enterprises asked for.
Innovation here means business sees results faster — IT keeps control because every step is configured, tested, and monitored.