openerp-dev-web team mailing list archive

[Ronald Portier <ronald@xxxxxxxx>]

I would like to add another requirement to make import really usefull:

Now data can only be imported, basically in an empty table, or a table
that has no overlap whatsoever with the data to be importerd regadring
unique keys.

This makes it really difficult to use the import function to synchronize
changes from other databases systems.

In my opinion there should be an option on the import function to:
EITHER throw an error when an row in the csv is encountered that is already in the database (existing functionality),
OR to ignore duplicates altogether (that is only add rows when their keys are not already in the database),
OR to update existing rows (having the same keys as in the csv) with the new values,
OR to use the import as a complete replace of existing data.

Kind regards,

-- 
You received this bug notification because you are a member of OpenERP
SA's Web Client R&D, which is a bug assignee.
https://bugs.launchpad.net/bugs/693308

Title:
  Import / Export to review in Trunk

Status in OpenERP Web Client:
  Fix Released

Bug description:
  Hello,

  The import/export tool must be reviewed completly in trunk in order to
  be easier to use. The main change is the "import compatible" option
  that allows to export any kind of data (including one2many, many2one,
  etc) and reimport the file after to update or create new data. The v5
  behaviour was unuseable at all.

  I already commited the changes in the server and GTK client to support
  this. Only the web client is remaining.

  Have a look at the attached PDF file for the useability of the two
  screens to review.

  Import Tool
  -----------

  The import tool must be simplified. We don't need to select the fields
  anymore, it will automatically take the columns defined by the first
  row of the .CSV file.

  When you select a file, the web client should make a preview of the
  first three rows. You can change the CSV options "field separator,
  field delimitor, encoding". Just display the columns as it, without
  any interpretation. (if they are ID or XML ID, just display the IDs).

  Export Tool
  -----------

  There is a real difference between the normal mode and the "Import
  Compatible" mode.

  If you set the import compatible mode:
  1. For every field:
    - many2one: just display two children: id and .id
    - many2many: just display this field without children
    - one2many: normal behaviour
  2. When you export, put the name of the fields in the first columns, and not their label. (example: partner_id/id)

  If you don't set the import compatible mode. For every:
  1. For every field:
    - many2one: you can see all children
    - many2many: you can see all children
    - one2many: you can see all children
  2. When you export, put the label of the fields in the first columns, and not their name. (example: Partner/ID)

  I changed the format of the csv file. Instead of "db_id", I used
  ".id". An example of "import compatible" file exported from partners:

    id,.id,name,address.id,address/id,address/name
    base.res_partner_agrolait,3,Agrolait,11,base.res_partner_address_8delivery,Paul

  This has to be done in trunk, before v6.0. I think it's critical for
  OpenERP Online users.

  Test with the GTK client to be sure the behaviour is the same in the
  web and GTK client.