← Back to team overview

openerp-india team mailing list archive

[Bug 873456] Re: yaml_import cannot specify empty value

 

This was partially supported as of server revision 3794
revid:fp@xxxxxxxxxxx-20111113223056-g65pf5vzg7dwkks1, and has been
extended to support None value after merging your patch at revision 3827
revid: odo@xxxxxxxxxxx-20111124153233-4vpb6k1c3ksllsfd

Thanks!

** Changed in: openobject-server
       Status: Confirmed => Fix Released

** Changed in: openobject-server
    Milestone: None => 6.1

-- 
You received this bug notification because you are a member of OpenERP
Indian Team, which is subscribed to OpenERP Server.
https://bugs.launchpad.net/bugs/873456

Title:
  yaml_import cannot specify empty value

Status in OpenERP Server:
  Fix Released

Bug description:
  I have a multi-company set up and I'm importing existing data using
  yaml format and "import module".

  I have two companies set up and I'd like to import objects with company_id set to:
  * base.company
  * other.company
  * None

  Where none share the contacts.

  If I don't specify company_id tag, then the record ends up having the company_id of the user_id=1 which is base company.
  If I specify valid company_id, then the record ends up having the company_id set to the correct company.
  When specify python None value, or serialised as null in yaml, openerp-server doesn't import it.

  Attaching a branch preposal to fix this problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/openobject-server/+bug/873456/+subscriptions