1. Compatibility preflight
Required source structures are checked before deployment so unsupported or missing dependencies can be identified early.
A governed reporting layer, source compatibility checks and school-focused Power BI pages turn operational Ed-admin data into management insight.
Ed-admin contains the operational data schools use every day. DataSolv Education Analytics adds a separate reporting layer designed for Power BI, so management reporting can use governed business definitions without placing report logic directly on raw operational tables.
Required source structures are checked before deployment so unsupported or missing dependencies can be identified early.
Canonical analytics views provide stable reporting contracts for the Power BI semantic model.
Native Power BI pages expose school-management views while keeping technical source identifiers out of the user experience.
For supported Ed-admin environments, DataSolv can analyse recorded learner behaviour entries by reporting period, grade, classification and behaviour type. Internal learner Notes remain outside business reporting, while authorised users can move from school-level patterns to detail and Student 360 context.
Because historical behaviour recording completeness can differ by school, DataSolv reports recorded entries rather than presenting unsupported behaviour-rate or “learners with no behaviour” measures.
DataSolv client reports are intended for authenticated Power BI distribution. The deployment model can use a Power BI workspace and app, with an on-premises data gateway where required for SQL connectivity. Power BI licences remain the client's Microsoft licensing responsibility unless expressly included in a quotation.
Source compatibility is verified because school versions, modules and historical usage can differ. DataSolv does not assume that every optional Ed-admin area exists or contains complete historical coverage.
Book a demonstration to discuss your Ed-admin environment, reporting priorities and Power BI deployment.