Custom DocTypes and Additional Form Fields on Update

[Finny_Philip]

Hi community,

We were really fascinated by ERPNext as I stumbled across it while looking to build a database system for our small nonprofit. We are mainly looking to work on it as a no-code tool with the existing nonprofit app, with some customizations. Had a few questions about it, however, and it would be a big help if someone from this wonderful community could answer those queries.

1. If we create a new custom doctype, will that get erased on the next frappe/erpnext upgrade (minor and major-version upgrade, both)?

2. If we add additional fields to an existing doctype that came prepackaged with erpnext, will those additional fields, and the data associated with them, get erased with the next frappe/erpnext upgrade (minor and major-version upgrade, both)? We will be using the Customize Form option to add fields to the existing doctypes.

3. We created a new custom doctype with some fields, and we want to give access to some admin users to add more fields to it, in case it is required. We want to do it through the “Customize Form” option, rather than the “Doctype” option, for security reasons. But we couldn’t locate the newly created doctype in the “Customize Form” option.

I realize it’s quite a bit of queries, and it will be a big help, and we would be really grateful, if the community could point us in the right direction.

Warm regards,

Finny

[Suresh_Thakor]

@Finny_Philip , Please find your answer in this thread. Hope your doubts will clear.

What is an effective ERPNext Implementation workflow for a small team?

We’re two people (Functional Implementer and a Developer). This is a learning experience for both of us. We’re currently doing an implementation for a client. The functional implementer was working on his instance at first. In the beginning, he created some custom DocType. When there was a development requirement, I took a backup of his instance and replicated it locally before I wrote a custom app. I set some of those new Doctypes under this module (the ones that made logical sense), so I have…

[Finny_Philip]

@Suresh_Thakor Thanks for your prompt response.

So, if I’m understanding it correctly–I need a developer in-house/on-call, if I’m looking to work on ERPNext with some customizations that can be done using custom doctypes and additional fields in the forms? Is there any way to use it entirely as a no-code solution?

Thanks, once again, for the help!

[Suresh_Thakor]

Yes, you can implement ERPNext yourself if there is no more logic required.
Even here is a good thread also available for Learning purposes posted by the best contributor.

Thanks.

[Finny_Philip]

Thanks for replying again.

So can I assume that the custom doctypes added by me, and the custom fields I add to the preset doctypes (using the customize form option), will not be deleted when ERPNext/Frappe is updated?

Is there any way to get the custom doctypes to show up in the “Customize Forms” option so that I can allow some users to add fields without editing the custom doctype itself?

Thank you, once again, for all the help.

[Suresh_Thakor]

Yes, Customize will save in the Database.

If you need changes to be applied on another site then you will have to manage the custom app with the GitHub repository.

Find one more thread. Credit goes to @brian_pond.

Guidance to work with Forks on Github for ERPNext only

This is a complicated topic. I will try to summarize the 4 different approaches, beginning with the least-complex scenario. 1. Making changes with the “Customize” button. To make simple modifications (changing a DocField’s label, adding a new Naming Series, adding a DocField to an existing DocType), you may decide to use the Customize button. When using this button, your changes are saved –in the SQL database– of your Site. The ERPNext code itself is not touched. So no git logs. (Except…

Thanks

[Finny_Philip]

Thanks again @Suresh_Thakor for a prompt reply! This is, indeed, very helpful.

The community is all the more better because of you!