EpicorFree worksheetPDF, Excel, Word exportEpicor Kinetic

Epicor User Defined Field Register Worksheet

UD fields are how Epicor sites extend standard tables, and over the years they pile up with names like Character07 that nobody can explain. This register gives each field a meaning, an owner and a usage count.

Download:

Table	UD column	Data type	Business label	Used by	Owner	Total rows	Rows populated	Fill %	Action
								86.7%
								14.1%
								54.2%
								0%
								4.9%

UD fields registered

Average fill %

32%

Lowest fill %

Highest fill %

86.7%

Run counts of populated rows from a SQL or BAQ query against each table and paste them here. Fields with near zero fill and no owner are retirement candidates, after checking reports and customizations that reference them.

Data dictionary help

An optional review that documents your UD fields and where they are used.

Optional. The tool and every export work without this. No spam.

How to use the register

List each user defined column with its table, data type and business label. Add who uses it, such as a screen, report or integration, and name an owner. Enter total rows and populated rows from a query and the worksheet computes fill percentage. Use the action column to mark what to keep, document or retire. Export to Excel for review sessions.

Record the business label, not only the column
Name a human owner
Pull fill counts from the database
Check reports before retiring

Reading fill percentage

A high fill percentage on a table with many rows suggests an active, important field. A very low percentage may indicate a one time project field, a field used by a single team, or a field created and abandoned. Context matters, so low fill is a prompt to ask, not an instruction to delete.

UD fields versus UD tables

UD fields are columns added to existing tables such as parts or orders and suit a small number of extra attributes. When data is one to many, needs its own key, or has grown to dozens of fields, a UD table is usually cleaner. The action column includes Move to UD table to flag such cases for design work.

Common mistakes

Teams reuse a UD field for a second meaning when the first is forgotten, which corrupts reports. Others delete a field that a custom report, BAQ or integration still reads. Search your customizations and queries for each column before retiring, and keep a record of the old definition.

Frequently Asked Questions

What are UD fields in Epicor?

UD fields are user defined columns on standard tables, such as character, number, date and check box fields, that you label and show on screens through customization. They let you store extra data without changing the standard schema.

How do I count populated rows?

Run a query or BAQ that counts rows where the column is not empty for each table, and compare to the total rows. Do this per table, then paste the counts into the register. Numeric and check box fields need a rule for default values.

Is it safe to remove an unused UD field?

Only after checking every place that references it: screen customizations, BPM directives, reports, BAQs and integrations. Disable usage in a test system first, then keep a backup of the label and customization definition for rollback.

When should I choose a UD table instead?

Choose a UD table when the data repeats per parent record, has its own key, or needs many attributes. Adding many UD fields to a busy standard table makes the model harder to explain and test than a dedicated table.

If you want help finding where each UD field is referenced across screens, reports and queries, Netray can assist.

Talk to an Expert Explore More Free Tools

Related Tools

Epicor

More Epicor tools

See all

Back to All Tools