Do you call _technical name_ to the OpenERP source code field name, or the PostgreSQL column name? In the later case, is not working for me. Mapping works but maps to _entity name_ instead of the exact PostgreSQL column name!

Name which is given inside the model is the table name it self. so whatever field name are define in spefice table in _columns {} dictionary you need to use that field name as column header to import data.

Ah ja, but the problem comes when... I'm actually doing manual mappings to database id of an entity (which is not a field but an ORM elsething) because I can not use a mapping based on field. We are talking about detecting a type of account, but there are two instance rows for this type of account, if you consider its name ('Capital' type of account), each for a different chart of accounts (in a multi-company environment)! I solve it doing a mapping to the actual row id in the CSV, but that way, when doing the import, I have to manually specify it as a "Entity BD Id" where has been mapped to "Entity", which btw is containing the name.

I finally solved these and all other issues performing imports using XML-RPC against OpenERP (hence committing after each import, I suppose, BTW), instead of using the browser CSV import, that makes a single commit if the import of all rows is successful and hence more expensive in terms of developer time.

Aha, understood. I guess the browser import is actually far more complex than the approach I used. However, at this point of expertise, to me it seems easier not to import using browser but using the 'create' method of the 'osv.Model' class, using a small script that reads a file and creates an entity per line. All the comlexity of calculating column lines is distributed among previous scripts that query PostgreSQL e.g. for row ids retrieving.

'column lines'* i meant 'values for each field in a row'.

John Doe, what you pointed out in your comment, as an answer, might be the most correct answer possible, given the literal question.

That page prompts "country_id:id" to force mapping to id. John Doe prompted to use "parent_id/id". Do you know which of either is older or which of either's deprecation is more probable?