In order for me to understand the architecture and systematics of ERPNext I make some customization.
When I edit/customize a doctype and change the Module from one module to another, in the new module there is a new folder created with the name of the doctype (with some files in it). But the doctype’s py file is still empty.
And in the old module, the doctype’s folder is still exist (with all the standard files).
Is this new doctype a symlink? Because when click on the menu page, it opens the same (standard) doctype.
If I want to make customization, should I do it in the new or standard doctype?
If I wan to create a new module for the sidebar menu, is this the correct way to do?
Should I also move (and merge) the standard doctype folder to the new module?
better to create a new apps for new module. why? when you create a new module for apps that already there thats mean you are modifying the apps. when there is a new version for thats app you will have trouble when updating
creating a 2nd module for the apps that you create will need to execute bench migrate and update desktop.py for it to show on the system.
if the current module only have a couple thing that you want its better to create a new doctype than modifying
Back to this question.
This happen even when I’m not creating new module/app. I only change the module owner of a doctype in the dictype customization, for example change doctype Item from Stock module to Asset module.
In the Asset module will occur a new folder called Item with some basic files. But in the Stock, the original Item folder still exist.
Is the new Item in the Asset a symlink?
If I want to make custom doctype or report or other, should I put it in the Stock’s Item or Asset’s Item?