CRM module is not yet covered

Bug #983731 reported by Christophe Combelles on 2012-04-17
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenUpgrade Addons
Status tracked in 7.0
Holger Brunn (Therp)

Bug Description


after an upgrade we got the following issues on the crm :

- the mail_message_id_seq sequence was missing
- a domain using removed attribute "type" of crm_case_stage was still there
- the corresponding "type" column was still there although the attribute did not exist

I had to :

CREATE SEQUENCE mail_message_id_seq MINVALUE 0;
SELECT setval('mail_message_id_seq', (SELECT MAX(id) FROM mail_message)+1);
alter table crm_case_stage drop column type;

and I had to manually remove the domain and context in the "Stages" window_action

Related branches

Hi Christophe,

thank you for your input. As you probably will know, only a number of modules have been written migration scripts for at this moment. The crm* modules for instance are not yet covered. Would you be able to provide a script for some of these modules? Your input above seems like a good starting point.

You can check the list of covered modules 6.0 -> 6.1 here:


Changed in openupgrade-addons:
importance: Undecided → Wishlist
summary: - issues on crm after upgrade
+ CRM module is not yet covered
Changed in openupgrade-addons:
status: New → Fix Committed
assignee: nobody → Holger Brunn (Therp) (hbrunn)

Hi Christophe,

the CRM module is now covered for migrations from 6.0 to 6.1. That should fix the references to the stage type.

Had a look at your other issue with the sequence. Turns out this is an oversight in the OpenUpgrade architecture. When renaming ORM tables, the sequences that OpenERP uses to provide the resource id need to be renamed as well. This will be fixed ASAP.


Changed in openupgrade-addons:
status: Fix Committed → In Progress
importance: Wishlist → High
Changed in openupgrade-addons:
status: In Progress → Fix Committed
Chris Halls (halls) wrote :

Just for info: I'm currently looking at CRM migration scripts for 5.0->6.0

Hi Chris,

thanks for the update. That would be great.

Crm 6.0 -> 6.1 has been covered by now. All the other issues in this thread have also been dealt with and merged, although in general like the 'type' column mentioned in the original post, obsolete columns are not being dropped yet. See this blueprint


Yann Papouin (yann-papouin) wrote :

About 6.1 -> 7.0, an error occured in migrate_partners [1], the "crm.meeting" does not have a partner_id.

In 6.1, the model "crm.meeting" defined in the module "crm" owns:
partner_id (many2one)
partner_address_id (many2one)

In 7.0, the model "crm.meeting" defined in the module "base_calendar" owns:
partner_ids (many2many)

[1] fix_partner(cr, pool, 'crm.meeting', 'partner_id', openupgrade.get_legacy_name('partner_address_id'))

It's time to kill this old bug. Yann, thanks for your observation. Can you create a new bug report for this specific issue?

Changed in openupgrade-addons:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers