MRPeasy Custom Fields
mrpeasy custom fields
Also searched as
- mrpeasy add custom field to item
- mrpeasy custom attributes customer order
- mrpeasy user defined fields
- mrpeasy custom field report
Short answer
MRPeasy lets administrators extend records with additional fields in its settings, so you can store information such as drawing revision, customer part number or inspection class on items and documents. Availability by record type and plan varies, so confirm in your account, and remember that a custom field stores data but does not by itself change planning logic.
Applies to: MRPeasy cloud; the set of records that accept custom fields and how they appear in reports and the API depends on release and plan
How to add and use a custom field
- 1Decide the purpose of the field: information only, a filter, a value printed on documents, or a value an integration reads.
- 2Open the settings area as an administrator and look for custom field or additional field configuration for the record type: items, customer orders, manufacturing orders or others.
- 3Choose a name and a data type that matches the use: text, number, date or a pick list when you need consistent values.
- 4Add the field to the record layout and to the grid columns, so users see and filter on it.
- 5Populate existing records by import where possible, rather than by hand, so data is complete.
- 6Add it to printed documents if it must appear on quotes, packing slips or work instructions.
- 7Test whether it appears in exports and in the API response before you build a report or integration around it.
What a custom field can and cannot do
A custom field is data. It lets you filter, search and print. It does not add planning rules, change a BOM explosion or block a shipment. If you need behavior, such as holding an order until an approval, use the available statuses, roles and workflow settings, or handle the rule outside in your own process.
Use pick lists for anything you will report on. Free text produces spellings like Rev A, rev a and A, which are three groups in every pivot table.
Items, orders and bills of materials
On items, typical fields are customer part number, drawing revision, material specification, country of origin and inspection class. On customer orders, it is common to keep customer purchase order line references and delivery instructions. For BOMs, fields rarely help, since the structure itself should hold the data; put the information on the item that the BOM line points to.
Keep the list short. Each additional field is another thing to maintain, train and clean, and every integration has to decide whether to carry it.
Reporting and API implications
Check whether the field is included in the grid export, in standard reports and in the REST API output. If it is exported, a spreadsheet or BI tool can use it right away. If it is not, you may need a different place to store the value, or a support request to the vendor.
When you integrate with Xero, Shopify or another system, map the custom field explicitly. Connectors rarely carry it by default.
Try it here, free
MRPeasy vs Katana Selection Scorecard
A 10-question fit test that scores how much planning depth and shop floor control your operation needs, to compare MRPeasy and Katana style cloud MRPs.
Common pitfalls
- !Using free text for values you need to filter or report on.
- !Creating fields for one-off needs and never retiring them.
- !Expecting a custom field to drive planning or approvals.
- !Not checking API and export visibility before building an integration.
- !Different teams using the same field for different meanings.
How an ERP-grounded AI assistant handles this
A private assistant can read the exported records, find inconsistent values in a free-text field, such as revision spellings, and propose a pick list and a cleanup file for you to approve. It runs on your own infrastructure, so the item master stays inside your network.
Frequently asked questions
Can I add custom fields in MRPeasy?
MRPeasy supports extending records through its settings, though which record types and field types are available depends on your plan and release. Look in the administrator settings and check with support if it is not visible.
Do custom fields appear in reports?
Often in grids and exports, but standard reports and the API may not include every field. Verify in a test before you rely on it for reporting.
Can a custom field change planning?
No. It stores information. Planning uses quantities, dates, lead times, BOMs and reorder rules, so use those standard structures for behavior.
Should I use text or a pick list?
Use a pick list for values you filter or report on, since consistent values are what make the field useful. Use text only for notes.
Related
MRPeasy Xero Integration (and Shopify)
MRPeasy offers integrations with Xero for accounting and with Shopify for sales orders and stock. In general, Xero receives invoices and related accounting documents from MRPeasy, and Shopify sends orders into MRPeasy while MRPeasy sends available stock back. Check the current integration documentation for exact fields and limits.
How-toMRPeasy Forecasting, Trial, Support and Cancellation
MRPeasy plans from customer orders, stock levels and reorder rules, and works well when demand is mostly known orders. It is not a statistical forecasting engine, so teams with forecast-driven demand usually add a spreadsheet or an external model. This page also covers trial evaluation, support routes and how to exit cleanly.
How-toHow to Compare Planned vs Actual Cost in MRPeasy
MRPeasy builds a planned cost from the bill of materials, routing and rates, then records actual cost as materials are consumed and work is reported on the manufacturing order. To find a variance, compare the two on the order itself and then drill into material price, quantity used, and time booked.
How-toKatana MRP Integrations and the MRPeasy REST API
Katana and MRPeasy both offer native connectors for common sales channels and accounting systems, plus a REST API for everything else. Use the native connector for orders and stock sync, and the API for custom reports, ERP links and missing fields. Always check which direction each connector syncs and what it ignores.
How-toHow to Create a Generic Inquiry in Acumatica
Generic Inquiries (GI) are Acumatica's no-code query builder for joining tables, adding filters, and exposing the result as an inquiry screen, dashboard data source, or API endpoint. Open System > Customization > Generic Inquiry, add your base table, define joins and conditions, then run and save. No SQL or customization project is required.
Error fixFix Odoo AccessError: You Are Not Allowed to Access Records
Odoo raises AccessError when a user's security groups do not grant a CRUD right on a model through ir.model.access.csv, or when an ir.rule record rule filters the specific record out for that user or company. Fix it by adding the user to the group named in the error, editing the model's access rights, or reviewing the record rule's domain under Settings > Technical > Security.
AI for ERPAI for MRPeasy Manufacturing ERP
Add private AI to MRPeasy: natural-language answers over production, inventory, and lot traceability data, plus MRP exception and PO follow-up agents, without a public AI reading your data.
AI for ERPAI for Katana Cloud Manufacturing
Add private AI on top of Katana: natural-language answers across Katana, Shopify, and QuickBooks Online, plus agents for reorder points and channel demand, without a public model reading your data.
Stuck on MRPeasy?
Talk to engineers who work inside MRPeasy every week, and who build private AI that answers these questions from your own ERP data.
Keep exploring
Free tools
- MRPeasy vs Katana Selection ScorecardA 10-question fit test that scores how much planning depth and shop floor control your operation needs, to compare MRPeasy and Katana style cloud MRPs.
- Epicor User Defined Field Register WorksheetA register of UD fields with table, column, label, owner and populated row counts. Spot unused fields and export to Excel.
- SyteLine Item Master Fields ReferenceSearchable list of important item_mst fields with typical values and what each one drives in planning, costing and inventory.
ERP fixes and how-tos
- MRPeasy API documentation: authentication, endpoints and examplesHow the MRPeasy REST API works: generate a key, authenticate, call endpoints for orders, items and stock, page results with ranges, and handle rate limits.
- How to Compare Planned vs Actual Cost in MRPeasyHow to compare planned and actual cost on MRPeasy manufacturing orders, find why a product cost looks wrong, and trace material, labour and overhead variance.
- MRPeasy Materials Shortage: Plan Purchases CorrectlyHow MRPeasy flags material shortages on customer and manufacturing orders, how booking works, and how to turn shortages into purchase orders with correct lead times.
Guides
- How to Add User Defined Fields in SyteLineComplete guide to adding user-defined fields (UDFs) in Infor SyteLine, covering database column creation, IDO property mapping, form placement, and reporting integration.
- Infor LN Studio Development: Building Extensions Without Upgrade PainInfor LN Studio development guide: 4GL sessions, DALs, LN Extensions, and CDFs - how to customize LN without source modifications that break upgrades.
- SyteLine User-Defined Fields Implementation GuideImplement SyteLine user-defined fields correctly. UDF architecture, data types, form integration, and reporting considerations for CloudSuite Industrial.
Integrations
- How to use ChatGPT with MRPeasyThree ways to use ChatGPT with MRPeasy: export and upload, a custom GPT with API actions, or a private model. Setup, limits and data-control trade-offs.
- How to add AI agents to MRPeasyHow to add AI agents to MRPeasy using its REST API: PO expediting, shortage triage and quote drafting, with human approval before any write-back.
Software
- MRPeasyMRPeasy is a cloud MRP and ERP system for small manufacturers. See its modules, integrations, limitations and alternatives for shortlisting.
- KatanaKatana is a cloud inventory and manufacturing system for small product makers. See its modules, integrations, limits and alternatives before you choose.