Naming Series pass_does_not_exist_error

Just updated to the latest. Once I navigate to naming series I get this error.

Traceback (most recent call last):
File “/home/test/frappe-bench/apps/frappe/frappe/”, line 55, in application
response = frappe.handler.handle()
File “/home/test/frappe-bench/apps/frappe/frappe/”, line 19, in handle
File “/home/test/frappe-bench/apps/frappe/frappe/”, line 36, in execute_cmd
ret =, **frappe.form_dict)
File “/home/test/frappe-bench/apps/frappe/frappe/”, line 879, in call
return fn(*args, **newargs)
File “/home/test/frappe-bench/apps/frappe/frappe/”, line 67, in runserverobj
frappe.desk.form.run_method.runserverobj(method, docs=docs, dt=dt, dn=dn, arg=arg, args=args)
File “/home/test/frappe-bench/apps/frappe/frappe/desk/form/”, line 38, in runserverobj
r = doc.run_method(method, args)
File “/home/test/frappe-bench/apps/frappe/frappe/model/”, line 661, in run_method
return Document.hook(fn)(self, *args, **kwargs)
File “/home/test/frappe-bench/apps/frappe/frappe/model/”, line 839, in composer
return composed(self, method, *args, **kwargs)
File “/home/test/frappe-bench/apps/frappe/frappe/model/”, line 822, in runner
add_to_return_value(self, fn(self, *args, **kwargs))
File “/home/test/frappe-bench/apps/frappe/frappe/model/”, line 655, in
fn = lambda self, *args, **kwargs: getattr(self, method)(*args, **kwargs)
File “/home/test/frappe-bench/apps/erpnext/erpnext/setup/doctype/naming_series/”, line 27, in get_transactions
AttributeError: ‘module’ object has no attribute ‘pass_does_not_exist_error’

Did some investigation and its throwing this error for ‘Time Log’ and ‘Time Log Batch’ which I believe has been removed already. However the entries still exist in tabDoc Field. Is there an existing patch that is supposed to remove these entries?

Does anyone know if Time Log and Time Log Batch entries are supposed to exist in tabDoc Field?

@bohlian thanks

@rohit_w can you send a patch to move Custom Field from Time Log to Timesheet to hotifx.

Also fix the rename_doctype feature.

Hi @bohlian,

Have fixed this issue and we’ll release it soon

Thanks, Rohit

@rohit_w @rmehta Thanks for this.