Reporting data files
CSV, JSON and fact-and-dimension outputs using stable names appropriate to the selected source and reporting view.
BI-ready data export
Prepare local fact and dimension tables for Power BI, Tableau and Qlik
Datplan turns supported source pulls into stable reporting files with documented grains and safe relationship guidance. Keep personal dashboards in Datplan, or write the prepared BI data to a local or Windows-accessible shared location for use by an authorised Power BI, Tableau or Qlik team.
Package contents
Files that explain both the data and the setup
datplan-semantic-model.json
A machine-readable description of tables, fields, grains and validated relationship guidance.
datplan-qlik-load.qvs
A Qlik load script to support the initial file-loading workflow.
README-BI.txt
Plain-language notes for folder choice, model setup, relationships and refresh safety.
Basic reporting view
Curated business areas
Use Basic when you want a smaller set of reporting tables focused on the main finance, CRM or discovery questions. It reduces model clutter and is the clearer starting point for most reports.
Advanced reporting view
All transformed tables
Use Advanced when you need the full transformed dataset and understand the consequences of additional joins, bridge tables, row grains and relationship paths.
Shared and team access
Keep Datplan personal, share the prepared BI data
Datplan dashboards are local working views. The ETL output can be written to a shared location so a wider team can use its existing BI platform without moving the source extraction into a Datplan-hosted warehouse.
Internal finance and BI teams
Choose a Windows-accessible export folder such as a synced OneDrive or SharePoint document library or a network share. Keep the Datplan file names and folder structure stable, then configure Power BI, Tableau or Qlik to read those files using the organisation's own access and refresh controls.
- One prepared dataset for authorised team reporting
- Stable paths for repeat Datplan exports
- Power BI, Tableau or Qlik remains the shared presentation layer
Consultant-to-client delivery
If a client grants access to its SharePoint, OneDrive or shared network location, a consultant can select that accessible location as the Datplan export destination. The client keeps control of the storage and BI permissions while receiving refreshed, modelled source files for its own reporting environment.
- No consultant-hosted reporting warehouse required
- Client-controlled storage and user access
- Consultant Datplan dashboards can remain private working views
Refresh remains a two-stage process. Datplan must first update the export files. Power BI, Tableau or Qlik must then refresh from those files using the connection and authentication method configured in that platform.
Relationship safety matters more than creating the largest model
Datplan includes only relationships it can validate safely and avoids recommendations that would introduce circular or parallel ambiguous paths. A missing automatic relationship is an instruction to review the model—not an invitation to connect every matching ID.
Keep exports separate. Use a different stable folder for each workspace, source and connection. Mixing files from different clients or sources can produce stale or misleading refreshes.
BI export questions
Know what the package does before modelling
What is in a Datplan BI package?
It includes prepared data files, a datplan-semantic-model.json description, a datplan-qlik-load.qvs script and README-BI.txt setup notes. Exact tables depend on the source and selected reporting view.
What is the difference between Basic and Advanced?
Basic focuses on curated key business areas. Advanced includes all transformed tables for users who need more detailed modelling control.
Does Datplan create Power BI or Tableau project files?
No. It does not generate a finished .pbit, .pbix, .tds or .tdsx file. The first model and report setup remains manual.
Why do file names need to remain stable?
BI queries usually refer to a path and file name. Keeping both stable lets a later Datplan export replace the data that the existing query expects.
Can a team use the same Datplan export files?
Yes. Choose a Windows-accessible shared export location that your organisation controls, such as a synced OneDrive or SharePoint library or a network share. Authorised users can then use the prepared files from Power BI, Tableau or Qlik according to that platform's supported connection, permissions and refresh setup. Access, permissions and publishing remain controlled by the chosen storage and BI platform.
See Datplan with real reporting data—without connecting a live account
The Windows app is free to download and includes Datplan Demo data, so you can test sync, dashboards, reporting grains and exports first.