When bulk edit fails in ERPNext v16, it is usually one of five things. The Actions button moved in the v16 List View redesign. A posting date resets because "Edit Posting Date and Time" is not ticked. A select-only role trips v16's tighter field permissions. Status is driven by actions, not an editable field. Or a custom has_permission hook returns None, which v16 reads as a denial. None of the fixes needs direct database surgery.
Bulk edit failures are quiet: no error toast, no console log, the dialog closes and the records look unchanged. The v16 tickets we have seen in this category have come down to one of the five below. I lead ERPNext and Frappe implementations at MithTech, a team of Frappe specialists in Bengaluru. This is the diagnostic order we use.
What are the five causes at a glance?
| Symptom | First check | ||
|---|---|---|---|
| 1 | Actions button moved in the v16 List View | "The button disappeared after the upgrade" | Tick a row's checkbox first |
| 2 | Posting date reset without "Edit Posting Date and Time" | Bulk edit accepts the date, the records keep the old one | Is set_posting_time ticked on the documents? |
| 3 | v16 select-only field permissions | You do not have permission to access field: X in the console | Retry as Administrator; if that works, it is the role |
| 4 | Status follows actions, not an editable field | status missing from the bulk-edit field picker on Sales/Purchase Order | Look for Close / Re-open in the Actions menu |
| 5 | Custom has_permission returns None on fall-through | Some rows update, some do not | grep def has_permission in every custom app for a missing return True |
The rest of the post takes one cause per section, with the fix.
Where did the Bulk Actions button go in ERPNext v16?
Answer
It moved. The v16 List View removed the right sidebar and put bulk operations in an "Actions" button that appears only after at least one row is ticked. If you never see the button, nothing is selected; that is the whole problem in many "bulk edit disappeared in v16" tickets.
Frappe's Migrating to version 16 notes record the change: the List View's right sidebar was removed to make better use of the screen, and saved filters moved to the top of the list.
If your users are on v16 and cannot find bulk actions:
- In any List View, tick the checkbox in the leftmost column of at least one row.
- Look at the toolbar above the list (there is no list sidebar any more).
- The Actions button appears with the count of selected rows. Click it for the bulk menu.
If Actions never appears even after selecting rows, the redesign is not the problem; work down the rest of the list.
Why does a bulk-edited posting date not stick?
You bulk-select Delivery Notes, choose Actions → Edit, pick a new posting date and click Update. The dialog closes without complaint, but the dates are unchanged. This was reported as Issue #45881 and closed in March 2025 with the explanation: on stock and accounting documents, ERPNext only keeps a posting date you set when Edit Posting Date and Time (set_posting_time) is ticked; otherwise it resets the date to today on save. Bulk edit changes one field at a time, so it cannot tick that box and change the date together.
Two ways to change the dates on draft documents:
A. Data Import (no code). Export the drafts, set both set_posting_time = 1 and the new posting_date in the file, then import with "Update Existing Records". This is the route the issue's maintainers suggest.
B. A bench console loop (admins). Set both fields together, and only on drafts:
import frappe
new_date = "2026-09-01"
names = ["DN-2026-00001", "DN-2026-00002", "DN-2026-00003"]
for name in names:
doc = frappe.get_doc("Delivery Note", name)
if doc.docstatus != 0:
continue # submitted: cancel and amend instead
doc.set_posting_time = 1
doc.posting_date = new_date
doc.save()
frappe.db.commit()
Run it from bench --site your-site.local console. Never rewrite the posting date of a submitted document directly in the database: its stock and GL entries keep the old date. For submitted documents, cancel and amend.
The same applies to other documents with "Edit Posting Date and Time": Sales Invoice, Purchase Invoice, Purchase Receipt and Stock Entry.
Why do I get "You do not have permission to access field" on v16?
The error You do not have permission to access field: Employee.status (with any field name) appears on v16 for roles that worked on v15. The forum thread (January 2026) and the matching Frappe issue #36280 show the repro: a Manufacturing User with only select on Employee picks an employee in a Job Card time log, and the link filter on employee.status fails. Frappe's maintainers called it expected behaviour after a security fix: a select-only role can no longer read other fields of the linked record.
Three fixes, in order:
- Upgrade Frappe to v16.10.0 or later. PR #37316 ("allow filtering by all permlevel 0 fields with select permission") shipped in Frappe v16.10.0 (February 2026) and covers the common link-filter cases.
- Add the referenced field to the linked DocType's search fields (Customize Form → Search Fields). Frappe's maintainers suggested this for users who must keep select-only access.
- Grant read on the linked DocType if the user should see its fields anyway.
The forum's "grant read on Workflow State" workaround only applies when a workflow is involved; it is not the general answer.
Why can't I bulk-update Sales Order status?
Actions → Edit does not offer status on Sales Order or Purchase Order, by design. Status on these documents comes from their lifecycle (Draft → To Deliver and Bill → Completed, and so on) and moves through actions like Submit, Close, Re-open and Cancel. Writing status directly would desynchronise it from docstatus and the child rows.
The common bulk need, closing or re-opening many orders, is built in from v16. Issue #49740 asked for it, and PR #50967 (merged December 2025) added Close and Re-open to the Actions menu of the Sales Order and Purchase Order lists. Tick the orders, then Actions → Close.
For a transition ERPNext does not offer, add your own action from a custom app's list script. Keep the standard onload, or you will remove the built-in actions:
// your_app/public/js/sales_order_list.js (doctype_list_js in hooks.py)
const settings = frappe.listview_settings["Sales Order"];
const standard_onload = settings.onload;
settings.onload = function (listview) {
if (standard_onload) standard_onload(listview);
listview.page.add_action_item(__("My Transition"), () => {
listview.call_for_selected_items("your_app.api.my_transition", {});
});
};
Put a confirmation and a permission check in your_app.api.my_transition: a bulk transition cannot be undone with one click.
Is your custom has_permission hook silently blocking the bulk action?
Many custom apps that added a has_permission hook on v15 have code of this shape:
# your_app/permissions.py
def has_permission(doc, ptype, user):
if some_condition(doc, user):
return True
# implicit None → v15: allowed the bulk action, v16: silently denies
Frappe's v16 migration notes say has_permission hooks must now explicitly return True (frappe#24253); None counts as a denial. When a user runs Actions → Edit on 30 rows and the hook returns None for some of them, those rows are not updated. The user sees "some rows updated, some didn't" and concludes bulk edit is broken.
Fix: audit every custom has_permission for a missing return on the fall-through path. If access is meant to be allowed there, add return True explicitly. The full change and grep pattern are in the v16 custom-app fix ladder.
What is the diagnostic order for a "bulk edit not working" ticket?
0 of 6 steps done
Tick a step’s number when it is done; the ticks stay on this device.
Confirm the user is selecting rows first
Ask for a screenshot after ticking at least one checkbox. If the Actions button appears, the "missing button" was the redesign, not a bug. If it does not appear after selection, continue.
Reproduce the specific field and DocType
Ask which DocType and which field. If it is a posting date on a stock or accounting document, check "Edit Posting Date and Time" and go to the Data Import route; do not spend time on permissions.
Check the browser console
Open DevTools → Console before running the bulk action. A 403 with You do not have permission to access field: X is the v16 select-only permission change; go to that section. A quiet 200 with no change is a posting-date reset or a has_permission denial.
Try the same action as Administrator
If Administrator can bulk-edit the same rows, the gap is in the user's role: the select-only change or a custom has_permission denial. If Administrator also fails, it is the posting-date rule or the status case.
Grep custom apps for has_permission with implicit None
For each app, check permissions.py and any file referenced by has_permission in hooks.py: grep -n "def has_permission" ., then read each function's fall-through. Any function without an explicit return True or return False at the end is a suspect.
Use the built-in action, Data Import or a script
For status, use Actions → Close / Re-open. For posting dates, use Data Import or the console loop above. Both are safer than forcing the bulk-edit dialog to do something it cannot.
FAQ
Is ERPNext v16 bulk edit broken across the board, or only on specific fields?
Only in specific cases. Bulk edit works for most DocTypes and fields on v16. The failures cluster around posting dates (which need "Edit Posting Date and Time"), select-only roles reading linked fields, status on Sales and Purchase Orders, and custom has_permission hooks.
Will a v16 point release fix the posting-date bulk edit?
There is nothing to fix upstream: Issue #45881 was closed in March 2025 as working as designed. Use Data Import with both set_posting_time and posting_date, or the console loop, for drafts.
Can I add my own bulk actions to the v16 List View?
Yes. listview.page.add_action_item still registers a custom bulk action, and the new toolbar picks it up. Chain the standard onload rather than replacing it, as in the example above, so the built-in actions stay.
Does the v16 permission change affect the API too, or just the desk?
Both. The You do not have permission to access field: X error comes from the permission layer, so a frappe.client call from a script, an external system or a form will raise it on a select-only role. The fixes (Frappe v16.10.0+, search fields or read permission) cover both.
Comments & ratings
No comments yet. Start a new discussion.
Manoj · Published on 9 August 2026
Worked with us? Leave a Google review