Skip to content

How to use Epiglossary

Epiglossary is a map of Epicor built from real support and development work. It won’t replace Epicor’s documentation or the community forum. It’s meant to get you to the right idea quickly, then point you at the places with more depth.

  1. Search first. Press Ctrl + K (or /) anywhere. Search works best with the words Epicor itself uses:

    • the exact error text from the message box
    • a business object or method, such as SalesOrder.Update or GetNewCustomer
    • a table or field, such as PartTran, TranType or OrderRel
    • a screen name, such as Customer Shipment Entry
  2. Check the badge. Every article says which client it applies to:

    Badge Meaning
    Kinetic The browser client and Application Studio
    Classic (E10) The Epicor 10 smart client, including customizations, oTrans and Event Wizard
    Kinetic + Classic Server-side or functional topics that behave the same in both, such as BPMs, Functions, BAQs, SSRS and the business processes

    If you’re on Kinetic and land on a Classic page, look for the matching Kinetic page. Migrating to Kinetic maps each Classic technique to its Kinetic replacement.

  3. Start at the overview. Every area (BPM, BAQ, Scheduling and so on) opens with an Overview page that explains the concepts and links everything in the area. When you’re new to an area, read that page before a how-to.

  4. Use the troubleshooting page. Most areas end with a Troubleshooting page in symptom → cause → fix form. Error messages are quoted exactly, so searching for the text of your error usually lands there.

  • Placeholders. Examples use made-up values so they’re safe to share: company EPIC06, custom prefix XX_, parts like PART-1001, and emails at example.com. Swap in your own values, and use your company’s naming convention for anything you create.
  • Test in a non-production environment first. Every BPM, function and data change here should be tried in Pilot or Test before Live.
  • Sources. When a page was informed by a public thread or article, the Sources list at the bottom links to it. The original discussion often has more context, alternatives and follow-ups.
  • Version notes. Most pages hold across versions. Where behavior changed in a release, the page says so inline.

Where to go when Epiglossary doesn’t have it

Section titled “Where to go when Epiglossary doesn’t have it”
  1. Search EpiUsers. Someone has very likely hit the same thing. Search for the error text or method name, and filter to the Kinetic ERP or Epicor ERP 10 category.
  2. Check Epicor’s own help. Press F1 in Kinetic for field and screen help, or open the Help & Support panel. Customers can also search the EpicCare knowledge base and problem repository (PRBs) to see whether it’s a known bug.
  3. Trace it. If you need to know what Epicor is doing, capture a trace and read the business object calls. See Find the method a screen calls and Debugging.
  4. Ask well. When you post, describe the goal rather than only the fix you tried (the XY problem). Include your version, the exact error and what you’ve already checked.

These collections pay back the time it takes to learn them.

Step-by-step write-ups from Experts’ Corner that are still some of the best Application Studio material anywhere:

Topic Thread
Grids Adding columns to an existing Kinetic grid · Working with grid selectors · BAQ grid pub-sub
Controls Making your own reusable combo · Selectable list
Dashboards Dashboard uplifts · Dashboard charts · Updateable dashboards and method directives
Events and forms Launch a form using App Studio · Upload a client file, parse it and show it in a grid · Row rule functions (older; check replies for newer approaches)
Debugging Debugging Kinetic in the browser
Server side Epicor Functions: hello world · Dynamic parameters (variables in BAQs) · Server event log dashboard
Tutorials Using a UD table as a temp table for external or generated data · Build a custom form to print job documents and tags without logging in to a job · Automatically replicate an entire environment for development and testing

Members share working code and whole projects on EpiUsers. Read the full thread before reusing anything, because later replies often carry fixes and newer approaches.

Kind Threads
Function libraries FunctionRunner2 · Helper library to get data from BAQs and Excel files · Custom library for sending REST calls out of Epicor · SysTaskMonitor library: update the activity message and write to the task log · Function to issue and return material · Stock log input library · Mass print files automatically · Configurator PcLookUp functions, server-side version · Images from alternate storage instead of database blobs
Snippets BPM logging snippet · Checking your code for speed with a Stopwatch · Simple one-liner to retrieve data from a table · LINQ with GroupBy and ToDictionary · LINQ: cast Key1 to an integer to get the max · Create a DataTable from a table with a map · DateTime offset annoyances · callContextBpmData hack · Passing tablesets to functions from directives
BAQs Fun with BAQ custom actions · Get a BAQ column label inside a BAQ BPM · Get uBAQ parameters in an advanced uBAQ BPM update · Better BOM BAQ · SQL for running queries just like Epicor
Classic client Using LINQ statements to query an EpiDataView · Get the actual row index honoring DataView filters · Customization tips and tricks (MEUG presentation code) · Tool tips · Automatically printing attachments
Kinetic and BPM forms Easy Kinetic App Studio project · Dynamic combo on a BPM form (Kinetic and Classic) · Manipulating the Kinetic web UI from the backend · A way to distinguish method directives
Projects The Stoplight Report: a time-phase summary for all parts · FindInCode: search BPM and BAQ code · CSVtoExcel · Modbus to Epicor integration · Printing from Epicor using BarTender · REST API and BarTender (Insights 2024)
Discussions BPM best practice · Using anonymous types to organize your code · Copy UD fields from QuoteDtl to OrderDtl when creating an order from a quote · Low-coder’s corner

In the product itself, F1 opens help for the current field or screen, and the Help & Support panel collects help articles, videos, guided tours and release notes.

More utilities, such as dotPeek, SSMS and barcode tools, are listed in Tools and links.

Every page has an Edit page link at the bottom that opens it on GitHub. Corrections, missing gotchas and better examples are welcome. The style guide covers the house rules: write in your own words, use placeholder data, and credit your sources.