ERPNext custom fields and Customize Form
Adding fields and changing standard forms in ERPNext without code: custom field types, fetching values from linked masters, property setters and what survives upgrades.

Specific ways to adapt ERPNext without forking it: custom fields, client and server scripts, custom apps, exported customizations, print formats, reports, web forms and automation.
Adding fields and changing standard forms in ERPNext without code: custom field types, fetching values from linked masters, property setters and what survives upgrades.
Adding browser-side behaviour to ERPNext forms: when a client script is enough, common patterns such as field filters and custom buttons, and testing across browsers.
Running Python on document events or as API endpoints without a custom app: server_script_enabled since version 15, the restricted environment and when to move logic into an app.
When ERPNext changes belong in a custom app: scaffolding with bench new-app, DocTypes, hooks for overriding and extending ERPNext, version control and deployment.
Getting customizations out of the database and into git: Export Customizations, custom folders in app modules, sync on migrate and the overwrite behaviour to plan for.
Designing invoices, delivery notes and reports for print in ERPNext: the version 16 Print Format Editor, Jinja HTML formats, Chromium and Typst PDF engines and the wkhtmltopdf removal.
Choosing the right report type in ERPNext: no-code Report Builder with group by, SQL query reports, Python script reports in an app, and report permissions.
Designing document numbering in ERPNext: naming series patterns with year and company, tax-rule numbering, changing the current value and avoiding gaps and duplicates.
Collecting data from outside users with ERPNext web forms: login versus guest forms, which DocTypes to expose, list views for portal users and permission checks.
Automating routine steps in ERPNext: when a notification, webhook, assignment rule or server script fits, and multi-step Automation Flows with waits and branches.
Creating DocTypes, scripts and pages in the UI and shipping them as a package to other sites: custom modules, README and license, and when to graduate to a full app.

Tell us what you're working on, whether it's a deployment, an audit, a security test or a cyber range. You'll speak with an engineer who can help you scope it.