Frappe Controllers

Called in this order:

On insert (new document)

1. before_insert
2. before_naming (before name is set)
3. autoname (custom naming logic — self.name is set after this)
4. before_validate
5. validate
6. before_save
7. (db insert)
8. after_insert
9. on_update
10. after_save
11. on_change

On update (existing document)

1. before_validate
2. validate
3. before_save
4. (db update)
5. on_update
6. after_save
7. on_change

On submit (submittable DocTypes)

1. before_validate
2. validate
3. before_save
4. before_submit
5. on_submit
6. on_update
7. after_save
8. on_change

On cancel

1. before_cancel
2. on_cancel
3. on_change

On delete

1. on_trash
2. after_delete

Common patterns

Set defaults before validation

def before_validate(self):
    if not self.currency:
        self.currency = frappe.defaults.get_global_default("currency")

Throw validation errors

frappe.throw("Error message")                    # general error
frappe.throw("Message", frappe.ValidationError)  # with exception type

Access current user

frappe.session.user  # email of logged-in user

Set field values

def before_save(self):
    self.full_name = f"{self.first_name} {self.last_name}"

Interact with other DocTypes

def on_submit(self):
    frappe.get_doc(
        doctype="Notification Log",
        subject=f"Expense {self.name} approved"
    ).insert(ignore_permissions=True)

Access flags

# Set a flag to skip validation in specific cases
doc.flags.ignore_validate = True
doc.save()

Anti-patterns

• Don't use frappe.db.set_value for fields with validation logic. It bypasses validate(), before_save(), and all lifecycle hooks. Never use it for status fields or state transitions. Use it only for simple counters, timestamps, or cached values.

  # BAD — skips controller validation
  frappe.db.set_value("Expense", name, "status", "Approved")
  # GOOD
  doc = frappe.get_doc("Expense", name)
  doc.status = "Approved"
  doc.save()
  

• Don't call frappe.db.commit() in controller methods or request handlers. See the Transactions section in database reference.
• Put permission checks inside controller methods, not in API wrapper helpers. This ensures enforcement regardless of call path (API, desk, background job).

  # BAD — check in api.py wrapper
  def _get_manager_doc(name):
      if "Expense Manager" not in frappe.get_roles(): ...
  # GOOD — check in the controller method itself
  class Expense(Document):
      @frappe.whitelist()
      def approve(self):
          if "Expense Manager" not in frappe.get_roles():
              frappe.throw("Not allowed", frappe.PermissionError)
  

• Be consistent with permission checks across all controller methods. If some methods on a DocType check for a role explicitly, all mutating methods should do the same — don't rely on implicit DocType perms for some and explicit checks for others.