Module product_autocompany breaks travis ci test about multi-company HOT 7 CLOSED

That can be solved providing a migration script (for v7) or post-hook for v8 that fills with one company each empty record.

from multi-company.

right! I'll create a migration script for that.

from multi-company.

@pedrobaeza I just checked the code of odoo,（ migration.py）, it seems that only when we update the module and the version is higher, the migration script will be executed. However in this case , we wanna run the migration script when the module is first installed. Please let me know if I miss anything. Thanks! :)

from multi-company.

For v7, if you check for version is None, you can execute it in first install. For v8, you have to use a pre or post-init hook. See an example here:

https://github.com/odoomrp/odoomrp-wip/blob/8.0/quality_control_stock/__openerp__.py#L42
https://github.com/odoomrp/odoomrp-wip/blob/8.0/quality_control_stock/__init__.py#L10

from multi-company.

@pedrobaeza Thanks very much for you answer. I get how it works for v8.
But for v7, What do you mean by 'version is None'. I checked the code again, the migration only works for the module whose state is "to upgrade" (no 'to install' state). I tried putting the version as none, not working.

from multi-company.

Here you can see an example of a migration script with if not version: condition that fits for performing at first install (not upgrade):

https://github.com/OCA/account-financial-reporting/blob/7.0/account_financial_report_webkit/migrations/7.0.1.0.2/post-migration.py

from multi-company.

There hasn't been any activity on this issue in the past 6 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 30 days.
If you want this issue to never become stale, please ask a PSC member to apply the "no stale" label.

from multi-company.