Skip to content
onagero

Analyzing Business Central: connect Dynamics data with your other sources

Business Central comes with reports and a connection to Power BI. But where a workflow needs data from production, Excel and ERP together, the analysis often ends up being done by hand again. With Onagero, your team builds exactly this analysis itself.

  • Read only
  • No change to your ERP
  • Connection included in the pilot
  • GDPR ready

In short

Onagero reads data from Microsoft Dynamics 365 Business Central through the interfaces your IT releases for this, and connects it with sources outside the ERP. The tool runs on your server. If you already have Power BI and someone who maintains it, we will tell you honestly whether Onagero still adds anything.

Possible ways to the data

Which one fits for you we clarify with your IT before the contract.

Released interface

Business Central provides data through programming interfaces. A service account with read rights on the required data is enough.

On-premises installation

If Business Central runs on premises at your site, read-only database access is also possible, if your IT prefers it.

Export

A scheduled export is enough to start with.

What your IT provides

  • a service account with read rights on the required data
  • for cloud operation: release of the connection from your network
  • a server or virtual machine in your network

Good to know

If you already use Copilot Studio or Power Platform, you will find the side-by-side comparison on our comparison page: what Microsoft covers and where Onagero goes further with data from industrial systems.

Turning Microsoft Dynamics data into a foundation to build on

What stays with you, what Onagero makes of it, and what the language model gets to see.

Onagero creates an analysis copy of the needed data on your server and describes it in the data map: the meaning of each column, relationships, origin and review status. Your people build on that.

In development, the copy holds no personal data. Released applications read from a live view only what their roles allow.

The data path at Onagero Your systems feed, over a read only connection, into a masked analysis copy on your server. Your people build internal tools from it with Onagero. Only the released, masked parts of a request go to the model provider. Your server, your network ERP BDE and MES Excel, files Analysis copyNames masked OnageroYour people build Internal toolwith roles per person Live view, only what thetool may read Model provider, external What goes out is only what a request needs: released and masked. The databasestays in your building. The data path at Onagero, top to bottom Your server, your network ERP BDE, MES Excel Analysis copyNames masked OnageroYour people build Live view, released Internal toolwith roles per person Model provider, external Only what a request needs, released and masked. The database never leaves your building.
The path of your data: platform, analysis copy and tools on your server; only masked parts of single requests go to the language model. Data security in detail

Questions about connecting to Microsoft Dynamics

Why not Power BI?

If it is maintained on your side and covers the question, Power BI is a good choice. Onagero is worthwhile where data first has to be brought together, a tool needs more than charts, or nobody can take over the maintenance.

Does this also work with Dynamics NAV?

Older installations usually have read-only database access. We clarify the route before the contract.

Does Onagero write into Business Central?

No. Tools read.

Where does the data sit when Business Central runs in the cloud?

Business Central stays where it is. Onagero reads the required data onto your server; the route to the model provider is described on the Data security page.

Which problem would
your team solve first?

Show us a real process. We will show you how it could look with Onagero.

Book a demo →

Check first whether a pilot fits: fit check in 2 minutes →