Custom fields: adding information with a clear definition

A custom field captures information that the standard record does not represent adequately. It is useful when the business can define what the value means, who supplies it and how it will be used. Adding a field without a decision or reporting purpose creates maintenance work rather than knowledge.

The field type should fit the information. A controlled choice supports consistent categories; free text supports explanation. Using free text for a value that needs reliable comparison often produces spelling variations and ambiguous reporting.

Custom fields in DNA

DNA's Custom Fields setup requires a field name, type and at least one assignment. It supports type-specific configuration, a required setting, active state and optional PDF-display settings. Choice-based types require options, and other types have their own configuration checks.

The setup distinguishes the internal field name from its display label. A clear display label helps users, while a stable internal definition helps integrations and reporting. Changing a label should not be confused with changing the meaning of existing values.

Required does not mean correct

A required field can encourage completion, but a supplied value can still be inaccurate. If Northstar adds an “Installation category” field, the permitted categories need an agreed meaning and someone responsible for maintaining them.

The setup request records the required flag and assignments. It should not be assumed that every unrelated screen or historical record automatically gains the same validation or a populated value.

Review the full use

Check the field in its assigned transaction context and, where configured, in the resulting document. Consider whether a report or integration also needs the value and verify that particular use.

Avoid duplicate custom fields with slightly different names for the same concept. A useful field has a definition, an owner, appropriate choices and a clear role in the business process.