Migrated Data made the custom Doctypes in the new bench unedittable

Keyur_Paraskar · January 16, 2024, 12:57am

I got an error while replicating my ongoing frappecloud site onto a local site.

frappe.exceptions.CannotChangeConstantError: Value cannot be changed for Created By

Here is what I did till this point,

I downloaded my backup files (db, public,private) from my ongoing site hosted on frappecloud.
Installed frappe’s container setup on a vm ubuntu(23.04).
Built bench, frappe, erpnext, localsite using the ./development/installer.py
ran bench --site sitename.localhost migrate with --db…{path} --private…{path} --public…{path}
This ran successfully with no errors.
Now when I access the desk mode of my localsite and try to edit a custom doctype I had built earlier on the cloud, It shows me the above error.
I could create new doctypes, but some of my existing server scripts also errors out on several different reasons.

Is this a migartion issue? Am I missing some steps?

Nasir_Khan · January 16, 2024, 8:57am

@Keyur_Paraskar , please turn on the developer mode by following:

bench --site site_name set-config developer_mode 1

Keyur_Paraskar · January 16, 2024, 2:20pm

@Nasir_Khan, Thanks for the prompt response! Setting the developer mode on fixed the issue with server scripts discrepencies. Although I still get the following error when trying to edit an existing custom doctype.

Jiri_Sir · January 16, 2024, 8:24pm

Hello,
I used to have very similar problem.

I used “dirty” workaround: go to frappe core code: frappe/frappe/model/document.py and delete this section (row 646 - 652):

github.com

frappe/frappe/blob/642e9f4ec1cf4d90e4484bc39b279e8c28f9f8a2/frappe/model/document.py#L646C1-L652C7


      
          				if fail:
          					frappe.throw(
          						_("Value cannot be changed for {0}").format(
          							frappe.bold(self.meta.get_label(field.fieldname))
          						),
          						exc=frappe.CannotChangeConstantError,
          					)

Then I save the changes in custom doctype and then I put the above section back for “clear” core.
Next savings in custom dcts are ok.

If anyone has a better solution, I’d love to know it
Jirka

Keyur_Paraskar · January 17, 2024, 5:55pm

@Jiri_Sir, Great workaround, thanks! This should work for me right now.

Just a heads-up to someone implementing this: make minor changes to “all” custom doctypes while the code snippet is commented out.

Abdullah_Yassin · March 31, 2024, 3:33am

It’s really “dirty” but it’s works!

Jake · February 8, 2025, 7:40pm

Another heads up, since it’s “cached”(probably wrong term) in init.py…

I tried all the usual migrate/restart/clear-cache/down/up etc on a bare metal install and it didn’t work. I’m sure there’s a more elegant solution… but after deleting(read:commenting out) those lines I rebooted the server to make it work.