How should we build this?
Builds and versions
DraftBuild queue
Approved versions appear here and are built in Power BI.
Approved versions appear here and are built in Power BI.
Four short steps. Every number in the report, Insights and the board pack is calculated from this data.
Pick where it lives. Daxwell reads it and Power BI refreshes from the same place. Credentials are never stored by Daxwell.
Sheets with the same columns and a shared prefix (for example PBI_NORTH, PBI_SOUTH) are appended into one table, the way Power BI will read them.
Pick a table to see its columns, what Daxwell found in them and anything that looks wrong.
Check how Daxwell read each column. If something is wrong, say what it means in your own words.
Check this, then build the report or open Insights and the board pack.
Keep the pages and rewrite their measures so they work on these tables.
Builds into the Power BI semantic model. Describe changes in plain English, or edit here.
Every client is on the one Daxwell plan: everything included.
Only native Power BI visuals are used unless this is ticked. Custom visuals need the client's Power BI admin to allow them (organisational visuals or AppSource).
Organisation settings. Reports, Insights, the board pack and exports follow these.
How Daxwell looks for you. This does not change your reports.
Board pack colours follow the report theme. Pick colours here to override them in the preview, HTML, PDF and PowerPoint.
Choosing a region fills in the rest; each one can still be changed.
With more than one, each report asks which workspace to publish to the first time it's built, and remembers the answer.
This month's assistant allowance for your organisation. Alerts go to Owners and Admins at 80%; at 100% new requests pause until the allowance resets.
Loading…
Built from your live data. Pick a slide to change its headline, visual, wording and notes, then send it for review or sign it off.