Review: Needs Fixing
UI/Business:
* The error message for missing required fields is not exactly fun to see. 
Maybe just a notice that there are unset required fields above the table, and 
the red coloration on the table cells/selects themselves
* There's a similar problem when selecting the same field for two different 
columns:
  - The message is unclear
  - Only one of the columns is highlighted as conflicting, it's hard to find 
the other one
  - It would be nice if there were anchors allowing users to jump directly to a 
column, when the preview table is wide
* It's hard to see that the options box can be opened, it looks like it's just 
empty. Some sort of small arrow next to the table to show it can be toggled 
would be nice.
* In the lists of fields (select), the list is completely unsorted and is a 
pain to wade through (the order is essentially random). Sort the list before 
displaying it
* Might be nice if the fields in the select box had their `string` value next 
to the fieldname (in parens for instance), although it might also make the 
column *too wide*. Not sure, could you look at it and recommend?

Note, untested
If I match a relational field to an external id (formerly xmlid), what happens? 
E.g. I match partner_id/id to the partner_id column in sales orders, does the 
import work correctly?

Note that external ids are what the export now produces in the case where 
you're selecting the relational field itself (and not a subfield), and 
`$fieldname/id` has disappeared from the export UI (`$fieldname/.id has also 
been moved solely to the non-import-compatible view, except for o2ms)
-- 
https://code.launchpad.net/~openerp-dev/openerp-web/trunk-import-kch/+merge/74216
Your team OpenERP R&D Team is subscribed to branch 
lp:~openerp-dev/openerp-web/trunk-import-kch.

_______________________________________________
Mailing list: https://launchpad.net/~openerp-dev-gtk
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~openerp-dev-gtk
More help   : https://help.launchpad.net/ListHelp

Reply via email to