How-toEpicor KineticDashboards / Refresh / Publish and Subscribe

Epicor Dashboard Refresh All, Timers, Publish and Subscribe, Parameters and Runtime vs Assembly

Question
epicor dashboard refresh all

Also searched as

  • epicor dashboard timer set
  • epicor dashboard publish and subscribe
  • epicor dashboard parameters
  • epicor dashboard runtime vs assembly
  • epicor dashboard change owning company

Short answer

Epicor dashboards refresh when the user runs the query, through a refresh action that updates every panel, or on a timer setting in the dashboard definition. Panels exchange values through publish and subscribe columns, queries take parameters as criteria, and a dashboard is either a runtime definition built in the system or an assembly dashboard compiled as code.

Applies to: Epicor ERP 10 and Epicor Kinetic dashboards; some options are in classic dashboard tools and may be located differently in Application Studio, so verify in your version

How to set refresh, links and parameters

  1. 1Open the dashboard in the Dashboard Definition tool (or the equivalent in your version) and select the panel or query to configure.
  2. 2For a manual refresh of all panels, use the refresh action on the dashboard toolbar so each query runs again with its current criteria.
  3. 3For automatic refresh, set the refresh timer interval on the dashboard or the panel in the definition, and keep it long enough for the query to finish.
  4. 4To link panels, mark columns as published on the source query and configure the subscribing query to use the published column as a criteria value.
  5. 5For parameters, define criteria on the BAQ that prompt for values, and set defaults such as today or the current user.
  6. 6Decide whether the dashboard is a runtime definition (no code) or an assembly dashboard (custom compiled code) and keep to one approach per dashboard.
  7. 7To move a dashboard to another company, export it and import it into the target company, then check security and menu entries.

Refresh behavior and timers

A dashboard query runs when the panel loads and when the user triggers a refresh. A refresh all action runs every panel, which can be expensive if panels are heavy. A timer re-runs the query at a fixed interval, useful for a shop floor status display and wasteful for a monthly report.

Every timer refresh is a full query execution against the database for every open copy of the dashboard. Twenty users with a one-minute timer on a slow query is a load problem. Set the interval according to the real decision speed, and put the heavy summary panels on a longer interval.

Publish and subscribe between panels

Publishing makes a column value from the selected row available to other panels in the same dashboard. A subscribing query uses that value as a criteria, so choosing a customer in one grid filters the order grid beside it. This gives a drill-down from summary to detail without opening another program.

Check the column names and data types on both sides. A published value of a different type, or a blank selection, leads to no rows or an error. Provide a sensible default for the subscriber when nothing is selected.

Runtime versus assembly, and owning company

A runtime dashboard is defined in data: queries, panels and layout built in the designer, with no compiled code. It is easy to export, import and upgrade. An assembly dashboard is a compiled .NET assembly that uses the Epicor client libraries, and it needs development, deployment of the assembly and compatibility work at each upgrade.

A dashboard belongs to the company where it was created, so another company does not see it automatically. The dependable path is to export it from the source company and import it into the other, or to create it as a system-level item where your version offers that. Do not edit the database directly.

Try it here, free

Epicor BAQ Runtime and Row Volume Estimator

Open full tool

Model how filters, joins and indexes change the rows a BAQ reads and the seconds it takes, before you publish it to users.

Common pitfalls

  • !Setting short timers on heavy queries, which loads the database for every open session.
  • !Publishing columns with mismatched types or names.
  • !Building assembly dashboards when a runtime dashboard would do, adding upgrade risk.
  • !Assuming a dashboard created in one company appears in all companies.
  • !Not testing the dashboard with a user who has restricted security.

How an ERP-grounded AI assistant handles this

Where a dashboard is only a way to ask the same question repeatedly, an assistant grounded in the Epicor data can answer the question on demand with the query shown, which avoids timers and heavy refreshes. The dashboard stays the right tool for a wall display or a fixed team view.

See ERPray

Frequently asked questions

How do I refresh all panels in an Epicor dashboard?

Use the refresh action on the dashboard toolbar, which re-runs every panel query with its current criteria. For unattended displays, set a timer in the dashboard definition instead.

How do I make one dashboard grid filter another?

Mark a column as published on the first query and set the second query to use it as a criteria value. When a row is selected, the second panel refreshes with the published value.

What is the difference between a runtime and an assembly dashboard?

A runtime dashboard is defined in system data with the designer and needs no code. An assembly dashboard is compiled custom code deployed as an assembly, with more flexibility and more maintenance.

How do I move an Epicor dashboard to another company?

Export it from the source company and import it into the target company, then reapply security and menu entries. Verify the exact options in your version.

Related

How-to

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-to

Epicor Kinetic Dashboard Examples (Shop Floor, Sales, Purchasing) and How to Add Filters

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.

How-to

Convert Epicor Classic Dashboards to Kinetic

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.

Error fix

Fixing 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-to

Fixing 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.

How-to

Epicor 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 ERP

AI 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 ERP

Private 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.

Talk to an ERP engineerBrowse ERP Help
All ERP Help articles

Keep exploring

Free tools

ERP fixes and how-tos

Guides

AI on your ERP

Integrations

Comparisons

Software

TermsEpicor BAQ (Business Activity Query)Event-Driven ArchitectureEpicor BPM (Business Process Management)