migrate from openerp 5.0.6 all i n one to 5.0.15

Before anything backup your entire stuff - code and db etc

- Install the new software

Make sure the openeeerp server is stopped. Start it manually with the -u all parameters
enter into the db with the client and it will male the update.

I think this is described in the doc. See doc.openerp.com and search for the installation instructions for windows.

Good luck !

Christophe

Ps: note that this is for updating from 5.x to 5.y. Migration for example to 6.x will be either much more work or a maintenance contract

Hi Christophe,
   My problem is i have edited most of the modules such as mrp, sale, hr_payroll, etc in my openerp 5.0.6 addons files. How can i get these changes after installing 5.0.15. When we install the 5.0.15, new addons are in server. I believe that now you got my actual problem. Please help me to solve this....
Thanks n regards
sandra

Sandra, I am sorry for you... My answer will probably not please you.

If you changed your ERP through the client interface (e.g: adding a filed) Normally you are fine.

If you changed directly the provided module (in the source code)-> a lot of work, because you need to re-apply your modifications to the new source code (a source control system may help).

Normally, customization are done through addoc modules that iniherits from the base ones (in short). If you proceed that way, just put in place your custom modules when you finished the install and follow the standard update process.

I hope it helps

Christophe

Hi Christophe,
 We have done the customization through the source files itself. Is re-applying our modifications to the new source code is the only possible way to solve this issue? And this application is currently running and we have done a lot of customizations in the addons. What can we do, please help .....
Thanks and regards
Sandra

You can apply your changes to the new version with Bazaar for example :
- create a local branch from the branch in launchpad, using the tag "5.0.6"
- replace the files in your branch with the files that you changed
- commit to you local branch : bazaar will detect all the changes you made
- merge the Launchpad branch, using the tag 5.0.15 : bazaar will merge
all it can, an show you where the conflicts are.
Check out the community manual for more about Bazaar.
Lionel Sausin.

 doing so with py files will usually work out quite good,
xml files are more tricky and I had lot of conflicts especially when changing the order of the fields.

Hi all,

 It will be great, if you explain how to get and work with launchpad baazar ?

Thanks
Sandra

http://doc.bazaar.canonical.com/latest/en/mini-tutorial/

Hi Sandra,

If anyone hasn't mentioned it - you should probably not use an All-in-one for Production (to run your business) per many of the recommendations in the community. We recommend you only use the all-in-one to "kick the tires" and try the system out. Are you planning on using the 5.0.15 All in one as well?

Typically on windows you would install bazaar, and then the OpenERP Server, OpenERP Web Client (if you're using the web client) + maybe a proxy server(apache, nginx), and then the OpenERP GTK clients on the user's machines. Bazaar has a 5 minute tutorial that will get you started on the concepts. In WIndows, they have a workable Gui based system.

The recommended development approach when you make modifications is to leave the "core" of OpenERP alone - to make upgrades, applying bug patches to the base OpenERP code, etc, easier. You would modify the system using "inheritance". You should look to download and read the Technical Memento - and read the developer documentation on this approach.
Think of it this way - using inheritance allows you to "bolt-on or add additional functionality" - while the core engine keeps running versus customizing the "engine" itself.

One of the things to consider - How much "custom" development or changes did you have in the original modules? If it is not that much - it might warrant creating new modules with your changes. You'll still have the issue of moving the data as a result, but you could easily do this with some database work as well. In the end it would put you on a better path going forward versus jumping from All-in-one installations.

What you are experiencing right now is exactly what many companies have to go through using other Non-OpenERP systems. If you implement OpenERP in the recommended way (inheritance), you'll hopefully avoid some of the pain you're now faced with. We'd like to see you get on the right path - so you don't have this issue going forward - for instance when you move to v6.

There are many examples of modules using inheritance in the http://bazaar.launchpad.net/~openerp-community/openobject-addons/trunk-addons-community/files project. Everything from modules that add "single fields" to views to adding new functionality. That might be worth investigating . . .

Perhaps another thought and "path" might be to make your changes on top of version 6 and implement that when its out versus the 5.0.15 upgrade. You'll still be faced with migration work though.

I hope this is helpful.

Hi all,
 Thanks for your kind support....
regards
sandra