Seamless Data Visualization: Connecting Power BI to Business Central via OData and Default Integrations 

If you’ve ever stared at Business Central’s raw data and thought, “There’s gold in here, but how do I actually see it?”, you’re not alone. Dynamics 365 Business Central holds a wealth of information on finances, inventory, sales, and operations, but turning that into actionable insights often means pairing it with Power BI. The good news? Microsoft has made the connection incredibly straightforward, whether you stick to the built-in defaults or go custom with OData. 

This guide breaks down both approaches: the quick plug-and-play integrations using Microsoft’s pre-built Power BI apps, and the more flexible OData method for tailored dashboards. We’ll cover setup steps, pros and cons, real-world tips, and when to choose one over the other. By the end, you’ll have the tools to build dashboards that deliver real-time KPIs, predictive trends, and even cross-system blends. No more endless Excel exports required. 

Why Power BI + Business Central is a Game-Changer

Business Central is great for transactions, but Power BI excels at visualization and analysis. Together, they let you drill from high-level overviews (like cash flow trends) straight into individual invoices. You get interactive charts, AI-driven insights, mobile access, and the ability to merge BC data with external sources. For SMBs running manufacturing, distribution, or services, this combo can cut reporting time dramatically and spot issues before they escalate. 

The integration works best in BC Online (SaaS), but on-premises users can connect too with a few extra steps. Licensing note: You’ll need Power BI Pro for sharing, and BC Essentials or Premium for full features. 

OData and Default Integrations p1

The Default Path: Microsoft's Power BI Apps for Instant Wins

The easiest way to get started is with Microsoft’s official Power BI apps. These are pre-packaged dashboards designed specifically for Business Central, covering areas like Finance, Sales, Inventory, Purchasing, Manufacturing, and Projects. They’re live, drillable, and embed right into your BC Role Center. 

Here’s the simple setup: 

  1. Enable the Connector in BC: In Business Central, click the gear icon > Assisted Setup > Search for “Power BI.” Run the wizard. It handles authentication and workspace creation. 
  2. Grab the Apps: Head to app.powerbi.com > Apps > Get more apps (or search AppSource for “Dynamics 365 Business Central”). Install the ones you need, like the Finance app. Initially, it uses demo data. 
  3. Link Your Data: In the app, select “Connect your data.” Enter your BC environment (e.g., Production), company name, and sign in with your Microsoft account. 
  4. Embed in BC: Back in Business Central, go to the Power BI section on your Role Center. Select the report from the dropdown. Your dashboard appears instantly, with tabs for key metrics like profit margins or aged receivables. 

These apps pull live data, support dimensions (departments, projects, etc.), and allow basic tweaks like slicers or color changes. Click a visual? It opens the exact BC record.  

Users love this for quick setups. Many report going from weekly manual reports to daily insights. A common win: Inventory apps that highlight turnover rates and stockouts in real time. 

Drawbacks? Customization is limited; major changes get overwritten on updates. Ideal for standard KPIs and team-wide sharing. 

The Custom Route: Business Central Connector and OData for Ultimate Flexibility

Need something bespoke? OData (Open Data Protocol) exposes BC data as queryable web services. It’s perfect for building from scratch in Power BI Desktop, blending with other sources, or handling complex scenarios like multi-company views or predictive analytics. 

OData V4 is the current standard, offering REST-like queries with better performance than older versions. 

Step-by-step in Power BI Desktop: 

1. Find Your OData Feed: In BC, search “Web Services” for published entities. Browse to the OData URL field and document what your tenant’s specific OData URL is. 

OData and Default Integrations p2 1

2. Add New Data Source: Inside of Power BI Desktop, click Transform Data > New Source > More.

OData and Default Integrations p3 1

3. Connect to BC: When the New Data Source window opens, search for Dynamics 365 Business Central connector.

OData and Default Integrations p5 1

4. Load Entities: The Navigator lists entities (G/L Entries, Customers, etc.). Load what you need in the report. Once all required entities are selected, click OK and load the results in Power Query. 

OData and Default Integrations p6 1

5. Data Transformation: With your entities loaded into Power Query, apply any filtering and/or transformation of data according to your reporting needs, then click Close & Apply to load the queries into the Power BI report.

OData and Default Integrations p7 1

Note: To enhance performance, filter and transform data as close to Business Central as possible. Power Query can handle complex data transformations, but performance is optimized if data transformations are handled in BC before loading into Power BI. 

 

6. Data Modeling: With your newly loaded BC data, you now need to verify that the table relationships are built and accurate.

OData and Default Integrations p8

7. Build Visuals: Now that your table relationships are set, you can build your dashboard, add drill-throughs, what-if parameters, etc.

OData and Default Integrations p9 1

8. Deploy Power BI Report: When your report is complete and ready to view, click Publish and then choose the appropriate Power BI workspace to deploy the report to and click SELECT. 

OData and Default Integrations p10 1

OData shines for power users: One example is combining BC sales data with external APIs (weather, market trends) for forecasting. It handles massive volumes efficiently and supports full customization without update conflicts. 

On-prem caveats: Ensure OData endpoint is enabled and accessible; use Entra ID or access keys (no Windows auth in Power BI). 

Default Apps vs. OData: Quick Comparison 

 

Start with apps for speed, then layer in the Business Central connector or OData for depth. Many hybridize: Use apps for ops, OData for executive strategy. 

Common Pitfalls and Fixes 

Permissions Issues: Check Power BI workspace access and BC permission sets. Fiscal vs. Calendar Year: In BC, set Accounting Periods to “Standard.” Dimensions Not Filtering: Ensure they’re applied at header/line level on transactions. Errors/Timeouts: Verify URL case-sensitivity; retry transients; optimize queries. 

Analysis Mode Bonus: In BC lists, use Copilot for plain-English pivots. No Power BI needed for quick ad-hoc.

OData and Default Integrations p11 1

Final Thoughts: Turn Data into Decisions

Connecting Power BI to Business Central, whether via defaults or OData, unlocks faster, smarter insights. Defaults get you 80% there instantly; OData handles the custom 20% that drives real growth. 

Ready to try? Test in a sandbox first. For deeper dives, check Microsoft’s docs or community forums. 

What’s your go-to integration method, or biggest hurdle? Share in the comments. Happy visualizing! 

User struggling using ERP after a failed implementation

Microsoft Dynamics 365 Business Central Resources

Explore Our Resource Links to Unlock the Full Potential of Dynamics 365 Business Central in Your Business Endeavors:

Get Your Free ERP Assessment | Explore Our Services | Learn More About Crestwood

Connect With Us: X | LinkedIn | Contact Us 
More Resources: Acumatica ERP | Business Central | Blog Home 

© 2025 Crestwood Associates. All rights reserved. 

Author

Share the Post:

Related Posts