How migrate changes to erpNext doctype

[Orlando_R_Curieles_V]

Hi, I created some fields on Customer doctype, how can migrate this changes to my production environment ?

[James_Robertson]

I don’t know of an automated way to do this. Right now I just do it manually by documenting what changed in dev and then doing same changes in prod. This would be great to know if it can be done automagically.

[revant_one]

If you have custom app checkout fixtures. Any Doctype can be exported as a fixture.
Useful for Custom Field, Property Setter, Print Format DocTypes

https://frappe.github.io/frappe/user/en/guides/app-development/how-to-create-custom-fields-during-app-installation

using filters for fixtures in hooks.py

Fixtures Support - filters

Hi Frappe team. As you know i made two apps, Base Vat and Jasper Erpnext Report. The problem is when i export fixtures (Custom Field) the fixtures of Jasper Erpnext Report get mix with fixtures of Base Vat and the other way around. So when i update my apps people get Custom Fields that they do not want. If they install only Base Vat then they get also the Custom Fields of Jasper. If we all made apps with fixtures then the problem propagates. So, the solution in my view is simple: just change …

It is easier to import Custom Script into fixtures by adding them to custom_scripts folder. Name the files as per the doctypes on which custom script is to be imported. Also remove Custom Script from fixtures in hooks.py or it will try to import Custom Script twice, once from custom_script.json and once from custom_scripts directory

e.g.