Openbravo Issue Tracking System - Openbravo ERP |
| View Issue Details |
|
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0014848 | Openbravo ERP | A. Platform | public | 2010-10-08 18:45 | 2022-02-01 08:08 |
|
| Reporter | marvintm | |
| Assigned To | Triage Platform Base | |
| Priority | normal | Severity | major | Reproducibility | have not tried |
| Status | new | Resolution | open | |
| Platform | | OS | 5 | OS Version | |
| Product Version | | |
| 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 | 0014848: Improvements in Import/Export Client |
| Description | The Import/Export client needs to be improved in the following ways:
- Dynamic Dataset: currently, the entities exported in the client are defined as the ones contained in the Client dataset. However, this information doesn't need to be explicitly set, as it can be computed from the access level of the tables themselves. A better implementation would be to export every table in the system which has a correct access level.
- Structure validation: a requirement for this process is that the tables which are exported in the exported instance also exist in the instance in which the client is imported, and contain the same columns with the same datatypes. Currently, this is not checked. The idea would be to export the table structure inside the client file itself, and it would be read and validated by the importing instance, before the instance attempts to import the client.
- Issues with dataset import: if a client contains records cloned from a dataset, the references to those records are lost, and therefore are not defined as having been imported in the imported client. This information should also be exported inside the client, and the references should be correctly resolved when importing the client. |
| Steps To Reproduce | |
| Proposed Solution | |
| Additional Information | |
| Tags | No tags attached. |
| Relationships | | related to | defect | 0014553 | 2.50MP23 | closed | marvintm | Dataset 'Client Definition' --> There are tables that do not meet the validation |
|
| Attached Files | |
|
| Issue History |
| Date Modified | Username | Field | Change |
| 2010-10-08 18:45 | marvintm | New Issue | |
| 2010-10-08 18:45 | marvintm | Assigned To | => marvintm |
| 2010-10-08 18:45 | marvintm | Target Version | => 3.0 |
| 2010-10-18 16:18 | marvintm | Relationship added | related to 0014553 |
| 2011-01-07 11:00 | hgbot | Checkin | |
| 2011-01-07 11:00 | hgbot | Note Added: 0033535 | |
| 2011-01-07 11:07 | shuehner | Issue Monitored: shuehner | |
| 2011-01-07 11:49 | marvintm | Note Added: 0033536 | |
| 2011-01-10 18:41 | hudsonbot | Checkin | |
| 2011-01-10 18:41 | hudsonbot | Note Added: 0033569 | |
| 2011-06-02 10:54 | dmitry_mezentsev | Target Version | 3.0MP0 => 3.0MP1 |
| 2011-06-22 19:57 | dmitry_mezentsev | Target Version | 3.0MP1 => 3.0MP2 |
| 2011-06-22 20:23 | dmitry_mezentsev | Target Version | 3.0MP2 => 3.0MP3 |
| 2011-08-31 10:12 | marvintm | Target Version | 3.0MP3 => 3.0MP4 |
| 2011-09-16 09:08 | roklenardic | Issue Monitored: roklenardic | |
| 2011-09-26 17:53 | marvintm | Target Version | 3.0MP4 => 3.0MP5 |
| 2011-10-26 17:11 | marvintm | Target Version | 3.0MP5 => 3.0MP6 |
| 2011-11-15 10:26 | iperdomo | Target Version | 3.0MP6 => |
| 2017-12-17 17:43 | shuehner | Assigned To | marvintm => platform |
| 2022-02-01 08:08 | alostale | Assigned To | platform => Triage Platform Base |