# Acumatica: How to Make a Field Required > Source: https://netray.co/erp-help/acumatica-make-field-required-customization-workflow > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: ERP Help ## Short answer In Acumatica you make a field required with a customization project: use workflow field states for conditional rules, mark an attribute as required for item or customer classes, or use a DAC extension in code for an always-required field. Choose the least invasive route, test in a copy of the tenant, and publish the project. ## Kind how-to ## System small-erp ## Erp Acumatica Cloud ERP ## Module Customization / Workflow ## Query acumatica make field required ## Alternate Queries - acumatica required field customization - acumatica software pros and cons - acumatica locations warehouse - acumatica make field mandatory ## Applies To Acumatica Cloud ERP 2022 R2 and later, including MYOB Advanced in markets where it is sold; screens vary by edition ## Steps ### Make a field required **Items:** - Decide if the rule is always or conditional. Conditional rules, such as required only when status is On Hold, suit workflow. - Open a test tenant and a customization project (System > Customization > Manage Customization Projects) and create or open your project. - For a screen workflow rule, edit the workflow for the screen and set the field's state to Required for the relevant state or condition. - For class-driven data, use attributes and mark the attribute as required for the item class, customer class or other class that uses it. - For an always-required field, a developer adds a DAC extension that applies a required UI setting and a persisting check, then publishes the project. - Publish, and test creating and saving the record as a user in the target role, including via import scenarios and the API. - Document the rule and keep the project in source control. ## Sections ### Choosing the method **Body:** Workflow is best when the requirement depends on state, because it changes with the document and needs no code. Attributes work well for descriptive data tied to a class, and they are configured by administrators. A DAC extension is the most direct way to make a field always required, but it needs a developer and follows the code upgrade path. A required indicator on the screen alone is not enough: if the rule must also hold for imports and the API, enforce it at the data level, not just in the UI. ### Acumatica pros and cons for manufacturers **Body:** Strengths commonly cited: cloud or private-cloud deployment, a single database across modules, an open customization platform and a REST API, and a licence model based on resource usage rather than named users. Manufacturing is available as a separate edition, so confirm the capabilities you need before purchase. Weaknesses to weigh: manufacturing depth is narrower than long-established discrete ERPs for complex routing, advanced planning and regulated industries, and heavy customization needs an implementation partner. Fully on-prem hosting is less typical than cloud, so check what deployment options your agreement supports. ### Locations **Body:** People searching for Acumatica locations usually mean warehouse locations (bins) inside a warehouse, set up in Inventory configuration, which are different from company branches. Enable location tracking at the warehouse and item level before you rely on bin-level stock. Decide early whether you need bin tracking: it improves accuracy but adds transaction steps for receiving, moves and issues. ## 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. ## Ai Angle Before enforcing a new required field, an ERPray-style assistant can query existing records to show how many currently have the field blank, so you can clean data first. It reads through the Acumatica API or database with the user's roles, and is read-only by default. For private deployments, the model can run on your own servers, though Acumatica itself is usually hosted by Acumatica or a partner. ## Faq ### How do I make a field mandatory on an Acumatica screen? **Answer:** Use workflow field states for conditional rules, a required attribute for class-based data, or a developer-built DAC extension for an always-required field. Then publish the customization project and test as a normal user, not an administrator. ### Will a required field apply to imports and the API? **Answer:** Only if it is enforced at the data level. A purely visual required marker applies to the screen. A persisting check in a DAC extension also applies to import scenarios and the API, so choose by where the rule must hold. ### What are Acumatica's pros and cons? **Answer:** Pros include a modern cloud platform, open API and flexible licensing. Cons can include narrower manufacturing depth for complex or regulated environments and reliance on partners for deeper customization. Test your own scenarios in a trial before deciding. ### What are locations in Acumatica? **Answer:** Usually warehouse locations, meaning bins inside a warehouse, configured in the inventory setup. They are different from branches or companies. Enable location tracking deliberately because it adds steps to receipts, moves and issues. ## Search terms acumatica make field required, acumatica required field, acumatica mandatory field, acumatica workflow required, acumatica software pros and cons, acumatica locations, acumatica customization project, acumatica attributes required --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json