migrating partners

migrating partners

Postby boran » Tue Dec 08, 2009 5:50 pm

Hi,

I would like to use your module to copy of partners & addresses.
After installing your 3 modules, I can connect to the old DB.
Then I created a schedule migration of for Partners, Partner Addresses.
When running the migration, there are 3 warnings and 1 error:

The warnings make sense, and I would have hope that I could just correct the receivable/payable accounts manually afterwards?
Warning! Object "res.partner" have relation field 'property_account_receivable' which related to object "account.account", this field was not filled because related object's model is not added in Import Model list.
Warning! Object "res.partner" have relation field 'property_account_payable' which related to object "account.account", this field was not filled because related object's model is not added in Import Model list.
Warning! Object "res.partner" have relation field 'events' which related to object "res.partner.event", this field was not filled because related object's model is not added in Import Model list.


Then there is this error:
Traceback (most recent call last):
File "/opt/openerp.bzr/server/bin/addons/server_migration/migration.py", line 600, in _import_data
res = self.import_model(cr, uid, sock, remote_config, remote_uid, id)
File "/opt/openerp.bzr/server/bin/addons/server_migration/migration.py", line 496, in import_model
res = self.import_model(cr, uid, sock, remote_config, remote_uid, rel_import_model_id[0], ref_list, rel_field)
File "/opt/openerp.bzr/server/bin/addons/server_migration/migration.py", line 469, in import_model
res = self.import_model(cr, uid, sock, remote_config, remote_uid, rel_import_model_id[0], ref, rel_field)
File "/opt/openerp.bzr/server/bin/addons/server_migration/migration.py", line 563, in import_model
res_id = create(self.pool.get(model_name), cr, uid, mdata_final)
File "/opt/openerp.bzr/server/bin/addons/server_migration/migration.py", line 267, in create
raise except_orm(_('ValidateError'),
NameError: global name '_' is not defined

What is wrong there?
boran
 
Posts: 1
Joined: Tue Dec 08, 2009 5:23 pm

Re: migrating partners

Postby ruslans » Wed Dec 09, 2009 11:00 am

The program try to throw error message: "The value "%s" for the field title is not in the selection"
Before you can import model with selection fields, where value get from another model, at first is needed to import information of this model. In your case is needed to import 'res.partner.title'.
ruslans
 
Posts: 15
Joined: Mon Jun 15, 2009 11:09 am

Re: migrating partners

Postby phu » Wed Feb 24, 2010 12:07 am

Hi,
I'm trying your server_migration module, but it seems not work correctly. In my simple test, my goal is to migrate all the partners in original database to newly created database.
My steps are:
1. Create a new database (A) with demonstration data, using Minimal Profile. This one will act as the original database. (A) contains 21 partners.
2. Create a new, blank database (without demonstration data) (B), using Miniml Profile too (to avoid differences in module set). (B) contains 1 partner.
3. Chose Partner in Model Mapping screen, then Create a Migration Scheduler with this mapping. The result for migration Partners data from (A) to (B) I got is: (B) contains 24 partners. There some arbitrarily duplicated rows.
4. To confirm, I repeated step 2 again, creating another new, blank database (C). Then repeated step 3 with (C). The result I got: (C) contains 34 partners. Don't know why there're many duplicated rows.
Would you please explain whether I made mistakes in some steps?

Thanks and regards,
P/S: btw, the idea of this module is very nice. Thanks for your good work!
phu
 
Posts: 4
Joined: Tue Feb 23, 2010 11:56 pm

Re: migrating partners

Postby sraps » Wed Feb 24, 2010 10:46 am

Hi!
We have been reported on this problem before, so it seems, that there may be some problem behind that.

I will give it a check in nearest time and report back.

Kaspars
sraps
 
Posts: 403
Joined: Mon May 04, 2009 10:04 pm

Re: migrating partners

Postby phu » Wed Feb 24, 2010 12:48 pm

Hi,
Thanks for you quick reply. I'll follow this thread to check the status of this.
Regards,
phu
 
Posts: 4
Joined: Tue Feb 23, 2010 11:56 pm

Re: migrating partners

Postby sraps » Tue Mar 02, 2010 5:19 pm

Hi,
although, I had no luck to repeat the problem you have described, we had some minor code cleanup for version that is not in LP currently. So, it theoretically, should not impose big improvement. Still, stay tuned, we will place the updated version soon.

Kaspars
sraps
 
Posts: 403
Joined: Mon May 04, 2009 10:04 pm

Re: migrating partners

Postby phu » Fri Mar 05, 2010 11:20 pm

Great, thanks!
I'm looking forward to the newest code, then try it again and give you my feedback.

Regards,
Le Truong Vinh Phu
phu
 
Posts: 4
Joined: Tue Feb 23, 2010 11:56 pm

Re: migrating partners

Postby sraps » Mon Mar 22, 2010 4:33 pm

Hi,
I have placed updated version of migration module, please have a look...

Kaspars
sraps
 
Posts: 403
Joined: Mon May 04, 2009 10:04 pm

Re: migrating partners

Postby catinga » Fri Apr 01, 2011 8:59 pm

This is what I'm getting and there's no way I can find a way to import Partners

Code: Select all
<<<<<<<<<<<<<<<< Warning! >>>>>>>>>>>>>>>> Warning! Object "res.partner" have relation field 'property_account_receivable' which related to object "account.account", this field was not filled because related object's model is not added in Import Model list. Warning! Object "res.partner" have relation field 'property_account_payable' which related to object "account.account", this field was not filled because related object's model is not added in Import Model list. Warning! Object "res.partner" have relation field 'events' which related to object "res.partner.event", this field was not filled because related object's model is not added in Import Model list. <<<<<<<<<<<<<<<< Error! >>>>>>>>>>>>>>>> Traceback (most recent call last): File "/home/mbmaster/openerp/addons/server_migration.zip/server_migration/migration.py", line 626, in _import_data res = self.import_model(cr, uid, sock, remote_config, remote_uid, id) File "/home/mbmaster/openerp/addons/server_migration.zip/server_migration/migration.py", line 498, in import_model res = self.import_model(cr, uid, sock, remote_config, remote_uid, rel_import_model_id[0], ref, rel_field) File "/home/mbmaster/openerp/addons/server_migration.zip/server_migration/migration.py", line 450, in import_model for model_data in sock.execute(remote_config['db_name'], remote_uid, remote_config['password'], old_model_name, 'read', ref_ids or rec_ids, fields_list): File "/usr/lib/python2.5/xmlrpclib.py", line 1147, in __call__ return self.__send(self.__name, args) File "/usr/lib/python2.5/xmlrpclib.py", line 1437, in __request verbose=self.__verbose File "/usr/lib/python2.5/xmlrpclib.py", line 1201, in request return self._parse_response(h.getfile(), sock) File "/usr/lib/python2.5/xmlrpclib.py", line 1340, in _parse_response return u.close() File "/usr/lib/python2.5/xmlrpclib.py", line 787, in close raise Fault(**self._stack[0]) Fault:
catinga
 
Posts: 5
Joined: Wed Feb 03, 2010 5:44 pm

Re: migrating partners

Postby sullivan » Thu Jul 18, 2013 3:30 pm

Oracle offers an extensive variety of relocation administrations to help you improve your use of Oracle engineering.racle can give uphold for moving from legacy or non-Oracle advances to Oracle.grating with Oracle SQL Developer decreases the time, dangers, and fiscal hindrances included in relocating to the Oracle stage.
look here
sullivan
 
Posts: 1
Joined: Thu Jul 18, 2013 3:30 pm

Next

Return to Server Data Migration

cron
Copyright © 2001 Alistek Ltd., ALL RIGHTS RESERVED