Most Business Central Power BI Problems Aren’t Power BI Problems

I spent some time browsing the Dynamics 365 Business Central Community forums recently. One thing immediately stood out: almost every Power BI question looked different, but most had the same root cause.

Some people couldn’t connect the standard apps.
Others still saw CRONUS.
Some reported missing data.
Others believed Power BI was returning incorrect figures.

At first glance, these appear to be completely unrelated issues.

They’re not.

After reading through many of the discussions, I noticed that very few questions were actually about Power BI itself. Most were configuration issues somewhere between Business Central and Power BI.

Microsoft’s own Power BI FAQ for Business Central reflects exactly the same pattern.

Whenever someone tells me “Power BI isn’t working”, I work through the same checklist.

Step 1 – Is the report connected to the correct Business Central environment?

This is the first thing I verify.

Installing one of Microsoft’s standard Power BI apps doesn’t automatically connect it to your Business Central environment.

After installation, you still need to connect the app to your:

Tenant
Environment
Company

If the report still shows CRONUS, you’ve almost certainly found the problem.

Useful references:

If you’re looking for the PBIX files behind Microsoft’s standard apps, you can also read:

Quick Tip: How Can You Download the Standard Business Central Power BI Reports?

Step 2 – Verify the environment and company

A surprising number of “wrong data” issues turn out to be perfectly correct data…

…from the wrong place.

Many customers have multiple environments:

Production
Sandbox
Test
Development

Even within the correct environment, multiple companies may exist.

Before investigating datasets, refresh schedules or permissions, verify you’re looking at the right environment and company.

I’ve spent more time than I’d like to admit troubleshooting reports that were simply connected to the wrong company.

Step 3 – Check access from both sides

Power BI and Business Central each have their own security model.

A user needs permission to:

access the Power BI workspace;
access the Business Central data.

Having SUPER in Business Central doesn’t automatically grant access to Power BI, and Power BI permissions don’t override Business Central security.

Both sides have to be configured correctly.

If licensing is involved, Microsoft’s documentation explains the supported scenarios:

Step 4 – Check when the data was refreshed

Sometimes nothing is broken.

The dataset simply hasn’t refreshed yet.

Before looking for more complicated explanations, check:

Last successful refresh
Scheduled refresh
Refresh failures

Quite a few “missing transactions” appear after someone posts new data and immediately opens the report.

Useful references:

Step 5 – Only now do I suspect Power BI

Authentication problems happen.

Microsoft service incidents happen.

Connector issues happen.

But after reading dozens of forum discussions, they appear far less frequently than configuration mistakes.

That’s actually reassuring.

It means Power BI itself is usually doing exactly what it has been configured to do.

The real pattern

The interesting observation isn’t that people have Power BI problems.

It’s that they rarely have the same Power BI problem.

Instead, they run into different configuration issues that all produce the same conclusion:

“Power BI doesn’t work.”

In reality, Business Central, authentication, APIs, workspaces, datasets, refresh schedules and licensing all have to line up before the first chart appears.

Power BI is simply the last step in that chain.

When one of the earlier steps is misconfigured, the dashboard becomes the messenger.

Don’t shoot the messenger.