Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0021594Openbravo ERP01. General setuppublic2012-09-10 18:142016-09-06 10:30
Reportercaristu 
Assigned ToTriage Omni OMS 
PriorityurgentSeveritymajorReproducibilityalways
StatusnewResolutionopen 
PlatformOS5OS Version
Product Version 
Target Version3.0MP16Fixed in Version 
Merge Request Status
Review Assigned To
OBNetwork customerOBPS
Web browser
ModulesCore
Support ticket16812
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary0021594: Core update turns inactive report template into active in Document type window
DescriptionAfter updating the core, a core record template marked as inactive turns into active.

In general, changes made in Document Type configuration should be maintained although dataset is applied again
Steps To Reproduce1) Start with an environment with the core not in the last MP (in MP12 for example)

2) As Group admin, Go to the [Document type] window, select the AR Invoice document type and in the [Report Template] tab, uncheck the "active" checkbox.

3) As System Admin, Go to [Module Management] and update the Core. Rebuild and restart the system.

4) As Group Admin, Go to the [Enterprise Module Management] window and apply the new datasets.

5) Go to the [Document type] window, select the AR Invoice, and notice that in the [Report Template] tab, the record is active again. It should keep the inactive status.
Proposed Solution
Additional Information
TagsNo tags attached.
Relationships
related to feature request 0015951 new Triage Platform Base Dataset application to exclude active check-boxes 
related to defect 0033567 new Triage Omni OMS It is possible to save report templates without name 
has duplicate design defect 0033525 closed platform Default reports get activated when updating 
related to feature request 0033572 closed caristu Ability to define a Report Template as default 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2012-09-10 18:14caristuNew Issue
2012-09-10 18:14caristuAssigned To => dmiguelez
2012-09-10 18:14caristuModules => Core
2012-09-10 18:14caristuOBNetwork customer => Yes
2012-09-10 18:14caristuSupport ticket => 16812
2012-09-10 18:14caristuResolution time => 1349733600
2012-09-10 18:15caristuIssue Monitored: networkb
2012-09-10 18:15caristuSummaryCore update turns inactive report template into active => Core update turns inactive report template into active in Document type window
2012-09-10 20:06dmiguelezAssigned Todmiguelez => jonalegriaesarte
2012-09-17 10:18jonalegriaesarteAssigned Tojonalegriaesarte => ioritzCia
2012-09-18 10:48ioritzCiaNote Added: 0052188
2012-09-18 10:49ioritzCiaNote Edited: 0052188bug_revision_view_page.php?bugnote_id=0052188#r3866
2012-09-18 10:49ioritzCiaTypedefect => design defect
2012-09-18 10:52ioritzCiaAssigned ToioritzCia => dmiguelez
2015-03-18 13:50maiteTriggers an Emergency Pack => No
2015-03-18 13:50maiteDescription Updatedbug_revision_view_page.php?rev_id=8022#r8022
2015-03-18 13:50maiteSteps to Reproduce Updatedbug_revision_view_page.php?rev_id=8024#r8024
2015-04-14 12:48Triage FinanceAssigned Todmiguelez => Triage Finance
2016-02-29 17:51ngarciaRelationship addedrelated to 0015951
2016-07-28 10:27caristuRelationship addedhas duplicate 0033525
2016-07-29 12:40caristuRelationship addedrelated to 0033567
2016-08-01 09:47caristuRelationship addedrelated to 0033572
2016-09-06 10:30caristuNote Added: 0089773

Notes
(0052188)
ioritzCia   
2012-09-18 10:48   
(edited on: 2012-09-18 10:49)
This issue is moved to design defect due to the following reason:

- The first option was to solve it as the ADSequence reference data exporting/importing. In ADSequence the currentnext column is not exported neither imported. We could do that for isactive column for the report templates, but this would be a regression because it would not allow us to inactive this record anymore.

- Another option was to inactive the records through a modulescript. This is not an option neither because the user would have to execute update.database after applying the database.

- The last option we figured out was to set the column as not to be exported in the dataset definition in the column tab. This is not an option, because the purpose is to keep one record to be activated or deactivated and this option would keep all records of being changed or not.

- Other options require a deep thought and due to that, this issue is changed to design defect.
(0089773)
caristu   
2016-09-06 10:30   
After solving issue 0033572, now it is possible to define a report template as default.

So, although the previously inactive documents get activated after applying the new datasets, this will not affect anymore.

This is because the document marked as default will be always taken into account at the first place.