How to connect Power BI to proALPHA
Short answer
Do not build reports straight on live OpenEdge tables. Load selected data into a reporting database or warehouse, model it in Power BI, and refresh through the on-premises data gateway. Then add natural-language Q&A on top of the same model.
Power BI is the most common request from proALPHA finance and operations teams who outgrow list exports and Excel. proALPHA runs on a Progress OpenEdge database, which Power BI does not read natively, so the path usually goes through ODBC or through an intermediate database.
The temptation is to connect DirectQuery to production tables. That tends to disappoint: table and field names are technical and customised, joins are non-obvious, and heavy visuals can load the live ERP. Most successful projects stage the data first and model it for reporting.
Your proALPHA release may also include its own business intelligence or analytics components. Check what you already license before building anything, because a standard cube or export may cover part of the need.
What teams use it for
On-time delivery and OTIF
Compare promised and actual ship dates by customer and product group, with drill-down to the order line.
Production order performance
Planned versus actual hours and material by order and work centre, to see where routings are wrong.
Inventory ageing and turns
Stock value by age bucket and warehouse, with slow movers flagged against recent demand.
Purchasing performance
Supplier on-time rate, price variance against last purchase and open commitment by month.
Margin by order and product
Sales value against actual cost, for post-calculation reviews on one-off machine builds.
Cash and open items
Receivables ageing and expected payments joined from finance tables, for weekly cash meetings.
proALPHA integration surface
- OpenEdge SQL ODBC or JDBC driver: Power BI can use ODBC through the on-premises gateway. Driver version and bitness must match across the gateway and desktop machines.
- Reporting database or warehouse: nightly or incremental loads from OpenEdge into SQL Server or similar give cleaner models and protect the ERP. Choose incremental keys per table, as changed-date fields vary.
- proALPHA analytics components: depending on release, there may be built-in BI or cube features. Confirm with your partner before duplicating.
- Exports: scheduled CSV or Excel outputs are a fallback when database access is restricted.
- On-premises data gateway: required for scheduled refresh from an internal source to the Power BI service.
How it works
- 1
Pick three dashboards
Choose delivery, inventory and production performance. Define each measure in writing with the business owner.
- 2
Map source tables
Document which OpenEdge tables and fields feed each measure, including customised fields. Record the traps, such as status codes.
- 3
Stage into a reporting database
Load nightly or incrementally. Create clean views with business names and resolved codes.
- 4
Build the semantic model
Use a star schema with date, item, customer, supplier and plant dimensions. Put measures in DAX once.
- 5
Install and configure the gateway
Use a dedicated server, standard mode, with service account and the matching ODBC or database driver.
- 6
Apply row-level security
Restrict by plant, sales region or cost centre using roles, matched to your Entra ID groups.
- 7
Reconcile and release
Tie dashboard totals to proALPHA reports for a closed month before wider rollout.
Example flows
Nightly refresh for the delivery dashboard
Trigger: Scheduled at 02:00
- Staging job extracts changed order lines from OpenEdge.
- Views resolve statuses and calculate lateness in days.
- Gateway triggers the Power BI dataset refresh.
- Morning dashboard shows yesterday's shipments.
Result: Operations review on-time delivery without exporting a spreadsheet.
Ask a question about the model
Trigger: Manager types a question in the report's Q&A or a Copilot-style feature
- The question is mapped to fields in the semantic model.
- Power BI builds a visual from measures you defined.
- Manager pins it to the dashboard.
Result: Self-service answers limited to the governed model, not raw ERP tables.
Keeping data on-prem
Power BI Desktop and the on-premises gateway let you keep the source database inside your network, while the report service itself is Microsoft-hosted. If your policy forbids that, Power BI Report Server is the on-prem option, with fewer features and a different licence. For natural-language questions on-prem, add a local model that translates questions into queries against your reporting database or semantic layer, so no data goes to an external AI service. The staging database should be a replica or reporting copy, not the live OpenEdge instance.
Security checklist
- Read-only staging credentials, and no gateway account with ERP write rights.
- Row-level security aligned to plants and sales regions.
- Sensitivity labels and workspace access limited by role for cost and margin data.
- Restrict export and sharing settings for sensitive reports.
- Monitor gateway and refresh logs for failed or unexpected loads.
Ways to get it done
Use proALPHA's built-in BI or analytics
Effort: Low; configuration with your partner.
Fits if your release already includes the reports you need.
Staging database plus Power BI
Effort: A few weeks for a first three dashboards, mostly modelling.
The common route for finance and operations dashboards.
Add natural-language Q&A with a private model (Netray)
Effort: Additional weeks on top of an existing model.
When managers want to ask questions beyond the prebuilt visuals, with data kept local.
Pitfalls
- !DirectQuery on live OpenEdge tables, which can slow users down and the ERP.
- !Driver mismatch between Desktop and gateway, so the report refreshes locally but fails online.
- !Ignoring customised fields and statuses, so numbers differ from proALPHA reports.
- !No agreed definitions, leading to two versions of on-time delivery.
- !Giving unrestricted cost and margin access to everyone in the workspace.
Frequently asked questions
Can Power BI connect directly to proALPHA?
Indirectly. proALPHA uses an OpenEdge database, so you connect through ODBC, often via the on-premises gateway, or better through a staged reporting database. Direct live queries on production tables are possible but rarely advisable.
Do we need a data warehouse?
Not always, but a staging database usually pays off. It protects the ERP, lets you clean codes and names, and gives a stable model. For a small first project, a few scheduled views on a replica may be enough.
Does proALPHA have its own BI tools?
Depending on release and licence, proALPHA offers analytics and reporting components. Check with your partner what you already own before building a parallel Power BI model.
Can we ask questions in natural language?
Yes, either through Power BI's Q&A style features on a well-named semantic model or with a separate AI layer that queries your reporting database. For on-prem data policy, the private model option keeps data inside.
How often can data refresh?
Nightly is typical. More frequent refresh is possible with incremental loads, but it needs reliable changed-date keys and consideration for load on the ERP. Confirm the real need before promising near-real-time.
Want Power BI working on your proALPHA?
A free 30 minute assessment: we map the integration path for your version and setup, and where it should run.
Get a free assessment