How Publishing an Epicor Dashboard Works
Publishing typically follows dashboard development and validation. A developer creates the dashboard, verifies its data sources and query behavior, configures the presentation, and makes it available according to the organization's deployment and access procedures.
A typical publishing workflow includes the following activities:
- Build and validate: Confirm that the dashboard displays accurate information and that its filters return the expected records.
- Configure access: Set up the appropriate security permissions so intended users can open the dashboard and access its underlying data.
- Publish the dashboard: Use the applicable Epicor tools and deployment process to make the configured dashboard available.
- Test with users: Verify that the dashboard opens correctly, displays expected information, and supports the intended business tasks.
- Maintain the published version: Review the dashboard after relevant changes to queries, business rules, security, or ERP configuration.
Publishing a dashboard does not automatically grant every user access to its source records. Permissions, company access, and data security remain important parts of deployment.
How Dashboard Subscriptions Work
Subscription behavior depends on what the dashboard supports. In a dashboard with linked views, one component may supply a selected record or parameter to another component, allowing users to explore related information. Other supported subscription or notification mechanisms may help users receive updates or focus on changes relevant to their work.
For example, a finance dashboard might display a list of overdue customer invoices alongside a detail panel. Selecting a customer or invoice can update the related view when the dashboard is configured for that interaction. This allows a finance employee to review summary information and supporting transaction details within a connected workflow.
Before implementing subscriptions, developers should identify the event or data relationship that triggers an update, the information passed between components, and the expected result. They should also test whether filters and parameters behave consistently for different users and business units.
Practical Finance and Procurement Use Cases
Dashboard publishing and subscription features can support several business processes by making relevant information available to the teams responsible for action.
- Accounts payable: Share invoice approval queues, due-date summaries, and supplier payment status with finance employees.
- Accounts receivable: Present outstanding balances and customer payment activity, with related views that help users investigate individual transactions.
- Procurement: Make requisition, purchase order, and approval information available to purchasing teams.
- Management reporting: Distribute consistent summaries of operational performance, financial activity, and outstanding exceptions.
For procurement teams, a Purchase Order Creation Walkthrough can help users understand the transaction stages represented in a dashboard, while Purchase Order Creation Process Explained provides context for requisitions, approvals, and purchase order issuance.
For accounts receivable, dashboards may help teams investigate unmatched customer payments and remittance details. How Hyperbots AI Agents 10x Epicor Finance Operations and Closing Epicor Finance Gaps with Hyperbots AI Agents discuss how finance workflows involving cash application, deductions, and receipt posting can be extended with AI agents.
ERP Integration and Configuration Considerations
Dashboard publishing should align with the organization's Epicor ERP environment, data structures, and security model. The dashboard must use appropriate queries and definitions so that different users interpret financial and operational measures consistently.
Epicor Integration Finance describes the coordination of financial data across ERP and connected systems. Understanding these integration points helps teams establish whether dashboard information comes directly from Epicor or from an approved external data source. The relevant Epicor ERP Modules also determine where transaction data originates and which functional teams use it.
When extending epicor workflows, teams should confirm that published dashboards remain compatible with the ERP configuration and that changes are tested before deployment. Technology-led approaches such as agentic ai can support broader finance transformation, but accurate dashboard data, defined permissions, and clear business rules remain essential.
The Hyperbots Platform supports company-specific ERP integrations, workflows, user roles, and general ledger structures through a no-code configuration framework. Its Process Specific Capabilities support finance workflows with domain-focused AI automation, and Ready to Deploy Capabilities include pre-trained agents and ERP connectors. Self Learning Capabilities allow systems to adapt from human actions, while Human in the Loop approaches provide review and approval for cases requiring employee judgment. These capabilities complement ERP dashboard reporting by addressing workflow execution and oversight.
Best Practices for Publishing and Subscribing
Effective dashboard management requires clear ownership and repeatable validation. Developers should document the purpose of each dashboard, its intended audience, the source of its metrics, and any subscription or interaction rules. A dashboard should present information that supports a specific decision rather than simply collecting unrelated measures.
Before releasing changes, compare displayed totals with source transactions, test representative filter combinations, and verify access for users with different roles. Where dashboards use linked components, test selections and parameter changes to ensure the correct records appear. After publication, assign an owner to review the dashboard when reporting requirements, workflows, or ERP settings change.
These practices help organizations maintain reliable shared reporting, support consistent financial decisions, and improve visibility across procurement, accounting, and operational teams.
Summary
Epicor Dashboard Publish and Subscribe covers the publication of configured dashboards and the supported relationships that connect users, views, data, or updates. Publishing makes dashboards available to authorized users, while subscription behavior enables relevant interactions or updates according to the dashboard's configuration. By validating data, managing permissions, testing linked views, and maintaining clear ownership, organizations can use Epicor dashboards to strengthen reporting consistency and operational visibility.