Converting Classic Epicor Dashboards to Kinetic UI

Overview

Migrating from Epicor ERP 10 (WinForms UI) to modern Kinetic layouts represents a major shift from client-side C# coding to low-code App Studio configurations. Many IT departments assume the native converter tool executes a flawless transition, only to find that custom C# code-behinds, grid events, and manual adapter calls fail to load entirely. Since client-side C# is not supported in browser-native Angular interfaces, all Classic dashboard logic must be refactored.

When tackling dashboard conversion issues, the first rule is to separate client presentation from database logic. For example, if you previously had complex button triggers that populated text boxes by querying adapters, those must be rebuilt. Translate the intent of your C# scripts into App Studio Events and Actions. For standard dashboard grids, utilize Epicor's native row rules and App-Open actions rather than custom code-behinds. For deeper guidance on restructuring your interface, check out our comprehensive Epicor App Studio Customization Guide.

Technical Implementation Details

To implement this solution in your Epicor environment, utilize the following code block. Ensure you replace the standard configurations with your company database names, server URLs, and keys.

// Example of migrating legacy C# client script filter to server-side query parameters.
// In Classic WinForms, developers wrote client-side C# to modify query parameters:
// DynamicQueryAdapter dqa = new DynamicQueryAdapter(oTrans);
// QueryExecutionDataSet qeds = dqa.GetQueryExecutionParametersByID("MyBAQ");
// qeds.ExecutionParameter[0].ParameterValue = myTextBox.Text;
//
// In Kinetic, we declare an Event with "Action: ERP-BAQ" and map target parameters via App Studio:
{
  "eventName": "OnTriggerBAQ",
  "actionType": "erp-baq",
  "baqId": "MyBAQ",
  "executionParameters": [
    {
      "ParameterName": "MyFilterParam",
      "ParameterValue": "?{KeyFields.TextBoxValue}"
    }
  ]
}

Process Verification and Flow

Before launching the migration, audit all existing dashboards to identify which ones rely on legacy C# code. If your dashboard uses client-side calculations or queries multiple business objects, migrate that logic into server-side Epicor Functions (EFx) or post-processing Method Directives. For a complete pre-migration roadmap, consult our developer-focused Epicor Upgrade Customization Checklist to ensure a smooth transition with zero shop-floor downtime.