Acumatica: How to Make a Field Required

Make a field required

1. 1Decide if the rule is always or conditional. Conditional rules, such as required only when status is On Hold, suit workflow.
2. 2Open a test tenant and a customization project (System > Customization > Manage Customization Projects) and create or open your project.
3. 3For a screen workflow rule, edit the workflow for the screen and set the field's state to Required for the relevant state or condition.
4. 4For class-driven data, use attributes and mark the attribute as required for the item class, customer class or other class that uses it.
5. 5For an always-required field, a developer adds a DAC extension that applies a required UI setting and a persisting check, then publishes the project.
6. 6Publish, and test creating and saving the record as a user in the target role, including via import scenarios and the API.
7. 7Document the rule and keep the project in source control.

Acumatica pros and cons for manufacturers

Common pitfalls

• !Making a field required in the UI only and finding imports and API calls still save blank values.
• !Testing as an administrator only.
• !Customizing in production without a test tenant.
• !Conflicting projects that override each other.
• !Enabling bin tracking without training receiving staff.