# Epicor Kinetic Dashboard Examples (Shop Floor, Sales, Purchasing) and How to Add Filters > Source: https://netray.co/erp-help/epicor-kinetic-dashboard-examples-shop-floor-sales-purchasing > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: ERP Help ## Short answer A useful Kinetic dashboard is a BAQ with a small number of well-chosen columns, a date or status criterion, and a grid or chart on top. Good starters are late jobs and operations for the shop floor, open order lines for sales, and past-due PO releases for purchasing. Filters come from BAQ criteria set to prompt for a value, plus grid column filters. ## Kind how-to ## System epicor ## Erp Epicor Kinetic ## Module Dashboards / BAQ / Shop Floor, Sales, Purchasing ## Query epicor kinetic dashboard examples ## Alternate Queries - epicor dashboard filter - epicor dashboard examples shop floor - epicor dashboard open orders late jobs open po ## Applies To Epicor Kinetic (2021 and later) and Epicor ERP 10 dashboards; designer screens differ between classic dashboards and Application Studio ## Steps ### How to build an example dashboard with a filter **Items:** - Open Query Builder (BAQ Designer) and create a new query for the subject, such as late jobs. - Add the tables: for the shop floor JobHead and JobOper, for sales OrderHed, OrderDtl and OrderRel, for purchasing POHeader, PODetail and PORel. - In Display Fields, choose a limited set of columns and give them clear labels; add a calculated field for days late if needed. - In Phrase Build or criteria, add conditions such as JobComplete is false and ReqDueDate is before today, and mark a criteria to prompt for a value if users should choose it. - Test the query on the Analyze tab, then save and publish it as a dashboard source. - Create the dashboard and add a grid or chart bound to the query, and set the refresh options. - Add the dashboard to a menu and assign security; check the filters and the result with a user from the target group. ## Sections ### Shop floor examples **Body:** Late jobs: query JobHead where JobClosed and JobComplete are false and the required due date is earlier than today. Show Job Number, Part Number, Required Quantity, Production Quantity, Due Date and days late. Add a priority or customer if planners need it. Operation load: query JobOper joined to JobHead with a filter on open operations and group by resource group or work center to show remaining hours. A bar chart of remaining hours by resource group shows bottlenecks at a glance. ### Sales and purchasing examples **Body:** Open order lines: join OrderHed, OrderDtl and OrderRel and filter on open releases with a need-by date in the next N days. Show customer, order, line, part, release quantity and ship-by date. A filter on sales rep or territory makes it usable for a sales team. Past-due purchase releases: join POHeader, PODetail and PORel with open releases and a due date before today. Show supplier, PO, line, part, due date and the open quantity. Buyers can filter by buyer ID or supplier to work their own list. ### Adding filters and parameters **Body:** There are three layers of filtering. First, BAQ criteria narrow the data at the database and can prompt the user for a value such as a date range or customer. Second, dashboard parameters or panel links pass a value from one panel to another. Third, the grid itself offers a filter row for quick searching of loaded data. Prefer criteria in the query for anything that limits large tables, since a grid filter works only on what was already loaded. Keep query criteria on indexed fields such as dates and status flags to avoid slow dashboards. The existing BAQ performance guidance applies to every example. ## Pitfalls - Loading entire transaction tables and relying on the grid filter to reduce them. - Joining OrderRel without considering one row per release, multiplying line counts. - Using too many columns, which makes grids slow and hard to read. - Forgetting security: a dashboard shows data from the query even where the user lacks the equivalent program access. - Not defining what late means, so different dashboards show different counts. ## Ai Angle ERPray can answer the same questions in plain language, for example which jobs are late and which customers they affect, and show the query so a BAQ author can reuse it as the starting point for a dashboard. It reads the live Epicor database through a read-only connection and respects the user's role, and on-premises it runs on your own servers. ## Faq ### What tables do I need for a late jobs dashboard in Epicor? **Answer:** JobHead is enough for job-level lateness, and JobOper adds operation-level detail. Filter on completion flags and the required date. Join to the part table only if you need descriptions. ### How do I add a filter to an Epicor dashboard? **Answer:** Add a criteria in the BAQ that prompts for a value, or use dashboard parameters and panel links. Grid column filters offer quick filtering of the loaded data. ### Can one dashboard panel filter another? **Answer:** Yes. Use the publish and subscribe settings so a selection in one panel passes a column value as criteria to another panel's query. ### Why is my dashboard slow? **Answer:** Usually the query scans a large table without a selective criteria or uses many joins and calculated fields. Add date and status filters and reduce the column list. ## Search terms epicor kinetic dashboard examples, epicor dashboard filter, epicor late jobs dashboard, epicor open orders dashboard, epicor past due po dashboard, epicor baq dashboard criteria, epicor shop floor dashboard, epicor dashboard grid filter --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json