Customize Form DocType

1

in v15 i did a quick reco of the tables in MariaDB and the Doctypes
They were either a Doctype (tabXXXXXX), a single or a virtual. Even DocType has a tabDocType along with its child tables
Except for Customize Form
According to - Customizing DocTypes its only “a view that helps you easily customize DocTypes” so I assume its only python code. It lets you touch non sensitive fields (e.g. name is greyed out) in the Doctype so that links dont break

2 questions: -

  1. Is it upgrade safe (e.g v15 to v16) as it does not save it into Database tabXXXXXX (like tabCustom Field) so where does it save the data for upgrades/migrations? json?

  2. Any other documentation that shows what you can and what you cannot change?

Thanks

Customization form In Purchase Order
2

Hi @asieftejani

Customizations relies on

  • Custom field (new fields)
  • Property setter (properties of existing DocTypes or DocFields)

Custom doctypes definitions are stored too in database.
Upgrading will be safe if customization was made properly (avoiding code manipulation).

Hope this helps.

1 Like
3

Hi @avc

Whatever you have said is correct.

I was just a little confused as to why the “Customize Form” doctype is the only doctype not to have a corresponding “tabCustomize Form” table in the database

After some trial and error, I have figured out that this form actually uses the 2 you mentioned (custom field and property setter) and puts the data in those tables. So basically you can either use those two directly or this one as its more convenient and shows you the full doctype (e.g. you would need to know “reqd” for property setter as a developer while as a functional you can just tick “mandatory”).

Thanks again for your answer :folded_hands: