Odoo/addons/web/static/src/js/data_import.js, branch 14.0

[REM] import from core, moving to module

2012-09-11T06:36:07+00:00

bzr revid: xmo@openerp.com-20120911063607-xvhyjqohptynro30

[IMP] made a whole-application replace of $element by $el

2012-08-24T18:27:07+00:00

bzr revid: nicolas.vanhoren@openerp.com-20120824182707-vt91ef40ieeudwyw

[IMP] Mass rename \t to 4 spaces

2012-08-02T14:46:23+00:00

bzr revid: nicolas.vanhoren@openerp.com-20120802144623-ykl5te005ytnv584

[CHG] Ashes to ashes, dashes to underscores.

2012-06-27T14:12:49+00:00

bzr revid: fme@openerp.com-20120627141249-o10e2htxqtio72l7

[MERGE] 6.1 changes and trunk

2012-06-25T13:52:15+00:00

bzr revid: xmo@openerp.com-20120625135215-az1927llmk0vw655

[MERGE] OPW 574895: fix incorrect matching of column headers when importing CSV files

2012-06-06T17:40:43+00:00

- required fields may sometimes be provided by alternative columns,
  and all the alternatives are therefore not required (e.g. for
  a m2o the CSV can provide m2o or m2o/id columns)
- when fields share the same label, precedence when matching
  column headers should be given to the field with the exact
  same name, rather than just the first one encountered

bzr revid: odo@openerp.com-20120606174043-f1nmkad3p17mccyy

[FIX] web: data import: correctly handle 'required' many2one - user can provided any of base fieldname or with the '/id'

2012-05-30T10:17:15+00:00

bzr revid: xal@openerp.com-20120530101715-oe86b3vk6qynp29e

[FIX] web: data import: fields matching have to be done first on exactfieldname, then only on string

2012-05-30T10:16:08+00:00

bzr revid: xal@openerp.com-20120530101608-8al6jw332oz0v2c0

[FIX] data_import: allow importing m2o via name_search() on top of their XML ID

2012-05-25T07:08:59+00:00

We do default to exporting the XML ID, but there are
many cases where completely new data needs to be
imported and there is no XML ID available to do so.
In that case allowing name_search() to be used as in
6.0 is a life-saver. This patch simply makes the
m2o field itself visible during import, so users can
use it in their CSV file or manually select it.

Some trivial examples:
- you need to import 2000 new leads with their countries,
  obviously you can't guess that base.be should be used
  for country Belgium
- you need to update 2000 unassigned leads in the system
  and assign them to some of the salemen... but you don't
  have their XML IDs and even if you had, the match is
  quite hard to do.

bzr revid: odo@openerp.com-20120525070859-y4q3bnamvag2pzcq

[FIX]Refixed the translation issue in import.

2012-05-16T12:09:46+00:00

bzr revid: msh@tinyerp.com-20120516120946-bxroqa9tiwhqxbpo