← Back to team overview

c2c-oerpscenario team mailing list archive

[Bug 805246] Re: [6.0.2] CSV import auto-detect does not support ":id" headers at client-side

 

Hello Bernard,

When you say "does not accept", I suppose you mean that auto-detection
does recognize it, right? This does does not actually prevent you from
uploading the file by specifying the field names manually, normally.

I agree this is not consistent, and is caused by the various patches in
6.0 to improve the client-side import logic (rev 1727 and 1729).

Here are 2 quick and dirty patches (untested) to restore that behavior
in a consistent manner (also for translations) in both GTK and Web
clients. I will leave the final resolution to the Web and GTK teams.

** Patch added: "quick and dirty patch for gtk"
   https://bugs.launchpad.net/openobject-server/+bug/805246/+attachment/2192433/+files/bug_805246_gtk.patch

-- 
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/805246

Title:
  [6.0.2] CSV import auto-detect does not support ":id" headers at
  client-side

Status in OpenERP GTK Client:
  Confirmed
Status in OpenERP Web Client:
  Invalid

Bug description:
  Hello,

  Server: Ubuntu v10.04
  Workstation: Windows 7 

  In V5, it was possible to import via transactional object import (both
  GTK and web) all files including header line with ":id" or ".id". It
  seems that in V6 it is not possible anymore, as it accepts only "/id"
  or "/.id".

  This is a quite big regression as we can't use anymore the same file
  declaration for import via server or client.

  Our remark may look trivial, but we try to streamline our data
  migration processes like all other partners in order to reduce OpenERP
  costs against competitors. In that context we have developed data
  migration templates filled by clients. These templates can be used for
  data loading on server side as well on client side. It was succesful
  on v5 but no more on v6 due to that issue.

  Is there any good reason to block the ".id" and ".id" on client side
  in V6 ? This issue obliges to define two different templates for
  server and client import, which has no clear advantage...

  Regards,

  Bernard

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


References