How to connect Power BI to Made2Manage
Short answer
Because current Made2Manage installs run on SQL Server, Power BI can connect through the on-premises data gateway to purpose-built views or a reporting copy. Build a small star-schema model of jobs, orders and inventory first, then add dashboards and, optionally, natural-language Q&A.
Made2Manage ships with reports, and many shops have years of Crystal Reports and exports to Excel. Those answer known questions but are slow for exploration, and they live in a handful of heads. Power BI gives managers slicing and trending without a developer for every request.
The catch is that an ERP schema is built for transactions, not analysis. Pointing Power BI at raw tables produces slow reports and numbers that disagree with the ERP screens. The fix is a thin semantic layer: views or a small warehouse that encode your business definitions once.
This page covers the connection options, the dashboards that matter to a job shop, and how to add question-and-answer on top.
What teams use it for
On-time delivery dashboard
Promise date versus ship date by customer, product line and month, with drill-through to late orders and root causes.
Job cost versus estimate
Estimated and actual hours and material per job, with variance by work center and part family.
Backlog and capacity
Open orders by due week against routing hours per work center, to see overload before it happens.
Inventory health
On-hand value, turns, slow-moving stock and negative balances, split by location.
Purchasing performance
Supplier on-time receipt, price variance and open commitments by buyer.
Made2Manage integration surface
- SQL Server direct query or import mode via the Power BI SQL Server connector, with the on-premises data gateway bridging to the cloud service.
- A reporting replica or nightly copy keeps analytical queries away from the live shop database.
- SQL views you define (open orders, job cost, inventory snapshot) become the stable interface; table names vary by version and customisation.
- Older FoxPro-based installs will need an export or replication into SQL Server before Power BI can use them well.
- Excel and CSV exports from existing reports are a fallback for a quick start, but lose refresh automation.
How it works
- 1
Choose the data path
Prefer a replica or nightly staging database. Direct query on production is a last resort and should be tested for load.
- 2
Build the semantic views
Create views for fact tables (order lines, job operations, receipts) and dimensions (customer, part, work center, date) with clear definitions.
- 3
Install the gateway
Put the on-premises data gateway on a server with network access to SQL Server, using a dedicated read-only service account.
- 4
Model in Power BI
Import views, relate them in a star schema, and write measures for on-time %, variance and turns once, reused everywhere.
- 5
Reconcile with the ERP
Compare totals against known ERP reports before sharing. Fix definitions, not visuals, when numbers differ.
- 6
Add Q&A and publish
Turn on Power BI's natural-language Q&A on a curated model, or add an external assistant for richer questions, then set refresh schedules and row-level security.
Example flows
Weekly operations review
Trigger: Dataset refreshes at 5 a.m. through the gateway.
- Views are read from the reporting replica.
- The report shows late orders and overloaded work centers.
- The ops manager drills into a late order to see the blocking operation.
Result: The meeting starts from data instead of from reports pulled the night before.
Ask a question in plain language
Trigger: Executive types: which customers had the worst on-time delivery last quarter?
- Q&A maps the words to model fields and measures.
- A visual is generated from the semantic model.
- The user pins it to a dashboard if it is useful.
Result: Quick answers without a report request to IT.
Keeping data on-prem
Power BI Desktop and the gateway let you keep SQL Server on-prem while publishing to the cloud service, but the imported data does live in the Power BI service. If that is not acceptable, Power BI Report Server is the on-premises option, with its own licensing and feature differences from the cloud service. For natural-language questions on data that must stay local, put an open-weight model on your own GPU over the same semantic views, using vLLM or Ollama, and keep Power BI for fixed dashboards. This split is common for shops with customer-restricted data.
Security checklist
- Use a read-only SQL account for the gateway data source and restrict it to reporting views.
- Apply row-level security in the model for customer-, plant- or region-scoped audiences.
- Exclude cost rates and margin from broadly shared datasets.
- Limit workspace membership and review sharing settings.
- Patch and monitor the gateway server as you would any server holding credentials.
Ways to get it done
Direct connection to SQL views
Effort: A few weeks for a first set of dashboards.
Small installs wanting fast results with a reporting replica.
Staging database or warehouse
Effort: One to three months including modelling.
Multiple sources, heavy history, or performance concerns.
Partner such as Netray for model plus AI Q&A
Effort: A scoped project, typically several weeks.
You want dashboards and a private natural-language layer over the same definitions.
Pitfalls
- !Connecting visuals to raw tables and getting slow, inconsistent numbers.
- !Running heavy refreshes on the production database during the shift.
- !Defining 'on time' differently in each report.
- !Forgetting gateway availability; a stopped service means stale dashboards.
- !Ignoring customisations such as user-defined fields that change the meaning of columns.
Frequently asked questions
Can Power BI connect directly to Made2Manage?
It can connect to the underlying SQL Server database with the standard SQL Server connector, assuming your install is on SQL Server. Use the on-premises data gateway for refresh, and point at views or a reporting copy instead of raw production tables.
Do we need a data warehouse?
Not always. A small shop can use well-designed SQL views over a replica. A warehouse becomes worthwhile when you need long history, several systems in one report, or when analytical queries are hurting transaction performance.
Why do Power BI numbers not match Made2Manage reports?
Usually definitions or filters differ, such as which statuses count as open or how dates are chosen. Reconcile against a known ERP report, then encode the agreed definition once in a view or measure rather than in each visual.
Can we ask questions in plain English?
Power BI offers natural-language features on curated models, and their availability depends on your licence and tenant settings. For richer or private questions, a separate assistant over the same semantic views can run on-prem with an open model.
Is Power BI Report Server an option?
Yes, if you must keep reporting on-premises. It has its own licensing requirements and does not match every cloud feature. Confirm your needs, such as refresh and mobile access, against its documented capabilities before choosing it.
Want Power BI working on your Made2Manage?
A free 30 minute assessment: we map the integration path for your version and setup, and where it should run.
Get a free assessment