Openbravo Issue Tracking System - Openbravo ERP |
| View Issue Details |
|
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0009139 | Openbravo ERP | 00. Application dictionary | public | 2009-05-22 10:55 | 2022-02-01 08:08 |
|
| Reporter | roklenardic | |
| Assigned To | Triage Platform Base | |
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | acknowledged | Resolution | open | |
| Platform | | OS | 20 | OS Version | Ubuntu 9.04 |
| Product Version | 2.50MP1 | |
| 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 | 0009139: Packs and Templates must not contain datasets |
| Description | Currently it is possible to define datasets for packs and templates. However, that should not be possible since Datasets should always be defined in modules. |
| Steps To Reproduce | |
| Proposed Solution | 1 Hide "has reference data" checkbox within the Module window when a pack or a template is selected
2 have a validation on the module listbox inside the dataset window so one cannot create a dataset that belongs to a module that is a pack or template |
| Additional Information | |
| Tags | No tags attached. |
| Relationships | |
| Attached Files | |
|
| Issue History |
| Date Modified | Username | Field | Change |
| 2009-05-22 10:55 | roklenardic | New Issue | |
| 2009-05-22 10:55 | roklenardic | Assigned To | => rafaroda |
| 2009-05-22 15:56 | rafaroda | Assigned To | rafaroda => alostale |
| 2009-05-22 15:56 | rafaroda | Status | new => scheduled |
| 2009-05-27 11:21 | pjuvara | Issue Monitored: iciordia | |
| 2009-05-27 11:21 | pjuvara | Note Added: 0016673 | |
| 2009-05-27 11:21 | pjuvara | Issue Monitored: pjuvara | |
| 2009-05-27 15:06 | iciordia | Note Added: 0016680 | |
| 2009-05-27 15:08 | iciordia | Note Added: 0016681 | |
| 2009-05-28 00:37 | pjuvara | Note Added: 0016693 | |
| 2011-10-28 13:38 | psarobe | Note Added: 0042242 | |
| 2011-10-28 13:38 | psarobe | Status | scheduled => closed |
| 2011-10-28 13:38 | psarobe | Resolution | open => no change required |
| 2011-10-28 14:19 | iciordia | Status | closed => new |
| 2011-10-28 14:19 | iciordia | Resolution | no change required => open |
| 2011-10-28 14:19 | iciordia | Status | new => scheduled |
| 2011-10-28 14:19 | iciordia | Type | defect => design defect |
| 2017-03-31 14:36 | alostale | Status | scheduled => acknowledged |
| 2017-04-10 14:35 | alostale | Assigned To | alostale => platform |
| 2022-02-01 08:08 | alostale | Assigned To | platform => Triage Platform Base |
|
Notes |
|
|
|
|
Reminder sent to: alostale, iciordia
Ismael,Asier,
I think this issue should be rejected. Templates and packs are not intended to contain data sets nor any other content (templates should only contain the configuration file).
What do you think?
Paolo |
|
|
|
|
I think this is a bug: because templates and packs are not intended to contain data sets nor any other content we should validate the information:
-Hide (display logic) fields in a pack/template that are not applicable to them (hasChartOfAccounts, isTranslationModule, hasReferenceData, referenceDataInfo)
-Hide (although it need some discussion about how to translate an Industry Template): default, language, requiresTranslation
-Remove them from drop-down lists where they are not applicable (application dictionary components, datasets, etc.)
-They can not have a db_prefix
Ismael |
|
|
|
|
|
Reminder sent to: alostale
My reply to Paolo, what do you think? |
|
|
|
|
|
Sorry. I had misread. As stated this is a defect. |
|
|
|
|
|
Can contain datasets, for example the Spanish localization pack contains the taxes module which is a dataset |
|