Data Panda reads your self-hosted Dynamics NAV or Business Central tenant through its OData web services and lands the data in a warehouse next to the rest of your business. From there we build dashboards, automations, AI workflows and small apps your team uses every day.
Microsoft Dynamics NAV and the on-prem versions of Business Central are the same Navision codebase Microsoft picked up in 2002 and kept iterating on. The cloud product runs on a published REST API, but the on-prem build exposes its data a different way: you publish individual pages and queries from the Web Services page, and the server hands them out as OData V4 endpoints on a port like 7048, scoped per company.
For BE and NL mid-market companies that still run NAV 2018, BC 14, BC 17 or a more recent on-prem release, that OData layer is the practical way out. The same customers, vendors, items, sales orders, journals, GL entries and dimensions you see in the role centre can be read into a warehouse without an upgrade project to BC Online first. The ERP keeps doing its job, and the data starts working for the people outside the BC client.
Numbers your team needs from NAV or on-prem BC, on a page that does not need a BC client or another seat.
Make NAV or on-prem BC talk to webshops, CRMs and tools without writing AL extensions for every link.
Most on-prem tenants carry a decade of operational history. Use it.
Small browser tools for people who should not need a NAV seat for a single task.
A list of concrete reports, automations and AI features we have built on MS Business Central OData (on prem) data. Pick the one that matches your situation.
Do we have to move to BC Online before this becomes useful?
No. The OData web services in NAV and on-prem BC expose the same customers, items, sales orders and ledger entries the cloud REST API does. We read straight from your server instance into a warehouse, and reporting, automations and apps light up there. If a cloud move comes later, the warehouse and the surfaces on top of it stay; only the source side gets reconfigured.
How do we report across multiple NAV companies without an upgrade project?
Each company in your NAV or on-prem BC database is its own OData scope, addressed by name or by company id. We pull each company once, land them in the same warehouse and apply a shared chart-of-accounts mapping. Group P&L, AR, AP and stock then run on one model, regardless of how many separate companies are inside the database.
Years of history sit in NAV. How do we get value out of it now?
The same OData endpoints expose item ledger entries, GL entries and posted documents for as far back as your tenant goes. Once that history is in the warehouse, reorder logic, churn signals and seasonal patterns become workable instead of theoretical. You stop debating whether to keep the data and start pricing, planning and forecasting against it.
Cash, AR and AP on one weekly view across every NAV company in the group, with worsening accounts called out instead of buried in an aging report. Month-end closes against what NAV already booked, no Excel rebuild every period.
Live stock and quote margin in front of the rep at quote time, plus a cleaner pipeline-to-order-to-invoice view than the standard NAV sales role centre. Reps stop calling the office to check whether something is in stock or sells profitably.
Stock per location, vendor reliability, slow-moving SKUs and reorder suggestions in one place, fed by NAV item ledger entries. The warehouse and the buyer stop chasing each other across NAV pages and start working from one priority list.
Shopify orders create sales orders in the right NAV or on-prem BC company through the published OData page service, with the right item, customer, price and tax setup. Refunds come back as credit notes, and stock and shipment status flow back to Shopify, so the webshop, the warehouse and the NAV ledger stay in step without a daily import file.
Closed-won HubSpot deals turn into sales quotes in the right NAV company with the right contact, items and pricing already filled in. Invoice and payment status from the NAV ledger flow back to the deal, so marketing and sales report against booked revenue instead of pipeline value.
New Salesforce accounts create NAV customers with billing, shipping and payment terms set, and order, invoice and payment status flow back to the Salesforce account view. Reps see a live order picture in their CRM without opening NAV or pinging finance.
Events from on-prem NAV or BC post into the right Slack channel: an invoice over a threshold goes overdue, a sales order misses its promised date, an item drops below safety stock, a purchase order sits in approval too long. The right person sees it the same hour, instead of finding out at the next NAV report cycle.
NAV jobs and project tasks land on a monday.com board with assignee, due date and status, and progress updates flow back as project entries in NAV. Project managers and finance see the same status without separate weekly check-ins.
Groups with NAV in one entity and Exact Online in another get both sets of GL, AR and AP entries into the same warehouse, with a shared chart-of-accounts mapping. Group reporting and consolidation work on one model, no monthly export from either system.
You keep the reporting tool you already have. We connect it to the warehouse where your MS Business Central OData (on prem) data lives.
OAuth authentication. Read-only by default. We sign a DPA and your admin keeps the keys.
Data flows into your warehouse on your schedule. Near real time or nightly, your call. You own the data.
We build the first dashboard, workflow or AI feature with you, then hand over the keys. Or we stay on for ongoing delivery.
We set up the foundation. Your team builds on top.
Best fit Teams that already have a BI analyst or data engineer and want to own the build.
We build the whole thing, end to end.
Best fit Teams without in-house BI or dev capacity. You tell us what you need and we deliver it.
You do. It lands in your warehouse, on your cloud account. We don't resell or aggregate it. If you stop working with us, the warehouse stays yours and keeps running.
Near real time for most operational systems. For heavier sources we schedule hourly or nightly. You pick based on what the reports need.
No. If you don't have one, we help you pick one and set it up as part of the first delivery. Common starting points are Snowflake, Microsoft Fabric, or a small Postgres start.
Standard NAV objects like Customer, Vendor, Item, Sales Order and G/L Entry already have OData-friendly pages and queries shipped with the product. We use those where they exist. For specifics like a custom dimension breakout or a posted-shipment view, your NAV partner publishes a page or query once on the Web Services list, and the warehouse picks it up from there.
We need the OData endpoint reachable from the warehouse, which is usually a port like 7048 on the Business Central Server. That's typically solved with a VPN, an SSH tunnel or a small reverse proxy your IT already has in place; we don't ask for domain credentials beyond a dedicated NAV user with read rights on the relevant pages.
We review your MS Business Central OData (on prem) setup and the systems around it. Together we pick the first thing worth building.