Autonaming Rule Not Reflecting After Changing Naming Rule in Doctype

Frappe Framework
, ,
1

I am experiencing an issue where the autonaming rule for a custom Doctype (Physical Audit) is not updating as expected after modifying the naming rule in the Doctype configuration.

Here are the details:

  1. Issue:
  • I changed the naming rule for the Physical Audit Doctype to use a new format: {node_details}_{DD}_{MM}_{YY}_{####}.
  • Despite this change, when I save a new record, the name still gets generated with the old prefix: state_24_12_12.
  • The new autonaming format is not being applied.
  1. Steps Taken:
  • Verified the naming rule in the Doctype settings (it’s correctly updated to the new format).
  • Ran bench migrate to ensure database schema and configuration changes are applied.
  • Tried uninstalling and reinstalling the app where the Doctype resides.
  • Verified that there are no custom server scripts or client scripts interfering with the autoname logic.
  • Checked for possible cache issues, including restarting the server.
  1. Environment:
  • Frappe version: 15.48.0
  1. Expected Behavior:
  • When saving a new record, the generated name should follow the updated autonaming format ({node_details}_{DD}_{MM}_{YY}_{####}).
  1. Actual Behavior:
  • The saved record continues to follow the old naming format (state_24_12_12).
  1. Additional Notes:
  • I have ensured that there is no custom logic or override in place for the autoname method.
  • This issue persists even after clearing caches and restarting the server.

I am looking for guidance or troubleshooting steps to resolve this issue. Any help would be appreciated!

2

Please check the Property Setter DocType by applying the filter for your custom DocType. If any records exist for your custom DocType (Physical Audit), delete them.

3

@ejaaz Yes There was a record in property setter which was doing this.
Thanks for pointing correctly