For core doctypes, what would happen if I change the Module to one of my custom apps and install it to another instance?
So far I found that the core doctype still exists in frappe-bench/apps/erpnext, and a new doctype was also created under my custom app directory.
Will there be any further conflicts down the road?
I have made some edits in core doctypes (not customize form, I know, thus cannot use property setter&fixtures), changing module seems like the only way to move the changes to another instance.
If there’s any other way to achieve this, I’d really appreciate. There’re too many edits to simply resume back to customize form and export customization.
Thank you so much! I totally overlooked the hooks. However, it seems to only override the .py and .js file. Is there a way to override the .json file for the core DocType in app? I am not planning to update my current instance.
I recommend you do this with fixtures, basically all the changes you made to the original erpnext doctype will be saved with the help of fixtures in your custom app. When loading this app into another instance the changes you made to the original doctype will be implemented.
Here is a video of Karani Geoffrey (the legend himself) explaining how to do this:
However there are some core doctypes that frappe does not allow to customize (for example doctype “User”). You can edit them, but this wont persist and will be gone on installing an update. However it is possible to export changes with fixtures, as described in this post: