Convert Epicor Classic Dashboards to Kinetic
epicor convert classic dashboard to kinetic
Also searched as
- epicor turn classic dashboard to kinetic
- epicor configuration upgrade dashboard
- epicor classic dashboard kinetic upgrade
Short answer
Classic dashboards built on BAQs convert most easily to Kinetic because the query survives and only the presentation changes. Dashboards with custom code, complex layouts or tracker panels often need to be rebuilt in Application Studio. Inventory them, convert in a test environment, then verify data, filters, actions and security one by one.
Applies to: Epicor upgrades from Classic (Smart Client) dashboards to Kinetic; conversion tooling and coverage vary by target release
How to move Classic dashboards to Kinetic
- 1List every Classic dashboard in use: who opens it, how often, and which BAQs and custom code it relies on. Retire the ones nobody uses.
- 2In a test copy of the upgraded environment, check your release for a dashboard conversion utility and run it against a small set first.
- 3Open each converted dashboard in Application Studio and compare the grids, filters, parameters and actions against the Classic original.
- 4Rebuild panels that did not convert: complex layouts, custom code, charts and tracker views, using the same BAQ as the data source.
- 5Re-test any actions that open other programs, such as launching Order Entry from a row, and the parameter passing to them.
- 6Check security: menu placement, dashboard security and BAQ access for each role.
- 7Compare row counts and key totals between Classic and Kinetic for a known date range.
- 8Roll out in groups and keep the Classic version available until users sign off.
What usually converts and what does not
The data layer is the stable part. A BAQ is the same object in both worlds, so a dashboard that is a grid over a BAQ with a few filters generally converts with little rework. Layout is the unstable part, because Kinetic uses a different layout model and component set.
Expect manual work for dashboards that embed custom code, use many nested panels, rely on tracker or tree views, or carry chart settings. These are rebuilt rather than converted, and a rebuild is also a good time to simplify.
Treat it as a clean-up
Most long-lived Epicor environments hold dashboards no one opens, duplicated BAQs and queries with hardcoded dates. Use the conversion as the moment to retire them. Fewer dashboards means less to test and less to maintain after the upgrade.
Where several dashboards differ only by a filter, consider one Kinetic dashboard with parameters. That reduces the maintenance surface and makes future changes cheaper.
Verification checklist
For each converted dashboard check four things: the data matches, the filters and parameters work, the row actions open the right program with the right key, and the right roles can see it. Record the result so the sign-off is evidence, not memory.
Run the check with a restricted user as well as an administrator. Security differences are the most common surprise after a conversion.
Try it here, free
Epicor Application Studio Layer Checklist
A checklist for Kinetic Application Studio layers covering naming, scope, events, rules, security, testing and upgrade impact.
Common pitfalls
- !Assuming a converted dashboard is finished because it opens.
- !Converting dashboards nobody uses.
- !Skipping testing with restricted roles.
- !Forgetting that custom code in Classic does not carry over automatically.
- !Moving everything at once instead of in small groups.
How an ERP-grounded AI assistant handles this
An assistant that reads your dashboard and BAQ definitions can build the inventory, flag which queries are shared, and compare Classic and Kinetic output for the same date range. That inventory is useful before an upgrade, and with a private deployment none of it leaves your network.
Frequently asked questions
Do Classic dashboards work in Kinetic automatically?
Not fully. The BAQ queries remain, but the presentation layer differs, so some dashboards convert with a tool and others must be rebuilt in Application Studio. Plan time for testing and rework.
Which dashboards must be rebuilt?
Those with custom code, complex layouts, charts, trackers or tree views typically need rebuilding. Simple BAQ grids with filters convert most easily.
Should I keep Classic dashboards after the upgrade?
Keep the definitions until users sign off the Kinetic versions, then retire them. Keep a record of what was retired.
How do I verify a converted dashboard?
Compare row counts and totals for a known range, test filters and actions, and run it as a restricted user. Record results per dashboard.
Related
How to build a Kinetic homepage dashboard in Epicor
Kinetic homepage dashboards are built from Active Homepage Maintenance: create a BAQ that returns the metric or list you want, add a KPI or List widget referencing that BAQ, arrange widgets on the homepage layout, and assign the homepage to a role or company so the right users see it.
How-toPreserving Customizations When Upgrading to Epicor Kinetic
Epicor Kinetic's web UI does not simply inherit classic smart-client customizations - most need to go through the Update Customization / Application Studio conversion process, and some WinForms-specific customizations cannot convert directly and must be rebuilt in the Kinetic designer. Plan the upgrade as a customization inventory and rework project, not a single technical cutover step.
How-toFixing a Slow Epicor BAQ (Business Activity Query)
A slow BAQ in Epicor is usually caused by unindexed join columns, a subquery or calculated field forcing a table scan, or the BAQ pulling far more rows than the dashboard actually displays before filtering client-side. Fix it by reading the SQL Server execution plan Epicor generates, moving filters into the BAQ criteria instead of the dashboard filter panel, and replacing subqueries with joins where possible.
AdvancedEpicor Application Studio: understanding customization layers
Kinetic UI is built in layers loaded in order - Base (Epicor-delivered), Customization (Application Studio, company/layer-wide), Personalization (user- or role-specific, applied on top), and optionally Extended (packaged add-on layers) - and a change you make will not appear if a higher layer overrides the same control or if you are testing in the wrong layer context.
Error fixFixing Epicor BusinessObjectException: BPM Directive Errors
A BusinessObjectException that says "A Business Process Management (BPM) directive has raised the following error" means a directive on that business object stopped the transaction, either deliberately via a Raise Exception widget or accidentally via an unhandled .NET error in Custom Code. Expand the InnerException on the error dialog to see the real message and the directive name, then open BPM Designer for that object and method to find the widget that fired.
How-toEpicor MRP Runs but Generates No Suggestions
When Epicor's MRP process completes without a job or purchase suggestion for a part you expect one for, the cause is almost always the part's own configuration (Part Class Type, Make Direct, Non-MRP flag, planning Time Fence) or the demand not being linked in a way MRP recognizes, not a defect in the MRP engine. Work through the part's Planning tab, its safety stock and lead time setup, and the demand source (sales order line status, job material requirement) before assuming the run itself failed.
AI for ERPAI for Epicor Kinetic, Beyond What Prism Covers
Add AI to Epicor Kinetic beyond Prism: private LLM over BAQs, BPM data, and REST v2, on-prem or private cloud, with honest guidance on when Prism already covers you.
AI for ERPPrivate AI for Epicor Kinetic Cloud, Outside the Multi-Tenant Boundary
Run a private LLM on Epicor Kinetic private cloud or Kinetic Cloud data via BAQs, REST v2 and Data Fabric, keeping sensitive manufacturing data off shared AI.
Stuck on Epicor Kinetic?
Talk to engineers who work inside Epicor Kinetic every week, and who build private AI that answers these questions from your own ERP data.
Keep exploring
Free tools
- Epicor Application Studio Layer ChecklistA checklist for Kinetic Application Studio layers covering naming, scope, events, rules, security, testing and upgrade impact.
- Epicor Kinetic Upgrade ChecklistA phase-by-phase upgrade checklist covering inventory, testing, integrations, cutover and rollback for Epicor Kinetic.
- Epicor Kinetic Upgrade Readiness AssessmentTen questions scoring how ready your customizations, BPMs, reports and integrations are for an Epicor upgrade.
ERP fixes and how-tos
- Preserving Customizations When Upgrading to Epicor KineticMoving Epicor 10 classic customizations to the Kinetic web UI is a conversion, not an automatic carry-over. Here is the checklist for what survives, what needs rework, and how to sequence the upgrade.
- How to build a Kinetic homepage dashboard in EpicorGuide to building Kinetic homepage dashboards in Epicor: KPI tiles from a BAQ, tracker widgets, layout, and security-driven personalization by role.
- Epicor Kinetic Dashboard Examples (Shop Floor, Sales, Purchasing) and How to Add FiltersPractical Epicor Kinetic dashboard examples for shop floor, sales and purchasing, with the tables to query and how to add filters and parameters.
AI on your ERP
- Private AI for Epicor Kinetic Cloud, Outside the Multi-Tenant BoundaryRun a private LLM on Epicor Kinetic private cloud or Kinetic Cloud data via BAQs, REST v2 and Data Fabric, keeping sensitive manufacturing data off shared AI.
- AI for Epicor Vantage, Vista, and E9, and a Real Kinetic Upgrade PathStill on Epicor Vantage, Vista, or E9? Add a private LLM over that Progress OpenEdge database now, and use it to plan a Kinetic upgrade with real data, not guesswork.
Integrations
- How to connect Power BI to Epicor KineticConnect Power BI to Epicor Kinetic using BAQ OData feeds, a data warehouse or a SQL replica, with an on-prem gateway, key dashboards and natural-language Q&A.
- How to add a mobile app to Epicor KineticBuild or choose a mobile app for Epicor Kinetic: barcode scanning, labor reporting, inventory moves and approvals over the REST API, with offline handling.
Software
- Epicor KineticEpicor Kinetic explained for manufacturers: modules, REST API, BAQs, deployment, strengths, limits and alternatives to compare before choosing or upgrading.
- Epicor CPQEpicor CPQ is a cloud configure-price-quote product with visual 3D configuration for manufacturers. Modules, ERP integrations and alternatives explained.