Business Central Power BI: Reports, Dashboards & Apps, Explained

What 'Business Central Power BI' actually means

Business Central online ships with built-in Power BI integration. Since February 2022, BC sources Power BI traffic from a secondary read-only database replica so reporting does not compete with transactional load on the primary database. Operational data reaches Power BI primarily through OData v4 API pages and queries (API V2.0 is the recommended surface) via the Dynamics 365 Business Central connector. The two products are designed as a pair, not a bolt-on.

It helps to frame BC plus Power BI as a layered system. Layer one is the embedded experience: Role Center parts, list-page FactBoxes, and report pages that surface Power BI inside BC. Layer two is the Power BI service, where interactive apps, workspaces, and shared dashboards live. Layer three is Power BI Desktop, where you build or extend semantic models and reports on the same API feeds. Layer four (2025 onward) is source-level ownership: Microsoft open-sourced the standard BC Power BI apps so you can fork models and visuals instead of rebuilding from a blank canvas. Microsoft also documents dataflows and datamarts via the Business Central connector in Power Query Online when you need shared, reusable preparation layers across many reports.

Each standard app is also a two-part product. A connector (AL) app ships preinstalled with Business Central and holds the APIs, setup pages, and embed surfaces. A separate Power BI template app on Microsoft Marketplace (AppSource) holds the semantic model and report pages. Both must be installed and configured before the out-of-the-box reports work.

Online versus on-premises matters. Marketplace Power BI apps, assisted setup, and Role Center embeds are first-class for Business Central online. On-premises can still expose OData web services and embed reports, but it requires additional Entra app registration and admin setup, and it does not get the same turnkey app catalogue experience. If you are still on-prem, plan the identity, gateway, and API surface before you promise the same dashboard experience as a SaaS tenant.

Vocabulary note: the phrase 'Business Central content pack' is legacy. Microsoft replaced content packs with Power BI template apps (now commonly called Power BI apps). This guide uses 'Power BI apps' throughout.

How to connect Business Central to Power BI

For Business Central online, start with assisted setup. Search for 'Set Up Power BI reports' or 'Connect to Power BI'. The guided flow verifies licensing and deploys default embedded reports. It is a one-time setup per environment. You can also configure parameters on the Power BI Connector Setup page without the wizard.

To install a functional-area Power BI app, open Microsoft Marketplace (AppSource), pick the BC app that matches your version (apps for 27.0 and later differ from version-26 packages), and install it into a dedicated Power BI workspace. Authenticate with OAuth2 and set the privacy level to Organizational so Power BI treats your BC tenant as an internal data source. Microsoft recommends one workspace per app so access boundaries stay clean.

After install, set two parameters on each semantic model in the Power BI service: Environment and Company. Company is case-sensitive — a mismatch silently returns no data. Assisted setup also asks for Calendar Type (Fiscal is the default; Standard and Weekly 445/454/544 are available), UTC offset (aligned to your BC time zone so 'today' is correct when the app is hosted in another region), Date Table Range (auto-filled from accounting periods; extend the end date if budgets run past the last period), and Work Days (Monday–Friday by default).

Map embedded reports back into BC so Role Centers and Report Explorer open the right app pages. On Power BI Connector Setup, link each functional area to the Power BI workspace and report you installed. Restrict load volume with app-level start/end date filters (or relative-date formulas where supported) before the first large refresh.

In Power BI Desktop, the manual path is Get Data → Online Services → Dynamics 365 Business Central. Navigator shows Environments, then Companies, then endpoints — prefer API V2.0 over legacy OData web services. Apply date-based filters early; OData scans across years of history are the most common cause of slow refreshes and timeouts.

On newer tenants (Business Central 2026 release wave 1 / BC28.2 and later), Power BI Report Deployments offers centralized install, status tracking, retry, and PBIX download for standard apps. As of mid-2026 documentation and partner write-ups, that deployments experience is available in evaluation companies first — production multi-company rollouts still commonly use Marketplace install plus Connector Setup.

1. 01
   Run assisted setup in Business Central

   In BC, search 'Set Up Power BI reports' or 'Connect to Power BI'. The guided flow verifies licensing, configures calendar/UTC/date range/work days, and deploys default embedded reports. One-time per environment.

2. 02
   Install the Power BI template app from Marketplace

   Use the version-matched install link (27.0+ vs version 26), sign in with a Power BI Pro (or capacity-backed) account, authenticate with OAuth2, set privacy to Organizational, and put each app in its own workspace.

3. 03
   Set Environment and Company parameters

   Open the semantic model → Settings → Parameters. Company is case-sensitive. Copy exact values from assisted setup or Power BI Connector Setup.

4. 04
   Map embeds, filters, dimensions, and refresh

   Map workspaces to functional areas for Role Center embeds. Set data-load date filters. Ensure the job queue entry for Update Dim. Set Entries runs (weekly or nightly). Run Refresh now, then schedule refresh within your license limits.

5. 05
   Connect manually in Power BI Desktop (optional)

   Get Data → Online Services → Dynamics 365 Business Central. Choose API V2.0 under the correct Environment and Company. Prefer star-schema models over flat API dumps.

Three Business Central Power BI architecture paths

Most failed BC + Power BI projects start by mixing three different jobs into one PBIX. Pick a primary path, then extend only where the path cannot answer the question. The three production-ready paths for SMEs in 2026 are: Microsoft template apps, custom semantic models in Power BI Desktop, and shared preparation via dataflows or datamarts.

Path A — Microsoft Power BI apps (default for most SMEs): install the version-matched Marketplace template for Finance, Sales, Purchasing, Inventory, and any other area you run. Map Environment and Company, schedule refresh, embed on Role Centers. Use open-source forks when you need 20% custom measures on an 80% complete model. This path is fastest to value and keeps measure definitions aligned with Microsoft's KPI docs.

Path B — Custom Power BI Desktop models: use Get Data → Dynamics 365 Business Central, select only the API V2.0 pages you need, model a star schema, and publish to a governed workspace. Choose this when the question spans companies, merges non-BC sources (CRM, warehouse IoT, spreadsheet forecasts), or needs a process Microsoft does not ship. Prefer Import mode with incremental refresh for SME interactivity; treat DirectQuery as an exception for very large or near-real-time sources that truly cannot import.

Path C — Dataflows / datamarts for shared prep: when multiple report teams keep re-shaping the same BC tables, centralize cleaning and joins in Power Query Online dataflows (or datamarts where licensed). Reports then connect to the prepared layer instead of re-pulling raw APIs. This path reduces refresh contention and stops five authors from inventing five 'revenue' definitions.

Starter set for a typical SME: install Finance first (liquidity, P&L, AR/AP), then Sales (revenue, retention, forecast), then Inventory or Purchasing depending on whether stock or spend is the pain. Manufacturing, Projects, Subscription Billing, and Sustainability wait until the process is live in BC and owners will actually open the report. Do not install every app on day one — each app is a workspace, a refresh job, and a Pro-seat conversation.

Default Business Central Power BI reports by functional area

Microsoft publishes a dedicated BC Power BI app per functional area. Each app bundles a semantic model, multiple report pages, embed surfaces in BC, and Role Center / Role Explorer links. Knowing what ships out of the box stops you rebuilding reports that already exist.

The Finance app covers financial statements and operational finance: Financial Overview, Income Statement by Month, Balance Sheet by Month, Budget Comparison, Liquidity KPIs (current, quick, and cash ratios), Profitability, EBITDA, Average Collection Period, Aged Receivables and Aged Payables, Late Payments, Liabilities, and detailed G/L, customer, and vendor ledger slices. If your finance team asks for a cash-ratio trend or aged AR by payment terms, the report already exists.

The Sales app covers revenue analytics: Sales Overview, Daily Sales heatmaps, Moving Average and Moving Annual Total, Period-over-Period and Year-over-Year growth, Sales by Item, Customer, Salesperson, Location, and Projects, Actual vs Budget, Sales Forecasting, Opportunity and Quote overviews, Return Orders, Sales Demographics, Decomposition, and Key Sales Influencers. Customer Retention Overview and Customer Retention History — generally available with Business Central 2026 release wave 1 (April 2026) — add loyalty, repeat-purchase, and churn-trend analysis so sales and finance stop exporting customer lists to spreadsheets for cohort checks.

Purchasing adds spend analytics (Purchases Overview, Period-over-Period and YoY, by Item, Vendor, Purchaser, and Location, Actual vs Budget, Vendor Quality, and Forecasting). Inventory adds availability and replenishment views (Overview, by Item and Location, Item Availability, Gross Requirement and Scheduled Receipt, Bin Contents, and ABC Analysis driven by ABC Analysis Setup — default 50/30/20 sales-value split across A/B/C, customizable so the three percentages sum to 100).

Additional apps cover Inventory Valuation, Projects, Manufacturing, Subscription Billing (including refreshed churn and recurring-revenue pages in 2026 wave 1 partner summaries), and Sustainability — each with its own model and report set. Before building anything custom, audit the app for your area and confirm the BC tables behind its KPIs so the refresh account has Read permission on every required table.

Power BI licensing traps that catch SMEs

This is where SMEs lose money and time. Power BI Free only works in a personal workspace and cannot install Marketplace template apps or share workspace content the way teams need. To install a BC app, refresh its semantic model, or view reports (in the Power BI service or embedded in Business Central), Microsoft documents Power BI Pro for the installer, the refresher, and each consumer — unless the content lives on Power BI / Microsoft Fabric Premium capacity that allows free viewers against that capacity. Practitioner write-ups in 2026 stress the same rule: Free is for solo exploration; the moment a second person views a shared or embedded BC report, paid licensing (or capacity) applies.

Current Microsoft list pricing (US, paid yearly, verified August 2026 on Microsoft's Power BI pricing page): Power BI Pro is $14 per user per month; Power BI Premium Per User (PPU) is $24 per user per month. Those list prices took effect 1 April 2025 (up from $10 and $20). Business Central Essentials and Premium do not include Power BI Pro seats — budget Pro as a separate line for every person who will open, share, or author reports, unless they already hold Microsoft 365 E5 or Office 365 E5, which include a Power BI Pro license per assigned E5 user.

Microsoft retired Power BI Premium per capacity P-SKUs for new purchases in July 2024; existing customers transition to Microsoft Fabric capacity (F-SKUs). Fabric makes sense when many free viewers and larger models justify capacity cost. Microsoft documents free viewing of capacity-backed content for Fabric SKUs F64 and above (and legacy P1+). Most SMEs are better on Pro per user until viewer counts or dataset size force a capacity conversation.

Apps are per-company. Each company in your BC tenant that you want to report on needs its own template-app install (or semantic-model configuration), typically in its own workspace. Cross-company consolidation requires a custom model, multi-company design, or deliberate merge outside the standard apps. Plan the company parameter before the first refresh fails.

Refresh ceilings are license- and capacity-bound, not marketing slogans. On shared (Pro) capacity, scheduled refresh is limited to 8 times per day (quota resets at 12:01 AM local time). On PPU, Premium, or Fabric capacity, you can schedule up to 48 times per day. Model size ceilings also differ (Pro models are much smaller than capacity-backed models). If finance wants near-real-time cash position, schedule design and incremental refresh matter as much as the SKU — but the SKU sets the ceiling.

Refresh, row-level security, and governance

A BC Power BI app is only as trustworthy as its refresh path and access model. Treat the semantic model as a production system: named owners, a second admin on every app workspace, documented refresh windows, and a clear rule for who can edit the model versus who can only view reports.

Refresh operations: after parameters and filters are set, run a manual refresh to validate credentials and data volume. Then schedule refresh inside your daily quota. Keep the BC job queue entry that runs Update Dim. Set Entries on a weekly or off-hours cadence so dimension set entries appear in apps after dimension changes. The Power BI account used for refresh needs Read permission on every BC table the model queries — Microsoft documents those tables per app KPI article.

Row-level security (RLS) belongs in the semantic model, not only in BC permission sets. Define roles and filter rules in Power BI Desktop (or the service model editor where supported), publish, then assign Entra ID users or groups to roles under Semantic model → Security. Test each role with 'View as' before go-live; broken RLS often looks like 'missing data' rather than an error. Use dynamic RLS (USERPRINCIPALNAME against a security bridge table) when sales managers must only see their customers. Object-level security is a separate control if certain columns must never leave the model.

Workspace governance: Microsoft guidance for template-app workspaces is high governance — do not treat the install workspace as a free-for-all authoring sandbox. Prefer a governed workspace for the certified semantic model, separate workspaces or apps for distribution, and a clear promotion path from sandbox to production. For multi-company tenants, name workspaces by company and functional area so parameters and access reviews stay auditable.

Single source of truth: pick one semantic model (or a thin set of domain models) per process metric. Do not let three custom PBIX files redefine 'revenue' three ways. When you customize an open-sourced Microsoft app, fork deliberately, keep measure names aligned with finance definitions, and document any divergence from the standard app so month-end reconciliation stays sane.

Open-source apps, drill-back, and centralized deployments

Three Microsoft changes reshape how SMEs should approach Business Central Power BI in 2025–2026: open-sourced app code, drill-back with dynamic dimensions, and centralized report deployments — plus continuous expansion of the Sales and Subscription Billing report sets.

Open source (generally available 1 October 2025 as part of 2025 release wave 2): Microsoft released source for the standard Power BI apps — including Finance, Inventory, Inventory Valuation, Manufacturing, Subscription Billing, Sustainability, Sales, Purchasing, and Projects. Instead of reverse-engineering measures, download the PBIX / source, adjust the semantic model for your dimensions and KPIs, and publish your controlled fork. That is the right path when a default report is 80% correct but missing a product family, legal entity filter, or margin definition.

Drill-back and dynamic dimension names (2025 release wave 2): standard apps gained tighter trust loops. Drill-back jumps from a Power BI visual into the underlying Business Central transactions so finance and ops can validate a number without a separate inquiry. Dynamic dimension names reduce cryptic dimension codes in visuals so managers read business language instead of setup keys. Partner posts in mid-2026 still highlight these as the features that finally make BC + Power BI trustworthy enough to retire shadow Excel workbooks.

Customer loyalty and retention analytics (Business Central 2026 release wave 1, generally available 1 April 2026): Customer Retention Overview and Customer Retention History join the Sales Power BI surface so repeat purchase, loyalty, and churn trends are first-class report pages rather than DIY DAX projects.

Power BI Report Deployments (Business Central 2026 release wave 1 / BC28.2): a list page (Power BI Report Deployments) lets you deploy multiple standard reports to a workspace, watch status (including Queued), retry failures, and download PBIX for selected reports. Partner documentation (including mid-2026 BC28.2 walkthroughs) notes the experience landing first in evaluation companies — treat it as the emerging control plane for standard apps, not a replacement for Pro licensing or semantic-model parameters.

The KPIs every SME should track in Business Central Power BI

Most SMEs install the apps, stare at the Overview page, and move on. The value is in the KPIs behind the reports. The five that move the needle for an SME finance and operations team are: cash ratio and current ratio (liquidity), DSO and DPO (cycle time), and inventory turnover (working capital).

Liquidity: the Finance app ships current, quick, and cash ratios out of the box. Trend these monthly against your operating expense run-rate, not against an industry benchmark you found online.

Cycle time: Average Collection Period (DSO) and the equivalent on the payables side (DPO) come from the Aged Receivables and Aged Payables reports. A 5-day improvement in DSO on a mid-sized SME is real cash.

Working capital: inventory turnover and days-of-supply come from the Inventory app. Pair them with Gross Requirement vs Scheduled Receipt so purchasing decisions follow demand, not gut feel. Use ABC Analysis Setup when inventory decisions need class-based focus instead of equal attention to every SKU.

The trap is defining too many KPIs. Pick the three to five that map to this quarter's operating priorities, pin them to a Role Center, and review them weekly. Power BI metrics lets you track these against targets without building a new report. When a metric needs a definition battle, resolve it in the semantic model once — that is the single source of truth section above, applied.

Near-live Business Central numbers without brittle Excel exports

Finance teams usually do not ask for 'a semantic model.' They ask for trustworthy numbers that match BC without tonight's CSV dump. Treat Excel exports as a failure mode, not a design pattern: they break column names, lose permissions, and never keep AR aging in sync with the ERP.

Prefer scheduled Import refresh of Microsoft apps or a thin custom model on API V2.0, with date filters and incremental refresh (RangeStart / RangeEnd) so history stays manageable. Eight Pro refreshes per day is enough for most SME close cycles if you schedule around bank cutoff and order-entry peaks. When eight is not enough, move the model to PPU or Fabric capacity for up to 48 scheduled refreshes before you redesign the whole stack.

Use drill-back from Power BI visuals into Business Central transactions (2025 release wave 2 and later apps) so controllers validate a number against the source document instead of rebuilding the query in Excel. Dynamic dimension names reduce the 'code soup' that used to force side spreadsheets for management language.

If leaders need a live wallboard during a shift, pin the high-priority page to a Role Center part and set a refresh cadence the license can sustain. Do not promise DirectQuery against every BC table as a free real-time feed — the Dynamics 365 Business Central connector and standard apps are built around Import-style semantic models, not unlimited live SQL against SaaS. When true cross-system real-time is mandatory, you are in a custom architecture conversation (Azure data platform, event pipelines, or capacity-backed models), not a Marketplace click-through.

Building custom Business Central Power BI dashboards

When the default apps do not answer a specific question — and open-source forks still fall short — build a custom report in Power BI Desktop on the same API V2.0 feeds. The discipline that separates a maintainable dashboard from a slow, brittle one is data-volume hygiene: filter at the source, not only in the visual.

Start in Power BI Desktop with Get Data → Online Services → Dynamics 365 Business Central. Select only the API pages you need — pulling every endpoint 'just in case' is the most common cause of refresh timeouts. Apply date filters using the RangeStart and RangeEnd parameters (case-sensitive reserved names) so incremental refresh can partition history from the rolling window.

Model with star schema discipline. BC API pages give you flat transactional tables; resist reporting off them directly. Build a date table aligned to your fiscal calendar, a customer dimension, an item dimension, and a single fact table per process (sales, purchases, ledger). Keep DAX measures simple and refreshes fast. Prefer reusing or extending Microsoft's open-sourced models when your custom need is a thin layer on a standard domain.

Publish to a workspace backed by the right capacity (Pro per user for small teams, Fabric F-SKU at scale). Pin key visuals to a Role Center in BC so the dashboard lives where users already work. Apply RLS before wide distribution. Test in a sandbox environment first: BC sandboxes let you validate refresh timing, parameter behaviour, and performance without risking the live semantic model.

Performance checklist before you call a custom model 'done': only required API pages selected; date filter at Power Query; incremental refresh configured; relationships in star form; no bi-directional relationships unless proven necessary; RLS tested with View as; refresh account Read permissions documented against Microsoft's KPI table list for that domain.

Why Business Central Power BI shows blank, slow, or wrong data

Blank reports almost always trace to parameters or permissions, not 'Power BI is broken.' Confirm Environment matches the BC environment name and Company matches the company name exactly (case-sensitive). Confirm the refresh identity has Read on the app's source tables. Confirm the template app version matches your BC major version (27.0+ packages vs version-26 packages).

Slow refreshes usually mean unbounded OData pulls. Tighten start/end date filters on Power BI Connector Setup, reduce selected API pages in custom models, enable incremental refresh with RangeStart/RangeEnd, and avoid calculating heavy measures over unfiltered fact tables. Watch for schema drift: renamed or removed source columns fail service refresh until you schema-refresh in Desktop and republish.

Wrong numbers often mean calendar mismatch (Fiscal vs Standard vs Weekly), UTC offset wrong for your geography, budgets extending past the date table end date, or dimension set entries not updated after dimension changes. Re-run Update Dim. Set Entries, re-check calendar setup, and compare a sample measure to a BC inquiry with drill-back where available.

Sharing failures are licensing. Users with only Free seats cannot consume shared Pro workspace content the way teams expect. Either assign Pro (or PPU) to each consumer or place the model on Fabric/Premium capacity that supports free viewing. Embedded pages in BC still require the viewer path documented for your capacity model.

Frequently asked questions