| Age | Commit message (Collapse) | Author |
|
bzr revid: xmo@openerp.com-20120911063607-xvhyjqohptynro30
|
|
bzr revid: nicolas.vanhoren@openerp.com-20120824182707-vt91ef40ieeudwyw
|
|
bzr revid: nicolas.vanhoren@openerp.com-20120802144623-ykl5te005ytnv584
|
|
bzr revid: fme@openerp.com-20120627141249-o10e2htxqtio72l7
|
|
bzr revid: xmo@openerp.com-20120625135215-az1927llmk0vw655
|
|
CSV files
- 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
|
|
provided any of base fieldname or with the '/id'
bzr revid: xal@openerp.com-20120530101715-oe86b3vk6qynp29e
|
|
exactfieldname, then only on string
bzr revid: xal@openerp.com-20120530101608-8al6jw332oz0v2c0
|
|
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
|
|
bzr revid: msh@tinyerp.com-20120516120946-bxroqa9tiwhqxbpo
|
|
bzr revid: nicolas.vanhoren@openerp.com-20120417115726-5zwzwyp1lzdjxwh7
|
|
bzr revid: msh@tinyerp.com-20120404085243-69cx9zr4915eb6kz
|
|
bzr revid: nicolas.vanhoren@openerp.com-20120221162912-zheko30qoh84hcoq
|
|
bzr revid: nicolas.vanhoren@openerp.com-20120221153023-cqs66neaddtuf7km
|
|
bzr revid: nicolas.vanhoren@openerp.com-20120217114357-5jeue9292eg2zoqf
|
|
previous change would exclude all fields with @readonly, but @state can remove @readonly from fields and means fields are importable again (pretty much). Need to add that, otherwise it's almost impossible to import stuff
bzr revid: xmo@openerp.com-20120216163155-wh8uory00i2qifxy
|
|
fields
bzr revid: xmo@openerp.com-20120209090214-84d6jjr1jnf32kpi
|
|
bzr revid: fme@openerp.com-20120110165451-pvchn668y0b1p645
|
|
lp bug: https://launchpad.net/bugs/892248 fixed
lp bug: https://launchpad.net/bugs/885507 fixed
bzr revid: fme@openerp.com-20111221134306-k5w0g0oih3uvhy34
|
|
bzr revid: xmo@openerp.com-20111216114941-fr6wsfabxfqf86xw
|
|
dialog titles)
bzr revid: xmo@openerp.com-20111215104031-h2xjkf0zwf8x8zjk
|
|
bzr revid: xmo@openerp.com-20111201110140-ozkrhoxt0ug5qcnj
|
|
to server error
lp bug: https://launchpad.net/bugs/898547 fixed
bzr revid: xmo@openerp.com-20111201110007-sy3fj347ga7pj7d8
|
|
bzr revid: xmo@openerp.com-20111114101221-905mu3id02o3n2li
|
|
bzr revid: xmo@openerp.com-20111024142744-zeal912gqf9bvrrp
|
|
bzr revid: xmo@openerp.com-20111024141737-bk2rg08wvll1hgno
|
|
bzr revid: xmo@openerp.com-20111024140658-8t9csv9i6gd30luj
|
|
bzr revid: xmo@openerp.com-20111024135521-aikh791r9j94moal
|
|
lp bug: https://launchpad.net/bugs/878005 fixed
bzr revid: xmo@openerp.com-20111019134936-xfo9zt1ivgocbffr
|
|
lp bug: https://launchpad.net/bugs/878005 fixed
bzr revid: xmo@openerp.com-20111019103822-lx0gldsmxbqb87dr
|
|
bzr revid: xmo@openerp.com-20111018102108-2c1uixgbeb3t6wkx
|
|
bzr revid: ysa@tinyerp.com-20111017131849-u034vkz20cw8e31t
|
|
bzr revid: ysa@tinyerp.com-20111017061602-6sv4m5ew70by57yx
|
|
on required fields list.
lp bug: https://launchpad.net/bugs/871625 fixed
bzr revid: ysa@tinyerp.com-20111012080540-1m6x6npy7e0jaoif
|
|
todo: if exact equality with field name and field string fail, a levenshtein distance test
with the field string would be pretty cool (mostly for importing stuff)
bzr revid: xmo@openerp.com-20110926100744-1mcucy3njp9fd3r5
|
|
bzr revid: xmo@openerp.com-20110926093024-et5kvpvvq1vm811h
|
|
bzr revid: xmo@openerp.com-20110923130943-293wxucafwjloxwh
|
|
might have to change that, or something
bzr revid: xmo@openerp.com-20110923124634-sk9ka293ugc159gu
|
|
bzr revid: xmo@openerp.com-20110923122202-hnp6o1ybwgugive4
|
|
bzr revid: xmo@openerp.com-20110923110605-vw82lm018q6b2grt
|
|
bzr revid: xmo@openerp.com-20110923095609-ogxc6q3wnd0tez8v
|
|
bzr revid: xmo@openerp.com-20110923094500-0jn0tb3fgix9j8wg
|
|
everything's ready to setup autocompletes and check required fields & al
bzr revid: xmo@openerp.com-20110923092346-007j09xf5wfzq9zo
|
|
required fields
bzr revid: xmo@openerp.com-20110923083341-xa3sg2t053zonlsm
|
|
bzr revid: xmo@openerp.com-20110922155751-rkch0vpmhpolihxa
|
|
the validation process clearer
bzr revid: xmo@openerp.com-20110922121327-zqenx9bisr8pe4kd
|
|
selected
bzr revid: xmo@openerp.com-20110922120810-2fcmntd4w6yh9zvy
|
|
bzr revid: xmo@openerp.com-20110922120328-h9eh9gl6wf28xbzd
|
|
bzr revid: xmo@openerp.com-20110922105948-oms4h0t4uyl0qnm6
|
|
bzr revid: xmo@openerp.com-20110922095409-xxqb0l3mirralwps
|