Openbravo Issue Tracking System - Openbravo ERP |
| View Issue Details |
|
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0010794 | Openbravo ERP | 00. Application dictionary | public | 2009-09-28 17:57 | 2012-09-25 12:34 |
|
| Reporter | gorkaion | |
| Assigned To | marvintm | |
| Priority | normal | Severity | major | Reproducibility | have not tried |
| Status | scheduled | Resolution | open | |
| Platform | | OS | 20 | OS Version | Gentoo |
| Product Version | pi | |
| Target Version | | Fixed in Version | | |
| Merge Request Status | |
| Review Assigned To | |
| OBNetwork customer | |
| Web browser | |
| Modules | Core |
| Support ticket | |
| Regression level | |
| Regression date | |
| Regression introduced in release | |
| Regression introduced by commit | |
| Triggers an Emergency Pack | No |
|
| Summary | 0010794: Export cloned datasets with original uuids |
| Description | At this moment it is possible to import several times a dataset in different client/organizations. To manage this there is the AD_REF_DATA_LOADED table, where is stored the original uuid of each imported record as it is in the xml file and the generated uuid in each import. This avoids the duplicate primary key problem.
The problem is that when a dataset is being exported these cloned records are not considered and the xml is generated using the new uuids instead of the original. Making very difficult to update an existing dataset.
This is, when you modify an imported dataset clone it should be possible to export it so the xml is updated. And later import again the dataset to update all the clones to the last changes (which is already possible) |
| Steps To Reproduce | Create a new dataset.
Import it in several organizations.
Modify the exported data of a dataset.
Try to export it again. |
| Proposed Solution | |
| Additional Information | |
| Tags | No tags attached. |
| Relationships | |
| Attached Files | |
|
| Issue History |
| Date Modified | Username | Field | Change |
| 2009-09-28 17:57 | gorkaion | New Issue | |
| 2009-09-28 17:57 | gorkaion | Assigned To | => rafaroda |
| 2009-09-29 22:43 | psarobe | Note Added: 0020548 | |
| 2009-09-29 22:43 | psarobe | Status | new => feedback |
| 2009-10-09 16:46 | psarobe | Note Added: 0020916 | |
| 2009-10-09 17:25 | gorkaion | Status | feedback => scheduled |
| 2009-10-09 17:25 | gorkaion | Assigned To | rafaroda => mtaal |
| 2009-10-09 17:25 | gorkaion | fix_in_branch | => pi |
| 2009-10-19 10:49 | mtaal | Assigned To | mtaal => marvintm |
| 2009-10-19 10:52 | mtaal | Note Added: 0021156 | |
| 2009-10-19 17:02 | marvintm | Note Added: 0021183 | |
| 2009-12-02 12:03 | rafaroda | version | => pi |
| 2009-12-02 12:03 | rafaroda | fix_in_branch | pi => |
| 2009-12-16 12:44 | dalsasua | Issue Monitored: dalsasua | |
| 2012-05-08 16:54 | marvintm | Type | defect => design defect |
| 2012-09-25 12:34 | AugustoMauch | Note Added: 0052559 | |
|
Notes |
|
|
|
Hi Gorka,
Are the steps to reproduce correct and the description? |
|
|
|
|
|
Reminder sent to: gorkaion
Please provide feedback |
|
|
|
(0021156)
|
|
mtaal
|
|
2009-10-19 10:52
|
|
Hi Antonio,
I assigned this issue to you cause afaics it corresponds to the topic 'Changes to make Import/Export client more robust and useful' which is on your list. Let me know if I am mistaking here!
gr. Martin |
|
|
|
|
|
Yep, exactly, this issue is related to the changes we need to make to Import/Export client. |
|
|
|
|
Effort: 5
Impact: low
Plan: mid |
|