c2c-oerpscenario team mailing list archive

[Raphaël Valyi - http://www.akretion.com <693308@xxxxxxxxxxxxxxxxxx>]

Guys,

I add that if you could make the 'module' (the referential actually)
acceptable in the import context or specifiable in a field somewhere that
would be very good, it would make it very integrated with the
base_external_referentials module: so one could specify in which referential
(eg module) the "XML" ids he is providing are to be considered. This is
terribly useful when OpenERP is connected to other systems: like external
ecommerce, external accounting tool, external CRM and all: each OpenERP
business entity can hence have different ids each referential
and base_external_referentials makes this straightfoward and even allows to
define field mapping operations right inside OpenERP.


On Wed, Dec 22, 2010 at 8:50 AM, Ferdinand @ Camptocamp <
693308@xxxxxxxxxxxxxxxxxx> wrote:

> I wouild realy appreciate to have a default export list definition for
> all fields and a bit of intelligence choosing this definition excluding
> fields not available
>
> see attachment
> it is not userfriendly  and most users will have problems and loos much
> time to choose the correct fields to ask users to create a default  export
> list
> it's much easier to remove some unwanted fields or to drop a column in the
> spreadsheet
>
>
> ** Attachment added: "chricar_tools_export.zip"
>
> https://bugs.launchpad.net/openobject-client-web/+bug/693308/+attachment/1773432/+files/chricar_tools_export.zip
>
> --
> You received this bug notification because you are a member of OpenERP
> Framework Experts, which is subscribed to OpenObject Web Client.
> https://bugs.launchpad.net/bugs/693308
>
> Title:
>  Import / Export to review in Trunk
>
> Status in OpenObject Web Client:
>  Confirmed
>
> 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.
>
>
>
>

-- 
You received this bug notification because you are a member of C2C
OERPScenario, which is subscribed to the OpenERP Project Group.
https://bugs.launchpad.net/bugs/693308

Title:
  Import / Export to review in Trunk

Status in OpenObject Web Client:
  Confirmed

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.