This question has been flagged
1 Reply
6275 Views

For example, I created a new date field in sales order form in a staging test branch. I need to get this change made in my production branch. A drag/drop merge doesn't work because it says there is nothing to merge.

I think I found instructions in the help documentation, but I do not understand what it is telling me to do. Can anyone expand on these instructions?

If you test configuration changes in staging branches, and want them to be applied in the production, you have to either:

  • write the configuration changes in XML data files overriding the default configuration or views in your branches, and then increase the version of your module in its manifest (__manifest__.py) to trigger the update of the module when you merge your staging branch in your production branch. This is the best practice for a better scalability of your developments as you will use the Git versioning features for all your configuration changes, and therefore have a traceability for your changes.
  • pass them manually from your staging to your production database, by copy/pasting them.
Avatar
Discard
Best Answer

You can EXPORT the Odoo Studio customizations, and then IMPORT them into the Production database.



Also, since inside the ZIP file is an Odoo module, you can add this directly to the Odoo.sh code repository, test it and merge like you would any other code that is written.

Always check inside the module folder for a WARNING.TXT file and review anything that could not be exported.


I would also review the documentation on writing modules, using GitHub and using Odoo.sh:

https://www.odoo.com/documentation/12.0/howtos/backend.html#build-an-odoo-module

https://guides.github.com/

https://www.odoo.com/documentation/user/12.0/odoo_sh/documentation.html

Avatar
Discard