diff options
| author | Harry (OpenERP) <hmo@tinyerp.com> | 2011-08-25 10:59:09 +0530 |
|---|---|---|
| committer | Harry (OpenERP) <hmo@tinyerp.com> | 2011-08-25 10:59:09 +0530 |
| commit | bf6388f3481baaab1315dd3e69546efa5c0756dd (patch) | |
| tree | 9cfb45aa8b841d491402becf80ceb3204d70b2b4 /addons/analytic_user_function/analytic_user_function_view.xml | |
| parent | 8f3b055dca9814411427022baf290fa238eee6b6 (diff) | |
| parent | 0d6bffd75ad086a06b609089ab133aa798551edc (diff) | |
[IMP] ir.edi:we must use the full __id from the EDI as the new XML-ID for objects created during EDI import. The db-uuid is an important part of it, this is what will avoid conflicts of IDs between multiple databases. So the 'module' column in ir.model.data will contain 'db-uuid:xml-id', which is fine. This will also avoid deleting all those records at the next update during cleanup of module data
bzr revid: hmo@tinyerp.com-20110825052909-hpb9nae84myld6bu
Diffstat (limited to 'addons/analytic_user_function/analytic_user_function_view.xml')
0 files changed, 0 insertions, 0 deletions