Dear Friends kindly help me runover the doubts, I have customized the Purchase Order form in ERPNext by adding a new table field to attach product specification images. This customization was done using the “Customize Form” option. When we customize a form using this standard method . If any update was give by Frappe does the customization done form will be corrupted are not . It will be same as after the update
Kindly Resolve the doubt.
Hi @Barath_24
I had the same question - Customize Form DocType
Better check out
Personally I dont think it will work as I dont see it being saved anywhere to be restored after an update or disaster recovery
Better you try on a test site and report your findings back here for the benefit of everyone
Alternatively you can ask the one who replied to my question to get full crystal clear clarificaiton
Hi @Barath_24 ,
When you “Customize Form”, the changes you make are saved in the SQL database only. This is what keeps them separated from the official document schemas.
Later when you update the software, those official document schemas may change. But because your Customization exist only in the databse, they remain as-they-were.
This means that (usually), there’s no corruption. However … it’s still possible. For example, perhaps you customized a Field that no-longer-exists in the newest version. Or maybe your custom field was in a Section Break, Column, or Tab that was officially deleted, renamed, or moved.
One final consideration: because your customizations only exist in the database, they are not monitored and tracked by git source control. There’s a risk you could lose them someday. To avoid this:
- Make sure you’re taking database backups regularly.
- You can export your customizations as “fixtures”. Which is strange term that essentially means “writing SQL rows to disk”. Which in your case would be Customizations. But fixtures could also represent business transactions, reports, permissions, or configuration settings. It’s a little tricky to wrap your head around initially.
Thank you for your response to my question.