Datplan help
Create a stable BI package and refresh it safely
Choose the reporting view, write the package to one dedicated folder and preserve the paths and names used by Power BI, Tableau or Qlik.
Create the package
- Complete and review a source syncDo not export an unexplained partial or failed run.
- Open Advanced exportsSelect the exact workspace, source and connection.
- Choose Basic or AdvancedStart with the curated Basic view unless the full transformed set is required.
- Select a stable dedicated folderKeep one client or connection per folder.
- Create the BI packageReview the included README and semantic-model description before building relationships.
Expected setup files
datplan-semantic-model.json
datplan-qlik-load.qvs
README-BI.txt
Prepared data files are included according to the source, reporting view and selected export format.
Refresh sequence
Run Datplan first and verify the source export. Then refresh the BI model that reads those files. If the BI report is published, verify that separate cloud refresh stage as well.
Export questions
Keep the model refreshable and reviewable
Where should I save a BI package?
Use a stable local folder dedicated to one workspace, source and connection. Do not combine different clients or sources in the same refresh folder.
Which view should I choose?
Start with Basic for curated key business areas. Choose Advanced only when you need all transformed tables and are comfortable reviewing additional relationships.
Can I rename exported files?
Do not rename files that an existing BI query uses. Stable paths and names are what allow a later Datplan export to feed the same model.
Does exporting publish data to a cloud BI service?
No. Datplan writes local files. Publishing or configuring a cloud refresh is a separate user action governed by the BI provider.
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.