BI Portal: Self-Service Without Losing Control addresses a problem most SAP landscapes know too well: Spreadsheet culture returns when self-service lacks governance.
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.
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 Flows: node types and run history
- BI Admin and folder assignment
- Data from SAP, SQL, Fabric on one page
- Widget export Excel/image
- Filter share and public links with expiry
- AI-assisted view design
Recommended workflow
- Open the relevant cockpit (iDataView Explorer, SQL Project, API Service Detail, or AccessGuard).
- Run Test (iDataView Test, SQL First Row, API Test Service, or AG scan) before scheduling or publishing.
- Extend the same definition to the next channel (API, SQL, MF, BI) without redesigning from scratch.
- Enable monitoring alerts and review dashboard KPIs for the first production cycle.
Real-world scenario (2024)
After SQL Transfer loads customers nightly, BI Objects refresh cache and flows email a PDF snapshot to executives — self-service plus push.
Why it matters
Widget export and share links spread insight without spreading uncontrolled extracts.
That combination is why enterprises adopt iDataEngine as a lifecycle platform — not a one-off integration tool.